date:20080214


[ 
https://issues.apache.org/jira/browse/GERONIMO-3857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12569195#action_12569195
 ] 

Sangjin Lee commented on GERONIMO-3857:
---

There is also an issue of handling folded headers.  Namely if a CRLF is 
followed by a LWSP character (SPACE or HTAB), it should be considered a 
continuation of the previous header line.

HttpResponseDecoder does not handle that case correctly, as it relies solely on 
CRLF to determine line boundaries.  It would not be able to handle folded 
headers.  I will follow up with a separate bug on that issue.  I think it can 
be handled with a separate fix...

> response header parsing is done incorrectly
> ---
>
> Key: GERONIMO-3857
> URL: https://issues.apache.org/jira/browse/GERONIMO-3857
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: AsyncHttpClient
>Affects Versions: 1.x
>Reporter: Sangjin Lee
>Assignee: Rick McGuire
> Attachments: GERONIMO-3857.patch
>
>
> When we decode response headers, HttpDecoder separates name from value using 
> ": " (note the *single*space after the colon).  This is incorrect.  The HTTP 
> spec says
> - The field value MAY be preceded by any amount of LWS, though a single SP is 
> preferred.
> The separator pattern should be simply ":".  Then any preceding or trailing 
> LWSP characters (SP or HT) should be removed from the value.  This is a 
> rather critical issue.  I had headers like 
> Server: Foo
> Content-Length:62
> Connection: close
> (notice lack of space after "Content-Length:")
> HttpResponseDecoder cannot properly parse the above headers, and throws a 
> StringIndexOutOfBoundsException.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (GERONIMO-3857) response header parsing is done incorrectly


 [ 
https://issues.apache.org/jira/browse/GERONIMO-3857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sangjin Lee updated GERONIMO-3857:
--

Attachment: GERONIMO-3857.patch

A suggested fix

> response header parsing is done incorrectly
> ---
>
> Key: GERONIMO-3857
> URL: https://issues.apache.org/jira/browse/GERONIMO-3857
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: AsyncHttpClient
>Affects Versions: 1.x
>Reporter: Sangjin Lee
>Assignee: Rick McGuire
> Attachments: GERONIMO-3857.patch
>
>
> When we decode response headers, HttpDecoder separates name from value using 
> ": " (note the *single*space after the colon).  This is incorrect.  The HTTP 
> spec says
> - The field value MAY be preceded by any amount of LWS, though a single SP is 
> preferred.
> The separator pattern should be simply ":".  Then any preceding or trailing 
> LWSP characters (SP or HT) should be removed from the value.  This is a 
> rather critical issue.  I had headers like 
> Server: Foo
> Content-Length:62
> Connection: close
> (notice lack of space after "Content-Length:")
> HttpResponseDecoder cannot properly parse the above headers, and throws a 
> StringIndexOutOfBoundsException.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Created: (GERONIMO-3858) start-server.bat fails to start server if there is a space in the path

2008-02-14 Thread YunFeng Ma (JIRA)

start-server.bat fails to start server if there is a space in the path
--

 Key: GERONIMO-3858
 URL: https://issues.apache.org/jira/browse/GERONIMO-3858
 Project: Geronimo
  Issue Type: Bug
  Security Level: public (Regular issues)
  Components: startup/shutdown
Affects Versions: 2.1, 2.1.1, 2.2
 Environment: Windows XP
Reporter: YunFeng Ma


start-server.bat fails to start server if there is a space in the install path, 
but startup.bat works fine.  Looks like it's an Ant bug.

H:\myf\Apache Geronimo\bin>start-server.bat
---
constituent[0]: file:/H:/myf/Apache Geronimo/etc/
constituent[1]: file:/H:/myf/Apache Geronimo/lib/gshell/geronimo-commands-2.1-SN
APSHOT.jar
constituent[2]: file:/H:/myf/Apache Geronimo/repository/org/apache/ant/ant/1.7.0
/ant-1.7.0.jar
constituent[3]: file:/H:/myf/Apache Geronimo/repository/org/apache/ant/ant-launc
her/1.7.0/ant-launcher-1.7.0.jar
constituent[4]: file:/H:/myf/Apache Geronimo/repository/org/apache/geronimo/gshe
ll/gshell-cli/1.0-alpha-1-SNAPSHOT/gshell-cli-1.0-alpha-1-SNAPSHOT.jar
constituent[5]: file:/H:/myf/Apache Geronimo/repository/org/apache/geronimo/gshe
ll/gshell-embeddable/1.0-alpha-1-SNAPSHOT/gshell-embeddable-1.0-alpha-1-SNAPSHOT
.jar
constituent[6]: file:/H:/myf/Apache Geronimo/repository/org/apache/geronimo/gshe
ll/remote/gshell-remote-client/1.0-alpha-1-SNAPSHOT/gshell-remote-client-1.0-alp
ha-1-SNAPSHOT.jar
constituent[7]: file:/H:/myf/Apache Geronimo/repository/org/apache/geronimo/gshe
ll/remote/gshell-remote-common/1.0-alpha-1-SNAPSHOT/gshell-remote-common-1.0-alp
ha-1-SNAPSHOT.jar
constituent[8]: file:/H:/myf/Apache Geronimo/repository/org/apache/geronimo/gshe
ll/remote/gshell-remote-server/1.0-alpha-1-SNAPSHOT/gshell-remote-server-1.0-alp
ha-1-SNAPSHOT.jar
constituent[9]: file:/H:/myf/Apache Geronimo/repository/org/apache/geronimo/gshe
ll/gshell-whisper/1.0-alpha-1-SNAPSHOT/gshell-whisper-1.0-alpha-1-SNAPSHOT.jar
constituent[10]: file:/H:/myf/Apache Geronimo/repository/org/apache/mina/mina-co
re/1.1.2/mina-core-1.1.2.jar
constituent[11]: file:/H:/myf/Apache Geronimo/repository/org/apache/mina/mina-fi
lter-ssl/1.1.2/mina-filter-ssl-1.1.2.jar
constituent[12]: file:/H:/myf/Apache Geronimo/repository/org/codehaus/groovy/gro
ovy-all/1.1-rc-1/groovy-all-1.1-rc-1.jar
constituent[13]: file:/H:/myf/Apache Geronimo/repository/org/slf4j/slf4j-log4j12
/1.4.3/slf4j-log4j12-1.4.3.jar
constituent[14]: file:/H:/myf/Apache Geronimo/repository/org/slf4j/jcl104-over-s
lf4j/1.4.3/jcl104-over-slf4j-1.4.3.jar
constituent[15]: file:/H:/myf/Apache Geronimo/lib/geronimo-kernel-2.1-SNAPSHOT.j
ar
constituent[16]: file:/H:/myf/Apache Geronimo/lib/log4j-1.2.14.jar
constituent[17]: file:/H:/myf/Apache Geronimo/lib/cglib-nodep-2.1_3.jar
constituent[18]: file:/H:/myf/Apache Geronimo/repository/org/apache/geronimo/spe
cs/geronimo-javaee-deployment_1.1MR3_spec/1.0/geronimo-javaee-deployment_1.1MR3_
spec-1.0.jar
constituent[19]: file:/H:/myf/Apache Geronimo/repository/org/apache/geronimo/mod
ules/geronimo-cli/2.1-SNAPSHOT/geronimo-cli-2.1-SNAPSHOT.jar
constituent[20]: file:/H:/myf/Apache Geronimo/repository/org/apache/geronimo/mod
ules/geronimo-deploy-config/2.1-SNAPSHOT/geronimo-deploy-config-2.1-SNAPSHOT.jar

constituent[21]: file:/H:/myf/Apache Geronimo/repository/org/apache/geronimo/mod
ules/geronimo-deploy-jsr88/2.1-SNAPSHOT/geronimo-deploy-jsr88-2.1-SNAPSHOT.jar
constituent[22]: file:/H:/myf/Apache Geronimo/repository/org/apache/geronimo/mod
ules/geronimo-deploy-tool/2.1-SNAPSHOT/geronimo-deploy-tool-2.1-SNAPSHOT.jar
constituent[23]: file:/H:/myf/Apache Geronimo/repository/org/apache/geronimo/mod
ules/geronimo-system/2.1-SNAPSHOT/geronimo-system-2.1-SNAPSHOT.jar
constituent[24]: file:/H:/myf/Apache Geronimo/repository/org/apache/geronimo/mod
ules/geronimo-plugin/2.1-SNAPSHOT/geronimo-plugin-2.1-SNAPSHOT.jar
constituent[25]: file:/H:/myf/Apache Geronimo/repository/org/apache/geronimo/mod
ules/geronimo-common/2.1-SNAPSHOT/geronimo-common-2.1-SNAPSHOT.jar
constituent[26]: file:/H:/myf/Apache Geronimo/repository/org/codehaus/plexus/ple
xus-archiver/1.0-alpha-7/plexus-archiver-1.0-alpha-7.jar
constituent[27]: file:/H:/myf/Apache Geronimo/repository/org/codehaus/plexus/ple
xus-utils/1.4.1/plexus-utils-1.4.1.jar
---
java.lang.IllegalArgumentException
at java.net.URI.create(URI.java:842)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.apache.tools.ant.launch.Locator.fromURI(Locator.java:162)
at org.apache.tools.ant.launch.Locator.getResourceS

[jira] Created: (GERONIMO-3857) response header parsing is done incorrectly

response header parsing is done incorrectly
---

 Key: GERONIMO-3857
 URL: https://issues.apache.org/jira/browse/GERONIMO-3857
 Project: Geronimo
  Issue Type: Bug
  Security Level: public (Regular issues)
  Components: AsyncHttpClient
Affects Versions: 1.x
Reporter: Sangjin Lee
Assignee: Rick McGuire


When we decode response headers, HttpDecoder separates name from value using ": 
" (note the *single*space after the colon).  This is incorrect.  The HTTP spec 
says

- The field value MAY be preceded by any amount of LWS, though a single SP is 
preferred.

The separator pattern should be simply ":".  Then any preceding or trailing 
LWSP characters (SP or HT) should be removed from the value.  This is a rather 
critical issue.  I had headers like 

Server: Foo
Content-Length:62
Connection: close

(notice lack of space after "Content-Length:")

HttpResponseDecoder cannot properly parse the above headers, and throws a 
StringIndexOutOfBoundsException.



-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Created: (GERONIMODEVTOOLS-283) Refactoring a Dynamic Web Project's name doesn't refactor it's artifact id & context root

Refactoring a Dynamic Web Project's name doesn't refactor it's artifact id & 
context root
-

 Key: GERONIMODEVTOOLS-283
 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-283
 Project: Geronimo-Devtools
  Issue Type: Wish
  Components: eclipse-plugin
Reporter: Shiva Kumar H R
Priority: Minor
 Fix For: 2.1.0


When a Dynamic Web Project with name say "tt" is created, a Geronimo deployment 
plan "geronimo-web.xml" will get created with module-id as "default/tt-1.0.car" 
and context-root as "/tt". 

When this project is re-factored to say "tz", the module-id will still be the 
same "default/tt-1.0.car" (note that artifact id is not re-factored from "tt" 
to "tz"). The context-root also remains the same "/tt". 

Although this doesn't pose any problem, wouldn't it be better to refactor the 
artifact-id & context-root to match the project name?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: [VOTE] Geronimo Server 2.1 and Geronimo TxManager 2.1.1 Releases

Hmm this seems bad. I was able to reproduce the problem on port 8443
only but _all_ portlets failed in this way. So the console is pretty
much unusable on port 8443. Can somebody else verify these findings?

Jarek

On Thu, Feb 14, 2008 at 1:43 PM, Paul McMahan <[EMAIL PROTECTED]> wrote:
> Good question :-)   I opened:
>  https://issues.apache.org/jira/browse/GERONIMO-3855
>
>  Best wishes,
>  Paul
>
>
>
>
>  On Feb 14, 2008, at 1:32 PM, Jacek Laskowski wrote:
>
>  > On Thu, Feb 14, 2008 at 6:00 AM, Paul McMahan
>  > <[EMAIL PROTECTED]> wrote:
>  >
>  >>  Looks good except for the Plugins portlet which is not working for
>  >>  me.  Several actions in that portlet lead to:
>  >>  javax.portlet.PortletSecurityException: No Supported
>  >
>  > Hi Paul,
>  >
>  > Have you reported it in JIRA? I could find any emails from jira
>  > about it.
>  >
>  > Jacek
>  >
>  > --
>  > Jacek Laskowski
>  > http://www.JacekLaskowski.pl
>
>

[jira] Commented: (GERONIMO-3855) PortletSecurityException in Plugins portlet


[ 
https://issues.apache.org/jira/browse/GERONIMO-3855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12569183#action_12569183
 ] 

Jarek Gawor commented on GERONIMO-3855:
---

I was able to reproduce this problem only on port 8443 (works fine on 8080) but 
what's worse is that all portlets fail in this way.


> PortletSecurityException in Plugins portlet
> ---
>
> Key: GERONIMO-3855
> URL: https://issues.apache.org/jira/browse/GERONIMO-3855
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: console
>Affects Versions: 2.1
>Reporter: Paul McMahan
>
> Cannot take any actions in the Plugins portlet.
> Recreate:
> Go to the Plugins portlet in the admin console
> Click any action-- "Update Repository List" or "Add Repository" or "Export a 
> Plugin" or "Assemble a Server"
> Note the exception:
> javax.servlet.ServletException: javax.portlet.PortletSecurityException: No 
> Supported
>   
> org.apache.pluto.driver.PortalDriverServlet.doGet(PortalDriverServlet.java:116)
>   
> org.apache.pluto.driver.PortalDriverServlet.doPost(PortalDriverServlet.java:158)
>   javax.servlet.http.HttpServlet.service(HttpServlet.java:713)
>   javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
> root cause
> javax.portlet.PortletSecurityException: No Supported
>   
> org.apache.pluto.driver.services.container.PortletURLProviderImpl.setSecure(PortletURLProviderImpl.java:67)
>   
> org.apache.pluto.core.PortletContainerImpl.doAction(PortletContainerImpl.java:261)
>   
> org.apache.pluto.driver.PortalDriverServlet.doGet(PortalDriverServlet.java:112)
>   
> org.apache.pluto.driver.PortalDriverServlet.doPost(PortalDriverServlet.java:158)
>   javax.servlet.http.HttpServlet.service(HttpServlet.java:713)
>   javax.servlet.http.HttpServlet.service(HttpServlet.java:806)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Resolved: (GERONIMO-3802) In plugin installer, assembling a server, add a page at the end to confirm or deny the assembly of a server package.


 [ 
https://issues.apache.org/jira/browse/GERONIMO-3802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jarek Gawor resolved GERONIMO-3802.
---

   Resolution: Fixed
Fix Version/s: 2.1.1

I resolved the problem by making PluginInfoBean serializable. I committed this 
change to trunk (revision 627948).

I also committed the patch with the serializable fix to branches/2.1 (revision 
627951).


> In plugin installer, assembling a server, add a page at the end to confirm or 
> deny the assembly of a server package.
> 
>
> Key: GERONIMO-3802
> URL: https://issues.apache.org/jira/browse/GERONIMO-3802
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: console
>Affects Versions: 2.1, 2.1.1, 2.2
>Reporter: Joseph Leong
>Assignee: Jarek Gawor
>Priority: Minor
> Fix For: 2.1.1, 2.2
>
> Attachments: GERONIMO-3802.patch
>
>
> Add a type of confirmation page at the end of Assembling a server to inform 
> the user whether the creation of there server was successful or not.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[RESULT] [VOTE] Geronimo Server 2.1 and Geronimo TxManager 2.1.1 Releases

2008-02-14 Thread Kevan Miller

All,
This vote passes with 16 +1 votes and no others.

Woo hoo! Great work everybody!

I'll get to work getting the binaries pushed out. Takes a while for
syncing with the Apache mirrors. So, will be a couple days before set
things up on our web site.

Meantime, let's keep going with the doc updates. I'm planning on
spending time tomorrow and over the weekend contributing what I'm able.

--kevan

On Feb 10, 2008, at 10:46 PM, Kevan Miller wrote:

All,
I've prepared a 2.1 release candidate for your review and vote. I've
also prepared a 2.1.1 TxManager release candidate for review and
vote. For simplicity, I'm holding a single vote for both releases.
The Geronimo server release is dependent upon the TxManager 2.1.1
release.

The source for the Geronimo 2.1 release currently resides here:
https://svn.apache.org/repos/asf/geronimo/server/branches/2.1.0

When the release vote is approved, I will svn mv the code to
https://svn.apache.org/repos/asf/geronimo/server/tags/2.1.0

An archive of this source code can be found here:
http://people.apache.org/~kevan/release-votes/G-2.1/geronimo-2.1-dist/geronimo-2.1-src.tar.gz

http://people.apache.org/~kevan/release-votes/G-2.1/geronimo-2.1-
dist/ contains the 8 Java EE and Minimal server binary distributions
to be released (tomcat/jetty, Java EE/Minimal, tar/zip) as well as
the RELEASE_NOTES and source code archives for the release.

For your convenience, here are pointers to the urls for the
distributions in zip format:

http://people.apache.org/~kevan/release-votes/G-2.1/geronimo-2.1-dist/geronimo-jetty6-javaee5-2.1-bin.zip
http://people.apache.org/~kevan/release-votes/G-2.1/geronimo-2.1-dist/geronimo-jetty6-minimal-2.1-bin.zip
http://people.apache.org/~kevan/release-votes/G-2.1/geronimo-2.1-dist/geronimo-tomcat6-javaee5-2.1-bin.zip
http://people.apache.org/~kevan/release-votes/G-2.1/geronimo-2.1-dist/geronimo-tomcat6-minimal-2.1-bin.zip

The maven artifacts for the release can be found here:
http://people.apache.org/~kevan/release-votes/G-2.1/geronimo-2.1/

or in the following archive (warning, this file is 458 megs):
http://people.apache.org/~kevan/release-votes/G-2.1/geronimo-2.1-dist.tar.gz

When the release vote is approved, these maven artifacts will be
moved to the m2-ibiblio-rsync-repository at Apache.

Due to the discovery of a bug in the Connector component of Geronimo
TxManager, a new release of TxManager was needed. TxManager 2.1.1 is
also part of this vote.

The source code for the TxManager 2.1.1 release can be found here:
https://svn.apache.org/repos/asf/geronimo/components/txmanager/tags/geronimo-txmanager-parent-2.1.1

The maven artifacts for TxManager 2.1.1 can be found here:
http://people.apache.org/~kevan/release-votes/G-2.1/geronimo-txmanager-2.1.1/

When the release vote is approved, these maven artifacts will be
moved to the m2-ibiblio-rsync-repository at Apache.

Please review these releases and register your vote.

[ ] +1 Release Geronimo 2.1 and TxManager 2.1.1
[ ] 0 No opinion
[ ] -1 Do not release Geronimo 2.1 and TxManager 2.1.1 (please
provide rationale)

I'll plan on calling this vote on Wednesday evening (11 PM EST).

--kevan

[jira] Commented: (GERONIMO-3807) ERROR's logged during plugin installation for non-existent plugins


[ 
https://issues.apache.org/jira/browse/GERONIMO-3807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12569172#action_12569172
 ] 

Jarek Gawor commented on GERONIMO-3807:
---

Well, I think this should be a code change. These errors are logged by 
PluginInstallerGBean.validatePlugin() The validatePlugin() method is for 
example called from the plugin portlet. For example, if we use the portlet to 
_list_ plugins from repository that contains older geronimo plugins these 
errors will be logged. But all the portlet is doing is just checking if a given 
can be installed on this version of Geronimo or not. That should not result in 
an error message to be logged. Maybe we should just change the log.error() call 
to log.debug() or .info() and change the message to say that a given plugin 'is 
not installable'. Or we can just totally remove that log statement.


> ERROR's logged during plugin installation for non-existent plugins
> --
>
> Key: GERONIMO-3807
> URL: https://issues.apache.org/jira/browse/GERONIMO-3807
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>Affects Versions: 2.1
>Reporter: Kevan Miller
> Fix For: Wish List
>
>
> I brought up the console screen to install plugins and had a number of 
> ERROR's logged of the following form:
> 21:36:07,628 ERROR [PluginInstallerGBean] Cannot install plugin 
> org.apache.geronimo.framework/geronimo-gbean-deployer-bootstrap/2.2-SNAPSHOT/car
>  on Geronimo 2.1-SNAPSHOT
> 21:36:07,722 ERROR [PluginInstallerGBean] Cannot install plugin 
> org.apache.geronimo.framework/j2ee-system/2.2-SNAPSHOT/car on Geronimo 
> 2.1-SNAPSHOT
> 21:36:07,723 ERROR [PluginInstallerGBean] Cannot install plugin 
> org.apache.geronimo.framework/xmlbeans/2.2-SNAPSHOT/car on Geronimo 
> 2.1-SNAPSHOT
> ...
> Presumably because the 2.2-SNAPSHOT plugins were registered in 
> ~/.m2/repository/geronimo-plugins.xml, but they are not in my repository.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Resolved: (GERONIMO-3854) deploy/assemble and ERROR GroovyRuntimeException: Ambiguous method overloading for method org.apache.geronimo.kernel.repository.Artifact#


 [ 
https://issues.apache.org/jira/browse/GERONIMO-3854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jarek Gawor resolved GERONIMO-3854.
---

   Resolution: Fixed
Fix Version/s: 2.2
   2.1.1

I changed the gshell command to prompt for the artifact name if the name was 
not specified on the command line. I also set the version to default to 1.0.

Changes committed to trunk (revision 627938) and branches/2.1 (revision 627939).


> deploy/assemble and ERROR GroovyRuntimeException: Ambiguous method 
> overloading for method org.apache.geronimo.kernel.repository.Artifact#
> ---
>
> Key: GERONIMO-3854
> URL: https://issues.apache.org/jira/browse/GERONIMO-3854
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: general
>Affects Versions: 2.1
>Reporter: Jacek Laskowski
>Assignee: Jarek Gawor
> Fix For: 2.1.1, 2.2
>
>
> [EMAIL PROTECTED]:/> deploy/assemble
> Listing configurations from Geronimo server
> Connecting to Geronimo server: localhost:1099
> Username: system
> Password: ***
> Connection established
> 
>  1:  Geronimo Plugins, Monitoring :: Agent DataSource (2.1)
>  2:  Geronimo Plugins, Monitoring :: Console DataSource (2.1)
> Administration
>  3:  Geronimo Plugins, Console :: Jetty (2.1)
>  4:  Geronimo Plugins, Console :: Plugin and Deployment Portlets
> (Jetty) (2.1)
>  5:  Geronimo Plugins, Welcome :: Jetty (2.1)
> Clustering
>  6:  Geronimo Plugins, Clustering :: Clustering (2.1)
>  7:  Geronimo Plugins, Clustering :: Farming (2.1)
>  8:  Geronimo Plugins, Clustering :: WADI (2.1)
> Connector
>  9:  Geronimo Plugins, Connector :: Deployer (2.1)
> Databases
>  10: Geronimo Plugins, System Database :: Console (Jetty) (2.1)
> Debug
>  11: Geronimo Plugins, Debug Views :: Jetty (2.1)
> Deployment
>  12: Geronimo Framework, Configs :: CLI Upgrade (2.1)
>  13: Geronimo Framework, Configs :: JSR-88 CLI (2.1)
>  14: Geronimo Framework, Configs :: JSR-88 DeploymentFactory (2.1)
>  15: Geronimo Framework, Configs :: Offline Deployer (2.1)
>  16: Geronimo Framework, Configs :: Online Deployer (2.1)
>  17: Geronimo Plugins, J2EE :: JSR-88 EAR Configurer (2.1)
>  18: Geronimo Plugins, J2EE :: JSR-88 JAR Configurer (2.1)
>  19: Geronimo Plugins, J2EE :: JSR-88 RAR Configurer (2.1)
>  20: Geronimo Plugins, J2EE :: JSR-88 WAR Configurer (2.1)
>  21: Geronimo Plugins, Remote Deploy :: Jetty (2.1)
> Development tools
>  22: Geronimo Plugins, Plan Creator :: Jetty (2.1)
> EJB
>  23: Geronimo Plugins, Corba :: Yoko ORB (2.1)
>  24: Geronimo Plugins, MEJB :: Config (2.1)
> EJB Container
>  25: Geronimo Plugins, Corba :: Deployer (2.1)
>  26: Geronimo Plugins, OpenEJB :: Deployer (2.1)
>  27: Geronimo Plugins, OpenEJB :: OpenEJB (2.1)
> Example
>  28: Geronimo Plugins, Shared Library (2.1)
> Fluff
>  29: Geronimo Plugins, Hot Deploy :: Deployer (2.1)
> Geronimo Core
>  30: Geronimo Assemblies :: Boilerplate Minimal (2.1)
>  31: Geronimo Framework, Configs :: Client System (2.1)
>  32: Geronimo Framework, Configs :: GBean Deployer (2.1)
>  33: Geronimo Framework, Configs :: J2EE System (2.1)
>  34: Geronimo Framework, Configs :: Plugin Management (2.1)
>  35: Geronimo Framework, Configs :: RMI Naming (2.1)
>  36: Geronimo Framework, Configs :: Shutdown (2.1)
>  37: Geronimo Framework, Configs :: Transformer Agent (2.1)
>  38: Geronimo Framework, Configs :: XMLBeans (2.1)
>  39: Geronimo Plugins, Client :: Client (2.1)
>  40: Geronimo Plugins, Client :: Deployer (2.1)
>  41: Geronimo Plugins, Client :: Security (2.1)
>  42: Geronimo Plugins, Connector :: Client transaction (2.1)
>  43: Geronimo Plugins, Connector :: Transaction Manager (JTA11) (2.1)
>  44: Geronimo Plugins, Corba :: Client Yoko (2.1)
>  45: Geronimo Plugins, Spring (2.1)
>  46: Geronimo Plugins, System Database :: System Database (2.1)
> JMS
>  47: Geronimo Plugins, ActiveMQ :: Broker (2.1)
>  48: Geronimo Plugins, ActiveMQ :: Console (Jetty) (2.1)
>  49: Geronimo Plugins, ActiveMQ :: Resource Adapter (2.1)
> JavaEE
>  50: Geronimo Framework, Configs :: JavaEE Specs (2.1)
>  51: Geronimo Plugins, J2EE :: Server (2.1)
>  52: Geronimo Plugins, JavaMail :: JavaMail (2.1)
> JavaEE deployment
>  53: Geronimo Plugins, J2EE :: Deployer (2.1)
>  54: Geronimo Plugins, Jasper :: Deployer (2.1)
> Jetty
>  55: Geronimo Plugins, Jetty :: Clustering Builder for WADI (2.1)
>  56: Geronimo Plugins, Jetty :: Deployer (2.1)
>  57: Geronimo Plugins, Jetty :: Jetty 6 (2.1)
>  58:

Re: Concurrency Utilities for Java EE

2008-02-14 Thread Gianny Damour


Hi,

This is really great news.

I very quickly browsed the specifications and I have a couple of  
questions:
1. Is there a way to define task dependencies? For instance, I should  
be able to queue a task B which will only be executed after the  
execution of task A as task B depends on task A's outputs.
2. Is there a way to specify routing strategies for distributable  
tasks? For instance, as an application developer, I would like to  
have an API to route my tasks to specific slaves.
3. Is there a way to transparently fail-over a non started task to  
another slave if the slave becomes unavailable?


Let me know if you need some helps to implement task distribution.  
FWIW, WADI has a simple distributed service invocation framework (see  
http://wadi.codehaus.org/wadi-core/apidocs/index.html - start with  
ServiceProxyFactory) which could be quite useful.


Thanks,
Gianny

On 15/02/2008, at 4:06 AM, Jarek Gawor wrote:


Folks,

For the past few weeks I've been working on the Concurrency Utilities
for Java EE specification implementation. The Concurrency Utilities
for Java EE specification is a draft specification (see
http://gee.cs.oswego.edu/dl/concurrencyee-interest/ for more info)
that is supposed to replace the JSR-236 (Timer API) and JSR-237 (Work
Manager API) specifications and become part of Java EE 6.  The
Concurrency Utilities for Java EE specification basically extends the
java.util.concurrent.Executor API and adds managed environment
qualities to the tasks executed via the Executor. That is, the
background tasks can execute with the same environment as the
application that started it.

I have a little bit of code but it's definitely not complete or fully
functional and still needs a lot of work (e.g. better integration with
Geronimo, etc.). I would like to donate this code to Geronimo, and
continue to work on it there as a community.

Now, the cool thing is that this implementation might become the
official Reference Implementation (RI) for this spec. I've talked with
the IBM co-spec lead and there is a good chance of that happening if
we also commit to writing a TCK for it. And I think that would be a
great opportunity for Geronimo to show some leadership in the Java EE
spec area.

Even if the RI thing does not work out or this specification does not
become part of Java EE 6, I still think this functionally would be a
good addition to Geronimo.

What do people think? Thoughts, any concerns?

Jarek

Re: framework assembly distribution?

2008-02-14 Thread Donald Woods

-Donald

Kevan Miller wrote:

On Feb 14, 2008, at 12:03 PM, David Jencks wrote:

On Feb 14, 2008, at 8:30 AM, Joe Bohn wrote:

With our 2.1 distribution (as with earlier distributions) we are only
providing the javaee5 & minimal assemblies. Are we ever planning to
make the geronimo-framework assembly available in a distribution so
that a user could start from scratch (not even a web container) and
build up a server by installing plugins?

That was the original intent when we created this assembly. I know
that the originally framework included enough deployment capability
to deploy plugins. However, I'm not certain that is still the case
(I haven't tried in a long time). Assuming you can still install
plugins (or we add that back in), I think it makes sense to
distribute this assembly. BTW, I'm not proposing this for 2.1 given
that it is nearly completely baked.

All the framework assembly can do is install plugins. I think we
should definitely distribute it in the future and I am proposing we
distribute it for 2.1 as well. IIUC in any case it will get into the
maven repos, so adding it to the official download page shouldn't be
too hard.

Agreed. We are releasing the framework assembly. It's part of the binary
artifacts in our maven repo --
http://people.apache.org/~kevan/release-votes/G-2.1/geronimo-2.1/org/apache/geronimo/assemblies/geronimo-framework/2.1/

Simple matter, IMO, to also include in the distribution page. IMO, a
vote isn't necessary (as it's already covered by the existing 2.1 vote).
I'll give this a bit of time, to see if there are contrary opinions.
Assuming, the 2.1 vote passes and there aren't any objections, I'll set
up framework in the distribution directory, also.

--kevan

smime.p7s
Description: S/MIME Cryptographic Signature

Re: [jira] Commented: (GERONIMO-3802) In plugin installer, assembling a server, add a page at the end to confirm or deny the assembly of a server package.

You mean rev 627838? Yes, was planning to but discovered a small problem.

Jarek

On Thu, Feb 14, 2008 at 2:24 PM, Donald Woods <[EMAIL PROTECTED]> wrote:
> Are you also going to check this into the 2.1 branch?  The JIRA shows
>  that it was fixed for 2.1.1, but trunk is 2.2.
>
>  -Donald
>
>
>  Jarek Gawor (JIRA) wrote:
>  > [ 
> https://issues.apache.org/jira/browse/GERONIMO-3802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12569043#action_12569043
>  ]
>  >
>  > Jarek Gawor commented on GERONIMO-3802:
>  > ---
>  >
>  > Committed the patch to trunk (revision 627838). Thanks!
>  >
>  > I've noticed a few more minor issues that can be improved with the portlet:
>  >
>  > 1) At minimum the user should provide an artifact id otherwise assembly 
> named --bin.tar.gz will be created. The portlet should check for empty 
> artifact id.
>  >
>  > 2) If no plugins are selected and 'assemble' button is pressed a nasty 
> exception will be displayed. The portlet should check if at least one plugin 
> was selected.
>  >
>  > 3) On the confirmation screen and on Windows the server path location will 
> contain / and \. For example c:\geronimo/var/temp/foo.tar.gz.
>  >
>  >
>  >
>  >> In plugin installer, assembling a server, add a page at the end to 
> confirm or deny the assembly of a server package.
>  >> 
> 
>  >>
>  >> Key: GERONIMO-3802
>  >> URL: https://issues.apache.org/jira/browse/GERONIMO-3802
>  >> Project: Geronimo
>  >>  Issue Type: Improvement
>  >>  Security Level: public(Regular issues)
>  >>  Components: console
>  >>Affects Versions: 2.1, 2.1.1
>  >>Reporter: Joseph Leong
>  >>Assignee: Jarek Gawor
>  >>Priority: Minor
>  >> Fix For: 2.1.1
>  >>
>  >> Attachments: GERONIMO-3802.patch
>  >>
>  >>
>  >> Add a type of confirmation page at the end of Assembling a server to 
> inform the user whether the creation of there server was successful or not.
>  >
>

Re: [jira] Commented: (GERONIMO-3802) In plugin installer, assembling a server, add a page at the end to confirm or deny the assembly of a server package.

2008-02-14 Thread Donald Woods

Are you also going to check this into the 2.1 branch?  The JIRA shows 
that it was fixed for 2.1.1, but trunk is 2.2.


-Donald


Jarek Gawor (JIRA) wrote:
[ https://issues.apache.org/jira/browse/GERONIMO-3802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12569043#action_12569043 ] 


Jarek Gawor commented on GERONIMO-3802:
---

Committed the patch to trunk (revision 627838). Thanks!

I've noticed a few more minor issues that can be improved with the portlet:

1) At minimum the user should provide an artifact id otherwise assembly named --bin.tar.gz will be created. The portlet should check for empty artifact id. 


2) If no plugins are selected and 'assemble' button is pressed a nasty 
exception will be displayed. The portlet should check if at least one plugin 
was selected.

3) On the confirmation screen and on Windows the server path location will 
contain / and \. For example c:\geronimo/var/temp/foo.tar.gz.




In plugin installer, assembling a server, add a page at the end to confirm or 
deny the assembly of a server package.


Key: GERONIMO-3802
URL: https://issues.apache.org/jira/browse/GERONIMO-3802
Project: Geronimo
 Issue Type: Improvement
 Security Level: public(Regular issues) 
 Components: console

   Affects Versions: 2.1, 2.1.1
   Reporter: Joseph Leong
   Assignee: Jarek Gawor
   Priority: Minor
Fix For: 2.1.1

Attachments: GERONIMO-3802.patch


Add a type of confirmation page at the end of Assembling a server to inform the 
user whether the creation of there server was successful or not.




smime.p7s
Description: S/MIME Cryptographic Signature

[BUILD] 2.2: Failed for Revision: 627860

2008-02-14 Thread gawor

Geronimo Revision: 627860 built with tests included
 
See the full build-1500.log file at 
http://geronimo.apache.org/maven/server/binaries/trunk/20080214/build-1500.log
 
Download the binaries from 
http://geronimo.apache.org/maven/server/binaries/trunk/20080214
[INFO] BUILD SUCCESSFUL
[INFO] 
[INFO] Total time: 30 minutes 16 seconds
[INFO] Finished at: Thu Feb 14 15:48:32 EST 2008
[INFO] Final Memory: 304M/994M
[INFO] 
 
TESTSUITE RESULTS (Failures only)
=
See detailed results at 
http://geronimo.apache.org/maven/server/testsuite/ResultsSummary.html
 
Assembly: tomcat
=
See the full test.log file at 
http://geronimo.apache.org/maven/server/binaries/trunk/20080214/logs-1500-tomcat/test.log
 
 
Assembly: jetty
=
See the full test.log file at 
http://geronimo.apache.org/maven/server/binaries/trunk/20080214/logs-1500-jetty/test.log
 
[INFO] Running console-testsuite.advance-test
[INFO] Tests run: 13, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 71.556 
sec <<< FAILURE!

[jira] Commented: (GERONIMO-3836) Deployment fails with FNFE due to missing jline_.dll on Cygwin


[ 
https://issues.apache.org/jira/browse/GERONIMO-3836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12569111#action_12569111
 ] 

Jarek Gawor commented on GERONIMO-3836:
---

I was able to replicate this problem with cygwin but not gsh. And the problem 
seemed to be related to the GERONIMO_TMPDIR which deploy.sh sets. 

I changed one line in deploy.sh from:

GERONIMO_TMPDIR=var/temp

to:

GERONIMO_TMPDIR=$GERONIMO_HOMEvar/temp

deploy.sh worked fine in cygwin. 

But I'm not really sure why this is a problem now.


> Deployment fails with FNFE due to missing jline_.dll on Cygwin
> --
>
> Key: GERONIMO-3836
> URL: https://issues.apache.org/jira/browse/GERONIMO-3836
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: deployment
>Affects Versions: 2.2
>Reporter: Jacek Laskowski
>
> Meant to deploy a webapp from a directory outside Geronimo's installation 
> dir. Deployer worked with -u and -p options although it spit FNFE exception, 
> but it failed without them.
> [EMAIL PROTECTED] 
> /cygdrive/c/apps/apache-wicket/src/jdk-1.5/wicket-examples/target
> $ c\:/geronimo/bin/deploy.sh -u system -p manager deploy wicket-examples.war
> Using GERONIMO_BASE:   c:\geronimo
> Using GERONIMO_HOME:   c:\geronimo
> Using GERONIMO_TMPDIR: 
> c:\apps\apache-wicket\src\jdk-1.5\wicket-examples\target\var\temp
> Using JRE_HOME:c:\apps\java5\jre
> java.io.FileNotFoundException: 
> c:\apps\apache-wicket\src\jdk-1.5\wicket-examples\target\var\temp\jline_.dll 
> (The system cannot find the path specified)
> at java.io.FileOutputStream.open(Native Method)
> at java.io.FileOutputStream.(FileOutputStream.java:179)
> at java.io.FileOutputStream.(FileOutputStream.java:131)
> at jline.WindowsTerminal.loadLibrary(WindowsTerminal.java:274)
> at jline.WindowsTerminal.initializeTerminal(WindowsTerminal.java:227)
> at jline.Terminal.setupTerminal(Terminal.java:77)
> at jline.Terminal.getTerminal(Terminal.java:28)
> at jline.ConsoleReader.(ConsoleReader.java:167)
> at jline.ConsoleReader.(ConsoleReader.java:162)
> at 
> org.apache.geronimo.deployment.cli.DeployTool.execute(DeployTool.java:164)
> at 
> org.apache.geronimo.kernel.util.MainConfigurationBootstrapper.main(MainConfigurationBootstrapper.java:45)
> at 
> org.apache.geronimo.cli.AbstractCLI.executeMain(AbstractCLI.java:67)
> at 
> org.apache.geronimo.cli.deployer.DeployerCLI.main(DeployerCLI.java:31)
> Deployed default/wicket-examples/1202695110250/war @
> /wicket-examples
> [EMAIL PROTECTED] 
> /cygdrive/c/apps/apache-wicket/src/jdk-1.5/wicket-examples/target
> $ c\:/geronimo/bin/deploy.sh undeploy 
> default/wicket-examples/1202695110250/war
> Using GERONIMO_BASE:   c:\geronimo
> Using GERONIMO_HOME:   c:\geronimo
> Using GERONIMO_TMPDIR: 
> c:\apps\apache-wicket\src\jdk-1.5\wicket-examples\target\var\temp
> Using JRE_HOME:c:\apps\java5\jre
> java.io.FileNotFoundException: 
> c:\apps\apache-wicket\src\jdk-1.5\wicket-examples\target\var\temp\jline_.dll 
> (The system cannot find the path specified)
> at java.io.FileOutputStream.open(Native Method)
> at java.io.FileOutputStream.(FileOutputStream.java:179)
> at java.io.FileOutputStream.(FileOutputStream.java:131)
> at jline.WindowsTerminal.loadLibrary(WindowsTerminal.java:274)
> at jline.WindowsTerminal.initializeTerminal(WindowsTerminal.java:227)
> at jline.Terminal.setupTerminal(Terminal.java:77)
> at jline.Terminal.getTerminal(Terminal.java:28)
> at jline.ConsoleReader.(ConsoleReader.java:167)
> at jline.ConsoleReader.(ConsoleReader.java:162)
> at 
> org.apache.geronimo.deployment.cli.InputPrompt.(InputPrompt.java:42)
> at 
> org.apache.geronimo.deployment.cli.ServerConnection.doAuthPromptAndRetry(ServerConnection.java:230)
> at 
> org.apache.geronimo.deployment.cli.ServerConnection.tryToConnect(ServerConnection.java:190)
> at 
> org.apache.geronimo.deployment.cli.ServerConnection.(ServerConnection.java:94)
> at 
> org.apache.geronimo.deployment.cli.DeployTool.execute(DeployTool.java:161)
> at 
> org.apache.geronimo.kernel.util.MainConfigurationBootstrapper.main(MainConfigurationBootstrapper.java:45)
> at 
> org.apache.geronimo.cli.AbstractCLI.executeMain(AbstractCLI.java:67)
> at 
> org.apache.geronimo.cli.deployer.DeployerCLI.main(DeployerCLI.java:31)
> Username: system
> Password: Error: Login Failed

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Reopened: (GERONIMO-3802) In plugin installer, assembling a server, add a page at the end to confirm or deny the assembly of a server package.


 [ 
https://issues.apache.org/jira/browse/GERONIMO-3802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jarek Gawor reopened GERONIMO-3802:
---


I think there is a smal problem with this change. I've noticed the following 
error on Tomcat on shutdown.

16:49:07,812 WARN  [[/plugin]] Cannot serialize session attribute javax.portlet.
p./plugin.ImportExport!1639862964|0?plugins for session ABF1AF9F9D32A15FE06C8DFC
5732C821
java.io.NotSerializableException: org.apache.geronimo.console.car.PluginInfoBean

at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1081)

at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:302)
at java.util.ArrayList.writeObject(ArrayList.java:569)
at sun.reflect.GeneratedMethodAccessor170.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)

Looks like PluginInfoBean objects are put into the session but the 
PluginInfoBean is not serializable.


> In plugin installer, assembling a server, add a page at the end to confirm or 
> deny the assembly of a server package.
> 
>
> Key: GERONIMO-3802
> URL: https://issues.apache.org/jira/browse/GERONIMO-3802
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: console
>Affects Versions: 2.1, 2.1.1, 2.2
>Reporter: Joseph Leong
>Assignee: Jarek Gawor
>Priority: Minor
> Fix For: 2.2
>
> Attachments: GERONIMO-3802.patch
>
>
> Add a type of confirmation page at the end of Assembling a server to inform 
> the user whether the creation of there server was successful or not.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (GERONIMO-3836) Deployment fails with FNFE due to missing jline_.dll on Cygwin

2008-02-14 Thread Jason Dillon (JIRA)


[ 
https://issues.apache.org/jira/browse/GERONIMO-3836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12569101#action_12569101
 ] 

Jason Dillon commented on GERONIMO-3836:


kay, I'll fire up my virtual machine and play.  Do you have the same problem in 
a non-cygwin-win32 environment?

> Deployment fails with FNFE due to missing jline_.dll on Cygwin
> --
>
> Key: GERONIMO-3836
> URL: https://issues.apache.org/jira/browse/GERONIMO-3836
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: deployment
>Affects Versions: 2.2
>Reporter: Jacek Laskowski
>
> Meant to deploy a webapp from a directory outside Geronimo's installation 
> dir. Deployer worked with -u and -p options although it spit FNFE exception, 
> but it failed without them.
> [EMAIL PROTECTED] 
> /cygdrive/c/apps/apache-wicket/src/jdk-1.5/wicket-examples/target
> $ c\:/geronimo/bin/deploy.sh -u system -p manager deploy wicket-examples.war
> Using GERONIMO_BASE:   c:\geronimo
> Using GERONIMO_HOME:   c:\geronimo
> Using GERONIMO_TMPDIR: 
> c:\apps\apache-wicket\src\jdk-1.5\wicket-examples\target\var\temp
> Using JRE_HOME:c:\apps\java5\jre
> java.io.FileNotFoundException: 
> c:\apps\apache-wicket\src\jdk-1.5\wicket-examples\target\var\temp\jline_.dll 
> (The system cannot find the path specified)
> at java.io.FileOutputStream.open(Native Method)
> at java.io.FileOutputStream.(FileOutputStream.java:179)
> at java.io.FileOutputStream.(FileOutputStream.java:131)
> at jline.WindowsTerminal.loadLibrary(WindowsTerminal.java:274)
> at jline.WindowsTerminal.initializeTerminal(WindowsTerminal.java:227)
> at jline.Terminal.setupTerminal(Terminal.java:77)
> at jline.Terminal.getTerminal(Terminal.java:28)
> at jline.ConsoleReader.(ConsoleReader.java:167)
> at jline.ConsoleReader.(ConsoleReader.java:162)
> at 
> org.apache.geronimo.deployment.cli.DeployTool.execute(DeployTool.java:164)
> at 
> org.apache.geronimo.kernel.util.MainConfigurationBootstrapper.main(MainConfigurationBootstrapper.java:45)
> at 
> org.apache.geronimo.cli.AbstractCLI.executeMain(AbstractCLI.java:67)
> at 
> org.apache.geronimo.cli.deployer.DeployerCLI.main(DeployerCLI.java:31)
> Deployed default/wicket-examples/1202695110250/war @
> /wicket-examples
> [EMAIL PROTECTED] 
> /cygdrive/c/apps/apache-wicket/src/jdk-1.5/wicket-examples/target
> $ c\:/geronimo/bin/deploy.sh undeploy 
> default/wicket-examples/1202695110250/war
> Using GERONIMO_BASE:   c:\geronimo
> Using GERONIMO_HOME:   c:\geronimo
> Using GERONIMO_TMPDIR: 
> c:\apps\apache-wicket\src\jdk-1.5\wicket-examples\target\var\temp
> Using JRE_HOME:c:\apps\java5\jre
> java.io.FileNotFoundException: 
> c:\apps\apache-wicket\src\jdk-1.5\wicket-examples\target\var\temp\jline_.dll 
> (The system cannot find the path specified)
> at java.io.FileOutputStream.open(Native Method)
> at java.io.FileOutputStream.(FileOutputStream.java:179)
> at java.io.FileOutputStream.(FileOutputStream.java:131)
> at jline.WindowsTerminal.loadLibrary(WindowsTerminal.java:274)
> at jline.WindowsTerminal.initializeTerminal(WindowsTerminal.java:227)
> at jline.Terminal.setupTerminal(Terminal.java:77)
> at jline.Terminal.getTerminal(Terminal.java:28)
> at jline.ConsoleReader.(ConsoleReader.java:167)
> at jline.ConsoleReader.(ConsoleReader.java:162)
> at 
> org.apache.geronimo.deployment.cli.InputPrompt.(InputPrompt.java:42)
> at 
> org.apache.geronimo.deployment.cli.ServerConnection.doAuthPromptAndRetry(ServerConnection.java:230)
> at 
> org.apache.geronimo.deployment.cli.ServerConnection.tryToConnect(ServerConnection.java:190)
> at 
> org.apache.geronimo.deployment.cli.ServerConnection.(ServerConnection.java:94)
> at 
> org.apache.geronimo.deployment.cli.DeployTool.execute(DeployTool.java:161)
> at 
> org.apache.geronimo.kernel.util.MainConfigurationBootstrapper.main(MainConfigurationBootstrapper.java:45)
> at 
> org.apache.geronimo.cli.AbstractCLI.executeMain(AbstractCLI.java:67)
> at 
> org.apache.geronimo.cli.deployer.DeployerCLI.main(DeployerCLI.java:31)
> Username: system
> Password: Error: Login Failed

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (GERONIMO-3844) Errors on shutdown from admin console (Jetty only) - java.lang.InterruptedException

2008-02-14 Thread Joe Bohn (JIRA)


[ 
https://issues.apache.org/jira/browse/GERONIMO-3844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12569091#action_12569091
 ] 

Joe Bohn commented on GERONIMO-3844:


Loooks like this isn't an issue with the 2.1 branch either.   Next stop is to 
try building the tag myself and see if I still hit it there.


> Errors on shutdown from admin console (Jetty only) - 
> java.lang.InterruptedException
> ---
>
> Key: GERONIMO-3844
> URL: https://issues.apache.org/jira/browse/GERONIMO-3844
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: console, Jetty
>Affects Versions: 2.1
> Environment: Jetty Java EE 5 assembly
>Reporter: Joe Bohn
>
> When shutting down Geronimo from the Admin console in the Jetty Assembly we 
> get the following exceptions:
> 13:23:19,474 ERROR [TcpTransportServer] Could not stop service: 
> tcp://0.0.0.0:61616. Reason: java.lang.InterruptedException
> java.lang.InterruptedException
> at java.lang.Object.wait(Native Method)
> at java.lang.Thread.join(Thread.java:1113)
> at java.lang.Thread.join(Thread.java:1166)
> at 
> org.apache.activemq.transport.TransportServerThreadSupport.doStop(TransportServerThreadSupport.java:81)
> at 
> org.apache.activemq.transport.tcp.TcpTransportServer.doStop(TcpTransportServer.java:219)
> at 
> org.apache.activemq.util.ServiceSupport.stop(ServiceSupport.java:58)
> at 
> org.apache.activemq.util.ServiceStopper.stop(ServiceStopper.java:42)
> at 
> org.apache.activemq.broker.TransportConnector.stop(TransportConnector.java:241)
> at 
> org.apache.geronimo.activemq.TransportConnectorGBeanImpl.doStop(TransportConnectorGBeanImpl.java:135)
> at 
> org.apache.geronimo.gbean.runtime.GBeanInstance.destroyInstance(GBeanInstance.java:1161)
> at 
> org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStop(GBeanInstanceState.java:339)
> at 
> org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:188)
> at 
> org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:563)
> at 
> org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:423)
> at 
> org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:180)
> at 
> org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:563)
> at 
> org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:423)
> at 
> org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:180)
> at 
> org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:563)
> at 
> org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:423)
> at 
> org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:180)
> at 
> org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:563)
> at 
> org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:423)
> at 
> org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:180)
> at 
> org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:563)
> at 
> org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:423)
> at 
> org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:180)
> at 
> org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:563)
> at 
> org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:423)
> at 
> org.apache.geronimo.kernel.config.KernelConfigurationManager$ShutdownHook.run(KernelConfigurationManager.java:316)
> at 
> org.apache.geronimo.kernel.basic.BasicKernel.notifyShutdownHooks(BasicKernel.java:668)
> at 
> org.apache.geronimo.kernel.basic.BasicKernel.shutdown(BasicKernel.java:645)
> at 
> org.apache.geronimo.console.servermanager.ServerManagerPortlet.doView(ServerManagerPortlet.java:74)
> at javax.portlet.GenericPortlet.doDispatch(GenericPortlet.java:247)
> at javax.portlet.GenericPortlet.render(GenericPortlet.java:175)
> at 
> org.apache.pluto.core.PortletServlet.dispatch(PortletServlet.java:208)
> at org.apache.pluto.core.PortletServlet.doGet(PortletServlet.java:139)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:693)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
> at 
> org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:487)
> at 
> org.apache.geronimo.jetty6.InternalJettyServletHolder.handl

[jira] Commented: (GERONIMO-3836) Deployment fails with FNFE due to missing jline_.dll on Cygwin

2008-02-14 Thread Jacek Laskowski (JIRA)


[ 
https://issues.apache.org/jira/browse/GERONIMO-3836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12569086#action_12569086
 ] 

Jacek Laskowski commented on GERONIMO-3836:
---

It does, but only when I'm in GERONIMO_HOME dir. I was outside and that's why 
the error came up.

> Deployment fails with FNFE due to missing jline_.dll on Cygwin
> --
>
> Key: GERONIMO-3836
> URL: https://issues.apache.org/jira/browse/GERONIMO-3836
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: deployment
>Affects Versions: 2.2
>Reporter: Jacek Laskowski
>
> Meant to deploy a webapp from a directory outside Geronimo's installation 
> dir. Deployer worked with -u and -p options although it spit FNFE exception, 
> but it failed without them.
> [EMAIL PROTECTED] 
> /cygdrive/c/apps/apache-wicket/src/jdk-1.5/wicket-examples/target
> $ c\:/geronimo/bin/deploy.sh -u system -p manager deploy wicket-examples.war
> Using GERONIMO_BASE:   c:\geronimo
> Using GERONIMO_HOME:   c:\geronimo
> Using GERONIMO_TMPDIR: 
> c:\apps\apache-wicket\src\jdk-1.5\wicket-examples\target\var\temp
> Using JRE_HOME:c:\apps\java5\jre
> java.io.FileNotFoundException: 
> c:\apps\apache-wicket\src\jdk-1.5\wicket-examples\target\var\temp\jline_.dll 
> (The system cannot find the path specified)
> at java.io.FileOutputStream.open(Native Method)
> at java.io.FileOutputStream.(FileOutputStream.java:179)
> at java.io.FileOutputStream.(FileOutputStream.java:131)
> at jline.WindowsTerminal.loadLibrary(WindowsTerminal.java:274)
> at jline.WindowsTerminal.initializeTerminal(WindowsTerminal.java:227)
> at jline.Terminal.setupTerminal(Terminal.java:77)
> at jline.Terminal.getTerminal(Terminal.java:28)
> at jline.ConsoleReader.(ConsoleReader.java:167)
> at jline.ConsoleReader.(ConsoleReader.java:162)
> at 
> org.apache.geronimo.deployment.cli.DeployTool.execute(DeployTool.java:164)
> at 
> org.apache.geronimo.kernel.util.MainConfigurationBootstrapper.main(MainConfigurationBootstrapper.java:45)
> at 
> org.apache.geronimo.cli.AbstractCLI.executeMain(AbstractCLI.java:67)
> at 
> org.apache.geronimo.cli.deployer.DeployerCLI.main(DeployerCLI.java:31)
> Deployed default/wicket-examples/1202695110250/war @
> /wicket-examples
> [EMAIL PROTECTED] 
> /cygdrive/c/apps/apache-wicket/src/jdk-1.5/wicket-examples/target
> $ c\:/geronimo/bin/deploy.sh undeploy 
> default/wicket-examples/1202695110250/war
> Using GERONIMO_BASE:   c:\geronimo
> Using GERONIMO_HOME:   c:\geronimo
> Using GERONIMO_TMPDIR: 
> c:\apps\apache-wicket\src\jdk-1.5\wicket-examples\target\var\temp
> Using JRE_HOME:c:\apps\java5\jre
> java.io.FileNotFoundException: 
> c:\apps\apache-wicket\src\jdk-1.5\wicket-examples\target\var\temp\jline_.dll 
> (The system cannot find the path specified)
> at java.io.FileOutputStream.open(Native Method)
> at java.io.FileOutputStream.(FileOutputStream.java:179)
> at java.io.FileOutputStream.(FileOutputStream.java:131)
> at jline.WindowsTerminal.loadLibrary(WindowsTerminal.java:274)
> at jline.WindowsTerminal.initializeTerminal(WindowsTerminal.java:227)
> at jline.Terminal.setupTerminal(Terminal.java:77)
> at jline.Terminal.getTerminal(Terminal.java:28)
> at jline.ConsoleReader.(ConsoleReader.java:167)
> at jline.ConsoleReader.(ConsoleReader.java:162)
> at 
> org.apache.geronimo.deployment.cli.InputPrompt.(InputPrompt.java:42)
> at 
> org.apache.geronimo.deployment.cli.ServerConnection.doAuthPromptAndRetry(ServerConnection.java:230)
> at 
> org.apache.geronimo.deployment.cli.ServerConnection.tryToConnect(ServerConnection.java:190)
> at 
> org.apache.geronimo.deployment.cli.ServerConnection.(ServerConnection.java:94)
> at 
> org.apache.geronimo.deployment.cli.DeployTool.execute(DeployTool.java:161)
> at 
> org.apache.geronimo.kernel.util.MainConfigurationBootstrapper.main(MainConfigurationBootstrapper.java:45)
> at 
> org.apache.geronimo.cli.AbstractCLI.executeMain(AbstractCLI.java:67)
> at 
> org.apache.geronimo.cli.deployer.DeployerCLI.main(DeployerCLI.java:31)
> Username: system
> Password: Error: Login Failed

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (GERONIMO-3836) Deployment fails with FNFE due to missing jline_.dll on Cygwin

2008-02-14 Thread Jason Dillon (JIRA)


[ 
https://issues.apache.org/jira/browse/GERONIMO-3836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12569081#action_12569081
 ] 

Jason Dillon commented on GERONIMO-3836:


gsh should work fine on cygwin...

> Deployment fails with FNFE due to missing jline_.dll on Cygwin
> --
>
> Key: GERONIMO-3836
> URL: https://issues.apache.org/jira/browse/GERONIMO-3836
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: deployment
>Affects Versions: 2.2
>Reporter: Jacek Laskowski
>
> Meant to deploy a webapp from a directory outside Geronimo's installation 
> dir. Deployer worked with -u and -p options although it spit FNFE exception, 
> but it failed without them.
> [EMAIL PROTECTED] 
> /cygdrive/c/apps/apache-wicket/src/jdk-1.5/wicket-examples/target
> $ c\:/geronimo/bin/deploy.sh -u system -p manager deploy wicket-examples.war
> Using GERONIMO_BASE:   c:\geronimo
> Using GERONIMO_HOME:   c:\geronimo
> Using GERONIMO_TMPDIR: 
> c:\apps\apache-wicket\src\jdk-1.5\wicket-examples\target\var\temp
> Using JRE_HOME:c:\apps\java5\jre
> java.io.FileNotFoundException: 
> c:\apps\apache-wicket\src\jdk-1.5\wicket-examples\target\var\temp\jline_.dll 
> (The system cannot find the path specified)
> at java.io.FileOutputStream.open(Native Method)
> at java.io.FileOutputStream.(FileOutputStream.java:179)
> at java.io.FileOutputStream.(FileOutputStream.java:131)
> at jline.WindowsTerminal.loadLibrary(WindowsTerminal.java:274)
> at jline.WindowsTerminal.initializeTerminal(WindowsTerminal.java:227)
> at jline.Terminal.setupTerminal(Terminal.java:77)
> at jline.Terminal.getTerminal(Terminal.java:28)
> at jline.ConsoleReader.(ConsoleReader.java:167)
> at jline.ConsoleReader.(ConsoleReader.java:162)
> at 
> org.apache.geronimo.deployment.cli.DeployTool.execute(DeployTool.java:164)
> at 
> org.apache.geronimo.kernel.util.MainConfigurationBootstrapper.main(MainConfigurationBootstrapper.java:45)
> at 
> org.apache.geronimo.cli.AbstractCLI.executeMain(AbstractCLI.java:67)
> at 
> org.apache.geronimo.cli.deployer.DeployerCLI.main(DeployerCLI.java:31)
> Deployed default/wicket-examples/1202695110250/war @
> /wicket-examples
> [EMAIL PROTECTED] 
> /cygdrive/c/apps/apache-wicket/src/jdk-1.5/wicket-examples/target
> $ c\:/geronimo/bin/deploy.sh undeploy 
> default/wicket-examples/1202695110250/war
> Using GERONIMO_BASE:   c:\geronimo
> Using GERONIMO_HOME:   c:\geronimo
> Using GERONIMO_TMPDIR: 
> c:\apps\apache-wicket\src\jdk-1.5\wicket-examples\target\var\temp
> Using JRE_HOME:c:\apps\java5\jre
> java.io.FileNotFoundException: 
> c:\apps\apache-wicket\src\jdk-1.5\wicket-examples\target\var\temp\jline_.dll 
> (The system cannot find the path specified)
> at java.io.FileOutputStream.open(Native Method)
> at java.io.FileOutputStream.(FileOutputStream.java:179)
> at java.io.FileOutputStream.(FileOutputStream.java:131)
> at jline.WindowsTerminal.loadLibrary(WindowsTerminal.java:274)
> at jline.WindowsTerminal.initializeTerminal(WindowsTerminal.java:227)
> at jline.Terminal.setupTerminal(Terminal.java:77)
> at jline.Terminal.getTerminal(Terminal.java:28)
> at jline.ConsoleReader.(ConsoleReader.java:167)
> at jline.ConsoleReader.(ConsoleReader.java:162)
> at 
> org.apache.geronimo.deployment.cli.InputPrompt.(InputPrompt.java:42)
> at 
> org.apache.geronimo.deployment.cli.ServerConnection.doAuthPromptAndRetry(ServerConnection.java:230)
> at 
> org.apache.geronimo.deployment.cli.ServerConnection.tryToConnect(ServerConnection.java:190)
> at 
> org.apache.geronimo.deployment.cli.ServerConnection.(ServerConnection.java:94)
> at 
> org.apache.geronimo.deployment.cli.DeployTool.execute(DeployTool.java:161)
> at 
> org.apache.geronimo.kernel.util.MainConfigurationBootstrapper.main(MainConfigurationBootstrapper.java:45)
> at 
> org.apache.geronimo.cli.AbstractCLI.executeMain(AbstractCLI.java:67)
> at 
> org.apache.geronimo.cli.deployer.DeployerCLI.main(DeployerCLI.java:31)
> Username: system
> Password: Error: Login Failed

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: Concurrency Utilities for Java EE

2008-02-14 Thread Kevan Miller



On Feb 14, 2008, at 12:06 PM, Jarek Gawor wrote:



Even if the RI thing does not work out or this specification does not
become part of Java EE 6, I still think this functionally would be a
good addition to Geronimo.

What do people think? Thoughts, any concerns?


Agreed. I think it would be great. My only question would concern  
licensing. As long as we have an api under an appropriate license (or  
can create one), seems like we could start this...


--kevan

[jira] Commented: (GERONIMO-3844) Errors on shutdown from admin console (Jetty only) - java.lang.InterruptedException

2008-02-14 Thread Joe Bohn (JIRA)


[ 
https://issues.apache.org/jira/browse/GERONIMO-3844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12569075#action_12569075
 ] 

Joe Bohn commented on GERONIMO-3844:


This is not a problem in trunk ... checking 2.1 branch soon.

> Errors on shutdown from admin console (Jetty only) - 
> java.lang.InterruptedException
> ---
>
> Key: GERONIMO-3844
> URL: https://issues.apache.org/jira/browse/GERONIMO-3844
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: console, Jetty
>Affects Versions: 2.1
> Environment: Jetty Java EE 5 assembly
>Reporter: Joe Bohn
>
> When shutting down Geronimo from the Admin console in the Jetty Assembly we 
> get the following exceptions:
> 13:23:19,474 ERROR [TcpTransportServer] Could not stop service: 
> tcp://0.0.0.0:61616. Reason: java.lang.InterruptedException
> java.lang.InterruptedException
> at java.lang.Object.wait(Native Method)
> at java.lang.Thread.join(Thread.java:1113)
> at java.lang.Thread.join(Thread.java:1166)
> at 
> org.apache.activemq.transport.TransportServerThreadSupport.doStop(TransportServerThreadSupport.java:81)
> at 
> org.apache.activemq.transport.tcp.TcpTransportServer.doStop(TcpTransportServer.java:219)
> at 
> org.apache.activemq.util.ServiceSupport.stop(ServiceSupport.java:58)
> at 
> org.apache.activemq.util.ServiceStopper.stop(ServiceStopper.java:42)
> at 
> org.apache.activemq.broker.TransportConnector.stop(TransportConnector.java:241)
> at 
> org.apache.geronimo.activemq.TransportConnectorGBeanImpl.doStop(TransportConnectorGBeanImpl.java:135)
> at 
> org.apache.geronimo.gbean.runtime.GBeanInstance.destroyInstance(GBeanInstance.java:1161)
> at 
> org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStop(GBeanInstanceState.java:339)
> at 
> org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:188)
> at 
> org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:563)
> at 
> org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:423)
> at 
> org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:180)
> at 
> org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:563)
> at 
> org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:423)
> at 
> org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:180)
> at 
> org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:563)
> at 
> org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:423)
> at 
> org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:180)
> at 
> org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:563)
> at 
> org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:423)
> at 
> org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:180)
> at 
> org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:563)
> at 
> org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:423)
> at 
> org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:180)
> at 
> org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:563)
> at 
> org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:423)
> at 
> org.apache.geronimo.kernel.config.KernelConfigurationManager$ShutdownHook.run(KernelConfigurationManager.java:316)
> at 
> org.apache.geronimo.kernel.basic.BasicKernel.notifyShutdownHooks(BasicKernel.java:668)
> at 
> org.apache.geronimo.kernel.basic.BasicKernel.shutdown(BasicKernel.java:645)
> at 
> org.apache.geronimo.console.servermanager.ServerManagerPortlet.doView(ServerManagerPortlet.java:74)
> at javax.portlet.GenericPortlet.doDispatch(GenericPortlet.java:247)
> at javax.portlet.GenericPortlet.render(GenericPortlet.java:175)
> at 
> org.apache.pluto.core.PortletServlet.dispatch(PortletServlet.java:208)
> at org.apache.pluto.core.PortletServlet.doGet(PortletServlet.java:139)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:693)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
> at 
> org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:487)
> at 
> org.apache.geronimo.jetty6.InternalJettyServletHolder.handle(InternalJettyServletHolder.java:65)
> at 
> org.mortbay.jetty.servlet.

[jira] Commented: (GERONIMO-3815) ContextManager.getCurrentContext() throws NullPointerException

2008-02-14 Thread Vamsavardhana Reddy (JIRA)


[ 
https://issues.apache.org/jira/browse/GERONIMO-3815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12569070#action_12569070
 ] 

Vamsavardhana Reddy commented on GERONIMO-3815:
---

 GERONIMO-3815-3.debug.patch seems to result in compilation errors.  Should it 
be callerSubject instead of currentSubject in getCurrentPrincpal()?

> ContextManager.getCurrentContext() throws NullPointerException
> --
>
> Key: GERONIMO-3815
> URL: https://issues.apache.org/jira/browse/GERONIMO-3815
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: security
>Affects Versions: 2.0.2, 2.1
>Reporter: Vamsavardhana Reddy
> Fix For: 2.0.x, 2.1.1
>
> Attachments: GERONIMO-3815-2.debug.patch, 
> GERONIMO-3815-3.debug.patch, GERONIMO-3815.debug.patch
>
>
> ContextManager.getCurrentContext() is throwing a NullPointerException.  This 
> is observed only when there is heavy load on the application.  Most likely it 
> is a threading issue where one thread is unregistering the subject while 
> another is executing getCurrentContext().  Excerpt from stacktrace given 
> below.
> 
> Caused by: java.lang.NullPointerException
> at 
> org.apache.geronimo.security.ContextManager.getCurrentContext(ContextManager.java:197)
> at 
> org.apache.geronimo.openejb.GeronimoSecurityService.isCallerAuthorized(GeronimoSecurityService.java:101)
> at 
> org.apache.openejb.core.stateless.StatelessContainer.invoke(StatelessContainer.java:142)
> at 
> org.apache.openejb.core.ivm.EjbHomeProxyHandler.create(EjbHomeProxyHandler.java:267)
> at 
> org.apache.openejb.core.ivm.EjbHomeProxyHandler._invoke(EjbHomeProxyHandler.java:158)
> at 
> org.apache.openejb.core.ivm.BaseEjbProxyHandler.invoke(BaseEjbProxyHandler.java:321)
> at 
> org.apache.openejb.util.proxy.Jdk13InvocationHandler.invoke(Jdk13InvocationHandler.java:49)
> at $Proxy16.create(Unknown Source)
> ... 53 more
>  

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: Concurrency Utilities for Java EE

2008-02-14 Thread Jason Dillon

Sounds good to me. 

--jason

-Original Message-
From: "Jarek Gawor" <[EMAIL PROTECTED]>

Date: Thu, 14 Feb 2008 12:06:43 
To:"Geronimo Dev" 
Subject: Concurrency Utilities for Java EE

Folks,

For the past few weeks I've been working on the Concurrency Utilities
for Java EE specification implementation. The Concurrency Utilities
for Java EE specification is a draft specification (see
http://gee.cs.oswego.edu/dl/concurrencyee-interest/ for more info)
that is supposed to replace the JSR-236 (Timer API) and JSR-237 (Work
Manager API) specifications and become part of Java EE 6.  The
Concurrency Utilities for Java EE specification basically extends the
java.util.concurrent.Executor API and adds managed environment
qualities to the tasks executed via the Executor. That is, the
background tasks can execute with the same environment as the
application that started it.

I have a little bit of code but it's definitely not complete or fully
functional and still needs a lot of work (e.g. better integration with
Geronimo, etc.). I would like to donate this code to Geronimo, and
continue to work on it there as a community.

Now, the cool thing is that this implementation might become the
official Reference Implementation (RI) for this spec. I've talked with
the IBM co-spec lead and there is a good chance of that happening if
we also commit to writing a TCK for it. And I think that would be a
great opportunity for Geronimo to show some leadership in the Java EE
spec area.

Even if the RI thing does not work out or this specification does not
become part of Java EE 6, I still think this functionally would be a
good addition to Geronimo.

What do people think? Thoughts, any concerns?

Jarek

[jira] Commented: (GERONIMO-3854) deploy/assemble and ERROR GroovyRuntimeException: Ambiguous method overloading for method org.apache.geronimo.kernel.repository.Artifact#


[ 
https://issues.apache.org/jira/browse/GERONIMO-3854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12569066#action_12569066
 ] 

Jarek Gawor commented on GERONIMO-3854:
---

Here are the additional problems:

By default artifact id and group id are optional.

1) If artifact id is not passed the command will fail with:

ERROR NullPointerException: artifactId is null: groupId: null, version: null, 
type: tar.gz

I'm not sure if we want to have some default artifact id or should we make the 
artifact id as a required argument.

2) If artifiact id is passed the generated assembly will be named:

-null-bin.tar.gz

becuase the group id is null.

Again, not sure if we should have a default group id, or a required argument, 
or change the generated assembly name to skip group id if null.

Comments welcome.


> deploy/assemble and ERROR GroovyRuntimeException: Ambiguous method 
> overloading for method org.apache.geronimo.kernel.repository.Artifact#
> ---
>
> Key: GERONIMO-3854
> URL: https://issues.apache.org/jira/browse/GERONIMO-3854
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: general
>Affects Versions: 2.1
>Reporter: Jacek Laskowski
>Assignee: Jarek Gawor
>
> [EMAIL PROTECTED]:/> deploy/assemble
> Listing configurations from Geronimo server
> Connecting to Geronimo server: localhost:1099
> Username: system
> Password: ***
> Connection established
> 
>  1:  Geronimo Plugins, Monitoring :: Agent DataSource (2.1)
>  2:  Geronimo Plugins, Monitoring :: Console DataSource (2.1)
> Administration
>  3:  Geronimo Plugins, Console :: Jetty (2.1)
>  4:  Geronimo Plugins, Console :: Plugin and Deployment Portlets
> (Jetty) (2.1)
>  5:  Geronimo Plugins, Welcome :: Jetty (2.1)
> Clustering
>  6:  Geronimo Plugins, Clustering :: Clustering (2.1)
>  7:  Geronimo Plugins, Clustering :: Farming (2.1)
>  8:  Geronimo Plugins, Clustering :: WADI (2.1)
> Connector
>  9:  Geronimo Plugins, Connector :: Deployer (2.1)
> Databases
>  10: Geronimo Plugins, System Database :: Console (Jetty) (2.1)
> Debug
>  11: Geronimo Plugins, Debug Views :: Jetty (2.1)
> Deployment
>  12: Geronimo Framework, Configs :: CLI Upgrade (2.1)
>  13: Geronimo Framework, Configs :: JSR-88 CLI (2.1)
>  14: Geronimo Framework, Configs :: JSR-88 DeploymentFactory (2.1)
>  15: Geronimo Framework, Configs :: Offline Deployer (2.1)
>  16: Geronimo Framework, Configs :: Online Deployer (2.1)
>  17: Geronimo Plugins, J2EE :: JSR-88 EAR Configurer (2.1)
>  18: Geronimo Plugins, J2EE :: JSR-88 JAR Configurer (2.1)
>  19: Geronimo Plugins, J2EE :: JSR-88 RAR Configurer (2.1)
>  20: Geronimo Plugins, J2EE :: JSR-88 WAR Configurer (2.1)
>  21: Geronimo Plugins, Remote Deploy :: Jetty (2.1)
> Development tools
>  22: Geronimo Plugins, Plan Creator :: Jetty (2.1)
> EJB
>  23: Geronimo Plugins, Corba :: Yoko ORB (2.1)
>  24: Geronimo Plugins, MEJB :: Config (2.1)
> EJB Container
>  25: Geronimo Plugins, Corba :: Deployer (2.1)
>  26: Geronimo Plugins, OpenEJB :: Deployer (2.1)
>  27: Geronimo Plugins, OpenEJB :: OpenEJB (2.1)
> Example
>  28: Geronimo Plugins, Shared Library (2.1)
> Fluff
>  29: Geronimo Plugins, Hot Deploy :: Deployer (2.1)
> Geronimo Core
>  30: Geronimo Assemblies :: Boilerplate Minimal (2.1)
>  31: Geronimo Framework, Configs :: Client System (2.1)
>  32: Geronimo Framework, Configs :: GBean Deployer (2.1)
>  33: Geronimo Framework, Configs :: J2EE System (2.1)
>  34: Geronimo Framework, Configs :: Plugin Management (2.1)
>  35: Geronimo Framework, Configs :: RMI Naming (2.1)
>  36: Geronimo Framework, Configs :: Shutdown (2.1)
>  37: Geronimo Framework, Configs :: Transformer Agent (2.1)
>  38: Geronimo Framework, Configs :: XMLBeans (2.1)
>  39: Geronimo Plugins, Client :: Client (2.1)
>  40: Geronimo Plugins, Client :: Deployer (2.1)
>  41: Geronimo Plugins, Client :: Security (2.1)
>  42: Geronimo Plugins, Connector :: Client transaction (2.1)
>  43: Geronimo Plugins, Connector :: Transaction Manager (JTA11) (2.1)
>  44: Geronimo Plugins, Corba :: Client Yoko (2.1)
>  45: Geronimo Plugins, Spring (2.1)
>  46: Geronimo Plugins, System Database :: System Database (2.1)
> JMS
>  47: Geronimo Plugins, ActiveMQ :: Broker (2.1)
>  48: Geronimo Plugins, ActiveMQ :: Console (Jetty) (2.1)
>  49: Geronimo Plugins, ActiveMQ :: Resource Adapter (2.1)
> JavaEE
>  50: Geronimo Framework, Configs :: JavaEE Specs (2.1)
>  51: Geronimo Plugins, J2EE :: Server (2.1)
>  52: Geronimo Plugins, Java

[jira] Commented: (GERONIMO-3854) deploy/assemble and ERROR GroovyRuntimeException: Ambiguous method overloading for method org.apache.geronimo.kernel.repository.Artifact#


[ 
https://issues.apache.org/jira/browse/GERONIMO-3854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12569064#action_12569064
 ] 

Jarek Gawor commented on GERONIMO-3854:
---

The problem can be avoided by passing an artifact id and version.

Committed a minor fix to trunk (revision 627854) and branches/2.1 (revision 
627855). But the gshell command still needs some improvements.


> deploy/assemble and ERROR GroovyRuntimeException: Ambiguous method 
> overloading for method org.apache.geronimo.kernel.repository.Artifact#
> ---
>
> Key: GERONIMO-3854
> URL: https://issues.apache.org/jira/browse/GERONIMO-3854
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: general
>Affects Versions: 2.1
>Reporter: Jacek Laskowski
>Assignee: Jarek Gawor
>
> [EMAIL PROTECTED]:/> deploy/assemble
> Listing configurations from Geronimo server
> Connecting to Geronimo server: localhost:1099
> Username: system
> Password: ***
> Connection established
> 
>  1:  Geronimo Plugins, Monitoring :: Agent DataSource (2.1)
>  2:  Geronimo Plugins, Monitoring :: Console DataSource (2.1)
> Administration
>  3:  Geronimo Plugins, Console :: Jetty (2.1)
>  4:  Geronimo Plugins, Console :: Plugin and Deployment Portlets
> (Jetty) (2.1)
>  5:  Geronimo Plugins, Welcome :: Jetty (2.1)
> Clustering
>  6:  Geronimo Plugins, Clustering :: Clustering (2.1)
>  7:  Geronimo Plugins, Clustering :: Farming (2.1)
>  8:  Geronimo Plugins, Clustering :: WADI (2.1)
> Connector
>  9:  Geronimo Plugins, Connector :: Deployer (2.1)
> Databases
>  10: Geronimo Plugins, System Database :: Console (Jetty) (2.1)
> Debug
>  11: Geronimo Plugins, Debug Views :: Jetty (2.1)
> Deployment
>  12: Geronimo Framework, Configs :: CLI Upgrade (2.1)
>  13: Geronimo Framework, Configs :: JSR-88 CLI (2.1)
>  14: Geronimo Framework, Configs :: JSR-88 DeploymentFactory (2.1)
>  15: Geronimo Framework, Configs :: Offline Deployer (2.1)
>  16: Geronimo Framework, Configs :: Online Deployer (2.1)
>  17: Geronimo Plugins, J2EE :: JSR-88 EAR Configurer (2.1)
>  18: Geronimo Plugins, J2EE :: JSR-88 JAR Configurer (2.1)
>  19: Geronimo Plugins, J2EE :: JSR-88 RAR Configurer (2.1)
>  20: Geronimo Plugins, J2EE :: JSR-88 WAR Configurer (2.1)
>  21: Geronimo Plugins, Remote Deploy :: Jetty (2.1)
> Development tools
>  22: Geronimo Plugins, Plan Creator :: Jetty (2.1)
> EJB
>  23: Geronimo Plugins, Corba :: Yoko ORB (2.1)
>  24: Geronimo Plugins, MEJB :: Config (2.1)
> EJB Container
>  25: Geronimo Plugins, Corba :: Deployer (2.1)
>  26: Geronimo Plugins, OpenEJB :: Deployer (2.1)
>  27: Geronimo Plugins, OpenEJB :: OpenEJB (2.1)
> Example
>  28: Geronimo Plugins, Shared Library (2.1)
> Fluff
>  29: Geronimo Plugins, Hot Deploy :: Deployer (2.1)
> Geronimo Core
>  30: Geronimo Assemblies :: Boilerplate Minimal (2.1)
>  31: Geronimo Framework, Configs :: Client System (2.1)
>  32: Geronimo Framework, Configs :: GBean Deployer (2.1)
>  33: Geronimo Framework, Configs :: J2EE System (2.1)
>  34: Geronimo Framework, Configs :: Plugin Management (2.1)
>  35: Geronimo Framework, Configs :: RMI Naming (2.1)
>  36: Geronimo Framework, Configs :: Shutdown (2.1)
>  37: Geronimo Framework, Configs :: Transformer Agent (2.1)
>  38: Geronimo Framework, Configs :: XMLBeans (2.1)
>  39: Geronimo Plugins, Client :: Client (2.1)
>  40: Geronimo Plugins, Client :: Deployer (2.1)
>  41: Geronimo Plugins, Client :: Security (2.1)
>  42: Geronimo Plugins, Connector :: Client transaction (2.1)
>  43: Geronimo Plugins, Connector :: Transaction Manager (JTA11) (2.1)
>  44: Geronimo Plugins, Corba :: Client Yoko (2.1)
>  45: Geronimo Plugins, Spring (2.1)
>  46: Geronimo Plugins, System Database :: System Database (2.1)
> JMS
>  47: Geronimo Plugins, ActiveMQ :: Broker (2.1)
>  48: Geronimo Plugins, ActiveMQ :: Console (Jetty) (2.1)
>  49: Geronimo Plugins, ActiveMQ :: Resource Adapter (2.1)
> JavaEE
>  50: Geronimo Framework, Configs :: JavaEE Specs (2.1)
>  51: Geronimo Plugins, J2EE :: Server (2.1)
>  52: Geronimo Plugins, JavaMail :: JavaMail (2.1)
> JavaEE deployment
>  53: Geronimo Plugins, J2EE :: Deployer (2.1)
>  54: Geronimo Plugins, Jasper :: Deployer (2.1)
> Jetty
>  55: Geronimo Plugins, Jetty :: Clustering Builder for WADI (2.1)
>  56: Geronimo Plugins, Jetty :: Deployer (2.1)
>  57: Geronimo Plugins, Jetty :: Jetty 6 (2.1)
>  58: Geronimo Plugins, Jetty :: Jetty 6 Clustering over WADI (2.1)
> Monitoring
>  59:

Re: framework assembly distribution?

2008-02-14 Thread Joe Bohn

Kevan Miller wrote:

On Feb 14, 2008, at 12:03 PM, David Jencks wrote:

On Feb 14, 2008, at 8:30 AM, Joe Bohn wrote:

--kevan

Thanks Kevan (and David). The framework assembly has been part of our
binary artifacts since late 2006 but we had yet to include it for
download with any release to date. And since it was not listed for 2.1,
I wasn't clear that we were going to include it this go-around either.
Thanks for the clarification.

Joe

[jira] Updated: (GERONIMO-3802) In plugin installer, assembling a server, add a page at the end to confirm or deny the assembly of a server package.

2008-02-14 Thread Donald Woods (JIRA)


 [ 
https://issues.apache.org/jira/browse/GERONIMO-3802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Donald Woods updated GERONIMO-3802:
---

Affects Version/s: 2.2
Fix Version/s: (was: 2.1.1)
   2.2

> In plugin installer, assembling a server, add a page at the end to confirm or 
> deny the assembly of a server package.
> 
>
> Key: GERONIMO-3802
> URL: https://issues.apache.org/jira/browse/GERONIMO-3802
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: console
>Affects Versions: 2.1, 2.1.1, 2.2
>Reporter: Joseph Leong
>Assignee: Jarek Gawor
>Priority: Minor
> Fix For: 2.2
>
> Attachments: GERONIMO-3802.patch
>
>
> Add a type of confirmation page at the end of Assembling a server to inform 
> the user whether the creation of there server was successful or not.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (GERONIMO-3856) Assemble a Server Confirmation Page

2008-02-14 Thread Donald Woods (JIRA)


 [ 
https://issues.apache.org/jira/browse/GERONIMO-3856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Donald Woods updated GERONIMO-3856:
---

Affects Version/s: 2.1.1
   2.1

It also affects the 2.1 and 2.1.1 release

> Assemble a Server Confirmation Page
> ---
>
> Key: GERONIMO-3856
> URL: https://issues.apache.org/jira/browse/GERONIMO-3856
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: console
>Affects Versions: 2.1, 2.1.1, 2.2
>Reporter: Joseph Leong
>Assignee: Joseph Leong
>Priority: Minor
>
> Improvements for the Assemble a Server Confirmation Page
> 1) At minimum the user should provide an artifact id otherwise assembly named 
> --bin.tar.gz will be created. The portlet should check for empty artifact id.
> 2) If no plugins are selected and 'assemble' button is pressed a nasty 
> exception will be displayed. The portlet should check if at least one plugin 
> was selected.
> 3) On the confirmation screen and on Windows the server path location will 
> contain / and \. For example c:\geronimo/var/temp/foo.tar.gz.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Resolved: (GERONIMO-3802) In plugin installer, assembling a server, add a page at the end to confirm or deny the assembly of a server package.


 [ 
https://issues.apache.org/jira/browse/GERONIMO-3802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Joseph Leong resolved GERONIMO-3802.


Resolution: Fixed

Assembly page committed, further improvements will be applied at GERONIMO-3856


> In plugin installer, assembling a server, add a page at the end to confirm or 
> deny the assembly of a server package.
> 
>
> Key: GERONIMO-3802
> URL: https://issues.apache.org/jira/browse/GERONIMO-3802
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: console
>Affects Versions: 2.1, 2.1.1
>Reporter: Joseph Leong
>Assignee: Jarek Gawor
>Priority: Minor
> Fix For: 2.1.1
>
> Attachments: GERONIMO-3802.patch
>
>
> Add a type of confirmation page at the end of Assembling a server to inform 
> the user whether the creation of there server was successful or not.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (GERONIMO-3802) In plugin installer, assembling a server, add a page at the end to confirm or deny the assembly of a server package.


[ 
https://issues.apache.org/jira/browse/GERONIMO-3802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12569053#action_12569053
 ] 

Joseph Leong commented on GERONIMO-3802:


Thanks Jarek,

Great suggestions.  I'll add these to the list and work on them for 
GERONIMO-3856



> In plugin installer, assembling a server, add a page at the end to confirm or 
> deny the assembly of a server package.
> 
>
> Key: GERONIMO-3802
> URL: https://issues.apache.org/jira/browse/GERONIMO-3802
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: console
>Affects Versions: 2.1, 2.1.1
>Reporter: Joseph Leong
>Assignee: Jarek Gawor
>Priority: Minor
> Fix For: 2.1.1
>
> Attachments: GERONIMO-3802.patch
>
>
> Add a type of confirmation page at the end of Assembling a server to inform 
> the user whether the creation of there server was successful or not.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Created: (GERONIMO-3856) Assemble a Server Confirmation Page

Assemble a Server Confirmation Page
---

 Key: GERONIMO-3856
 URL: https://issues.apache.org/jira/browse/GERONIMO-3856
 Project: Geronimo
  Issue Type: Improvement
  Security Level: public (Regular issues)
  Components: console
Affects Versions: 2.2
Reporter: Joseph Leong
Assignee: Joseph Leong
Priority: Minor


Improvements for the Assemble a Server Confirmation Page

1) At minimum the user should provide an artifact id otherwise assembly named 
--bin.tar.gz will be created. The portlet should check for empty artifact id.

2) If no plugins are selected and 'assemble' button is pressed a nasty 
exception will be displayed. The portlet should check if at least one plugin 
was selected.

3) On the confirmation screen and on Windows the server path location will 
contain / and \. For example c:\geronimo/var/temp/foo.tar.gz.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Assigned: (GERONIMO-3846) cookies are not carried over when requests are redirected


 [ 
https://issues.apache.org/jira/browse/GERONIMO-3846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sangjin Lee reassigned GERONIMO-3846:
-

Assignee: Rick McGuire

Just to put it on your radar...  Thanks!

> cookies are not carried over when requests are redirected
> -
>
> Key: GERONIMO-3846
> URL: https://issues.apache.org/jira/browse/GERONIMO-3846
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: AsyncHttpClient
>Affects Versions: 1.x
>Reporter: Sangjin Lee
>Assignee: Rick McGuire
>Priority: Minor
> Attachments: GERONIMO-3846.patch
>
>
> When you send a request and receive a redirect response (301 or 302), the 
> response may contain cookies (via Set-Cookie header).  For subsequent 
> redirect requests, these cookies need to be sent.  Currently AHC does not 
> send any cookies unless explicitly set by the caller.
> Two cases where this should be done are redirects and auth challenges.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Assigned: (GERONIMO-3854) deploy/assemble and ERROR GroovyRuntimeException: Ambiguous method overloading for method org.apache.geronimo.kernel.repository.Artifact#


 [ 
https://issues.apache.org/jira/browse/GERONIMO-3854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jarek Gawor reassigned GERONIMO-3854:
-

Assignee: Jarek Gawor

> deploy/assemble and ERROR GroovyRuntimeException: Ambiguous method 
> overloading for method org.apache.geronimo.kernel.repository.Artifact#
> ---
>
> Key: GERONIMO-3854
> URL: https://issues.apache.org/jira/browse/GERONIMO-3854
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: general
>Affects Versions: 2.1
>Reporter: Jacek Laskowski
>Assignee: Jarek Gawor
>
> [EMAIL PROTECTED]:/> deploy/assemble
> Listing configurations from Geronimo server
> Connecting to Geronimo server: localhost:1099
> Username: system
> Password: ***
> Connection established
> 
>  1:  Geronimo Plugins, Monitoring :: Agent DataSource (2.1)
>  2:  Geronimo Plugins, Monitoring :: Console DataSource (2.1)
> Administration
>  3:  Geronimo Plugins, Console :: Jetty (2.1)
>  4:  Geronimo Plugins, Console :: Plugin and Deployment Portlets
> (Jetty) (2.1)
>  5:  Geronimo Plugins, Welcome :: Jetty (2.1)
> Clustering
>  6:  Geronimo Plugins, Clustering :: Clustering (2.1)
>  7:  Geronimo Plugins, Clustering :: Farming (2.1)
>  8:  Geronimo Plugins, Clustering :: WADI (2.1)
> Connector
>  9:  Geronimo Plugins, Connector :: Deployer (2.1)
> Databases
>  10: Geronimo Plugins, System Database :: Console (Jetty) (2.1)
> Debug
>  11: Geronimo Plugins, Debug Views :: Jetty (2.1)
> Deployment
>  12: Geronimo Framework, Configs :: CLI Upgrade (2.1)
>  13: Geronimo Framework, Configs :: JSR-88 CLI (2.1)
>  14: Geronimo Framework, Configs :: JSR-88 DeploymentFactory (2.1)
>  15: Geronimo Framework, Configs :: Offline Deployer (2.1)
>  16: Geronimo Framework, Configs :: Online Deployer (2.1)
>  17: Geronimo Plugins, J2EE :: JSR-88 EAR Configurer (2.1)
>  18: Geronimo Plugins, J2EE :: JSR-88 JAR Configurer (2.1)
>  19: Geronimo Plugins, J2EE :: JSR-88 RAR Configurer (2.1)
>  20: Geronimo Plugins, J2EE :: JSR-88 WAR Configurer (2.1)
>  21: Geronimo Plugins, Remote Deploy :: Jetty (2.1)
> Development tools
>  22: Geronimo Plugins, Plan Creator :: Jetty (2.1)
> EJB
>  23: Geronimo Plugins, Corba :: Yoko ORB (2.1)
>  24: Geronimo Plugins, MEJB :: Config (2.1)
> EJB Container
>  25: Geronimo Plugins, Corba :: Deployer (2.1)
>  26: Geronimo Plugins, OpenEJB :: Deployer (2.1)
>  27: Geronimo Plugins, OpenEJB :: OpenEJB (2.1)
> Example
>  28: Geronimo Plugins, Shared Library (2.1)
> Fluff
>  29: Geronimo Plugins, Hot Deploy :: Deployer (2.1)
> Geronimo Core
>  30: Geronimo Assemblies :: Boilerplate Minimal (2.1)
>  31: Geronimo Framework, Configs :: Client System (2.1)
>  32: Geronimo Framework, Configs :: GBean Deployer (2.1)
>  33: Geronimo Framework, Configs :: J2EE System (2.1)
>  34: Geronimo Framework, Configs :: Plugin Management (2.1)
>  35: Geronimo Framework, Configs :: RMI Naming (2.1)
>  36: Geronimo Framework, Configs :: Shutdown (2.1)
>  37: Geronimo Framework, Configs :: Transformer Agent (2.1)
>  38: Geronimo Framework, Configs :: XMLBeans (2.1)
>  39: Geronimo Plugins, Client :: Client (2.1)
>  40: Geronimo Plugins, Client :: Deployer (2.1)
>  41: Geronimo Plugins, Client :: Security (2.1)
>  42: Geronimo Plugins, Connector :: Client transaction (2.1)
>  43: Geronimo Plugins, Connector :: Transaction Manager (JTA11) (2.1)
>  44: Geronimo Plugins, Corba :: Client Yoko (2.1)
>  45: Geronimo Plugins, Spring (2.1)
>  46: Geronimo Plugins, System Database :: System Database (2.1)
> JMS
>  47: Geronimo Plugins, ActiveMQ :: Broker (2.1)
>  48: Geronimo Plugins, ActiveMQ :: Console (Jetty) (2.1)
>  49: Geronimo Plugins, ActiveMQ :: Resource Adapter (2.1)
> JavaEE
>  50: Geronimo Framework, Configs :: JavaEE Specs (2.1)
>  51: Geronimo Plugins, J2EE :: Server (2.1)
>  52: Geronimo Plugins, JavaMail :: JavaMail (2.1)
> JavaEE deployment
>  53: Geronimo Plugins, J2EE :: Deployer (2.1)
>  54: Geronimo Plugins, Jasper :: Deployer (2.1)
> Jetty
>  55: Geronimo Plugins, Jetty :: Clustering Builder for WADI (2.1)
>  56: Geronimo Plugins, Jetty :: Deployer (2.1)
>  57: Geronimo Plugins, Jetty :: Jetty 6 (2.1)
>  58: Geronimo Plugins, Jetty :: Jetty 6 Clustering over WADI (2.1)
> Monitoring
>  59: Geronimo Plugins, Monitoring :: Agent (2.1)
>  60: Geronimo Plugins, Monitoring :: Console (Jetty) (2.1)
> Persistence
>  61: Geronimo Plugins, OpenJPA :: Deployer (2.1)
>  62: Geronimo Plugins, OpenJPA :: OpenJPA (2.1

[jira] Commented: (GERONIMO-3802) In plugin installer, assembling a server, add a page at the end to confirm or deny the assembly of a server package.


[ 
https://issues.apache.org/jira/browse/GERONIMO-3802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12569043#action_12569043
 ] 

Jarek Gawor commented on GERONIMO-3802:
---

Committed the patch to trunk (revision 627838). Thanks!

I've noticed a few more minor issues that can be improved with the portlet:

1) At minimum the user should provide an artifact id otherwise assembly named 
--bin.tar.gz will be created. The portlet should check for empty artifact id. 

2) If no plugins are selected and 'assemble' button is pressed a nasty 
exception will be displayed. The portlet should check if at least one plugin 
was selected.

3) On the confirmation screen and on Windows the server path location will 
contain / and \. For example c:\geronimo/var/temp/foo.tar.gz.



> In plugin installer, assembling a server, add a page at the end to confirm or 
> deny the assembly of a server package.
> 
>
> Key: GERONIMO-3802
> URL: https://issues.apache.org/jira/browse/GERONIMO-3802
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: console
>Affects Versions: 2.1, 2.1.1
>Reporter: Joseph Leong
>Assignee: Jarek Gawor
>Priority: Minor
> Fix For: 2.1.1
>
> Attachments: GERONIMO-3802.patch
>
>
> Add a type of confirmation page at the end of Assembling a server to inform 
> the user whether the creation of there server was successful or not.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: [VOTE] Geronimo Server 2.1 and Geronimo TxManager 2.1.1 Releases

2008-02-14 Thread Paul McMahan


Good question :-)   I opened:
https://issues.apache.org/jira/browse/GERONIMO-3855

Best wishes,
Paul


On Feb 14, 2008, at 1:32 PM, Jacek Laskowski wrote:

On Thu, Feb 14, 2008 at 6:00 AM, Paul McMahan  
<[EMAIL PROTECTED]> wrote:



 Looks good except for the Plugins portlet which is not working for
 me.  Several actions in that portlet lead to:
 javax.portlet.PortletSecurityException: No Supported


Hi Paul,

Have you reported it in JIRA? I could find any emails from jira  
about it.


Jacek

--
Jacek Laskowski
http://www.JacekLaskowski.pl

[jira] Created: (GERONIMO-3855) PortletSecurityException in Plugins portlet

2008-02-14 Thread Paul McMahan (JIRA)

PortletSecurityException in Plugins portlet
---

 Key: GERONIMO-3855
 URL: https://issues.apache.org/jira/browse/GERONIMO-3855
 Project: Geronimo
  Issue Type: Bug
  Security Level: public (Regular issues)
  Components: console
Affects Versions: 2.1
Reporter: Paul McMahan


Cannot take any actions in the Plugins portlet.

Recreate:
Go to the Plugins portlet in the admin console
Click any action-- "Update Repository List" or "Add Repository" or "Export a 
Plugin" or "Assemble a Server"
Note the exception:

javax.servlet.ServletException: javax.portlet.PortletSecurityException: No 
Supported

org.apache.pluto.driver.PortalDriverServlet.doGet(PortalDriverServlet.java:116)

org.apache.pluto.driver.PortalDriverServlet.doPost(PortalDriverServlet.java:158)
javax.servlet.http.HttpServlet.service(HttpServlet.java:713)
javax.servlet.http.HttpServlet.service(HttpServlet.java:806)

root cause

javax.portlet.PortletSecurityException: No Supported

org.apache.pluto.driver.services.container.PortletURLProviderImpl.setSecure(PortletURLProviderImpl.java:67)

org.apache.pluto.core.PortletContainerImpl.doAction(PortletContainerImpl.java:261)

org.apache.pluto.driver.PortalDriverServlet.doGet(PortalDriverServlet.java:112)

org.apache.pluto.driver.PortalDriverServlet.doPost(PortalDriverServlet.java:158)
javax.servlet.http.HttpServlet.service(HttpServlet.java:713)
javax.servlet.http.HttpServlet.service(HttpServlet.java:806)


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: framework assembly distribution?

2008-02-14 Thread Hernan Cunico

As much as I would like to see this new flavor out it wouldn't be the same if
nobody knows how to use it.

Yes, you all guessed right, I'm again around the documentation. Who is volunteering to do some "explaining" thingy ?

This is not a small deal, if we release this new distro we need to make some
announcements on the web site, add some overview on the download page and
definitively a section in the 2.1 documentation.

Cheers!
Hernan

Kevan Miller wrote:

On Feb 14, 2008, at 12:03 PM, David Jencks wrote:

On Feb 14, 2008, at 8:30 AM, Joe Bohn wrote:

--kevan

Re: [VOTE] Geronimo Server 2.1 and Geronimo TxManager 2.1.1 Releases

On Thu, Feb 14, 2008 at 6:00 AM, Paul McMahan <[EMAIL PROTECTED]> wrote:

>  Looks good except for the Plugins portlet which is not working for
>  me.  Several actions in that portlet lead to:
>  javax.portlet.PortletSecurityException: No Supported

Hi Paul,

Have you reported it in JIRA? I could find any emails from jira about it.

Jacek

-- 
Jacek Laskowski
http://www.JacekLaskowski.pl

Re: [DISCUSS] Geronimo Server 2.1 and Geronimo TxManager 2.1.1 Releases

On Thu, Feb 14, 2008 at 8:47 AM, Lin Sun <[EMAIL PROTECTED]> wrote:

>  P.S. sorry for trying these late - i just got back from a long long leave...

No need to worry. Do whatever you can and your time permits. Even
late-runners have something to say and their voice counts. Report any
issue you run across so it gets fixed in the upcoming releases if 2.1
is already out.

Jacek

-- 
Jacek Laskowski
http://www.JacekLaskowski.pl

Re: Concurrency Utilities for Java EE

On Thu, Feb 14, 2008 at 9:06 AM, Jarek Gawor <[EMAIL PROTECTED]> wrote:

>  Now, the cool thing is that this implementation might become the
>  official Reference Implementation (RI) for this spec. I've talked with
>  the IBM co-spec lead and there is a good chance of that happening if
>  we also commit to writing a TCK for it. And I think that would be a
>  great opportunity for Geronimo to show some leadership in the Java EE
>  spec area.
...
>  What do people think? Thoughts, any concerns?

Yay! That's awesome. I don't think we should wait for anybody to say
it's fine to make it public. There's some uncertainity it won't be
included in the spec and we'll have to develop something similar, but
then that's the issue of every early-adopter. If we do it right,
people might love it even though it's not part of the spec and it
eventually might become its part in javaee 7 or so.

+1

Jacek

-- 
Jacek Laskowski
http://www.JacekLaskowski.pl

Re: framework assembly distribution?

2008-02-14 Thread Kevan Miller

On Feb 14, 2008, at 12:03 PM, David Jencks wrote:

On Feb 14, 2008, at 8:30 AM, Joe Bohn wrote:

With our 2.1 distribution (as with earlier distributions) we are
only providing the javaee5 & minimal assemblies. Are we ever
planning to make the geronimo-framework assembly available in a
distribution so that a user could start from scratch (not even a
web container) and build up a server by installing plugins?

All the framework assembly can do is install plugins. I think we
should definitely distribute it in the future and I am proposing we
distribute it for 2.1 as well. IIUC in any case it will get into
the maven repos, so adding it to the official download page
shouldn't be too hard.

Agreed. We are releasing the framework assembly. It's part of the
binary artifacts in our maven repo -- http://people.apache.org/~kevan/release-votes/G-2.1/geronimo-2.1/org/apache/geronimo/assemblies/geronimo-framework/2.1/

Simple matter, IMO, to also include in the distribution page. IMO, a
vote isn't necessary (as it's already covered by the existing 2.1
vote). I'll give this a bit of time, to see if there are contrary
opinions. Assuming, the 2.1 vote passes and there aren't any
objections, I'll set up framework in the distribution directory, also.

--kevan

Re: framework assembly distribution?

2008-02-14 Thread Hernan Cunico


It would be nice to have this alternative available in the next releases.

Would this later become the new "minimal" dist? I mean the framework is as 
minimal as minimal can get, right!?

In any case, we'll need to fill the documentation gaps we are having today 
around the plugin architecture, how to install and manage them. If we would be 
voting, I would give a +1 as long as we provide the supporting documentation.

Cheers!
Hernan

Joe Bohn wrote:


With our 2.1 distribution (as with earlier distributions) we are only 
providing the javaee5 & minimal assemblies.  Are we ever planning to 
make the geronimo-framework assembly available in a distribution so that 
a user could start from scratch (not even a web container) and build up 
a server by installing plugins?


That was the original intent when we created this assembly.  I know that 
the originally framework included enough deployment capability to deploy 
plugins.  However, I'm not certain that is still the case (I haven't 
tried in a long time).  Assuming you can still install plugins (or we 
add that back in), I think it makes sense to distribute this assembly. 
BTW, I'm not proposing this for 2.1 given that it is nearly completely 
baked.


What do others think?

Joe

[jira] Created: (GERONIMO-3854) deploy/assemble and ERROR GroovyRuntimeException: Ambiguous method overloading for method org.apache.geronimo.kernel.repository.Artifact#

2008-02-14 Thread Jacek Laskowski (JIRA)

deploy/assemble and ERROR GroovyRuntimeException: Ambiguous method overloading 
for method org.apache.geronimo.kernel.repository.Artifact#
---

 Key: GERONIMO-3854
 URL: https://issues.apache.org/jira/browse/GERONIMO-3854
 Project: Geronimo
  Issue Type: Bug
  Security Level: public (Regular issues)
  Components: general
Affects Versions: 2.1
Reporter: Jacek Laskowski


[EMAIL PROTECTED]:/> deploy/assemble
Listing configurations from Geronimo server
Connecting to Geronimo server: localhost:1099
Username: system
Password: ***
Connection established

 1:  Geronimo Plugins, Monitoring :: Agent DataSource (2.1)
 2:  Geronimo Plugins, Monitoring :: Console DataSource (2.1)
Administration
 3:  Geronimo Plugins, Console :: Jetty (2.1)
 4:  Geronimo Plugins, Console :: Plugin and Deployment Portlets
(Jetty) (2.1)
 5:  Geronimo Plugins, Welcome :: Jetty (2.1)
Clustering
 6:  Geronimo Plugins, Clustering :: Clustering (2.1)
 7:  Geronimo Plugins, Clustering :: Farming (2.1)
 8:  Geronimo Plugins, Clustering :: WADI (2.1)
Connector
 9:  Geronimo Plugins, Connector :: Deployer (2.1)
Databases
 10: Geronimo Plugins, System Database :: Console (Jetty) (2.1)
Debug
 11: Geronimo Plugins, Debug Views :: Jetty (2.1)
Deployment
 12: Geronimo Framework, Configs :: CLI Upgrade (2.1)
 13: Geronimo Framework, Configs :: JSR-88 CLI (2.1)
 14: Geronimo Framework, Configs :: JSR-88 DeploymentFactory (2.1)
 15: Geronimo Framework, Configs :: Offline Deployer (2.1)
 16: Geronimo Framework, Configs :: Online Deployer (2.1)
 17: Geronimo Plugins, J2EE :: JSR-88 EAR Configurer (2.1)
 18: Geronimo Plugins, J2EE :: JSR-88 JAR Configurer (2.1)
 19: Geronimo Plugins, J2EE :: JSR-88 RAR Configurer (2.1)
 20: Geronimo Plugins, J2EE :: JSR-88 WAR Configurer (2.1)
 21: Geronimo Plugins, Remote Deploy :: Jetty (2.1)
Development tools
 22: Geronimo Plugins, Plan Creator :: Jetty (2.1)
EJB
 23: Geronimo Plugins, Corba :: Yoko ORB (2.1)
 24: Geronimo Plugins, MEJB :: Config (2.1)
EJB Container
 25: Geronimo Plugins, Corba :: Deployer (2.1)
 26: Geronimo Plugins, OpenEJB :: Deployer (2.1)
 27: Geronimo Plugins, OpenEJB :: OpenEJB (2.1)
Example
 28: Geronimo Plugins, Shared Library (2.1)
Fluff
 29: Geronimo Plugins, Hot Deploy :: Deployer (2.1)
Geronimo Core
 30: Geronimo Assemblies :: Boilerplate Minimal (2.1)
 31: Geronimo Framework, Configs :: Client System (2.1)
 32: Geronimo Framework, Configs :: GBean Deployer (2.1)
 33: Geronimo Framework, Configs :: J2EE System (2.1)
 34: Geronimo Framework, Configs :: Plugin Management (2.1)
 35: Geronimo Framework, Configs :: RMI Naming (2.1)
 36: Geronimo Framework, Configs :: Shutdown (2.1)
 37: Geronimo Framework, Configs :: Transformer Agent (2.1)
 38: Geronimo Framework, Configs :: XMLBeans (2.1)
 39: Geronimo Plugins, Client :: Client (2.1)
 40: Geronimo Plugins, Client :: Deployer (2.1)
 41: Geronimo Plugins, Client :: Security (2.1)
 42: Geronimo Plugins, Connector :: Client transaction (2.1)
 43: Geronimo Plugins, Connector :: Transaction Manager (JTA11) (2.1)
 44: Geronimo Plugins, Corba :: Client Yoko (2.1)
 45: Geronimo Plugins, Spring (2.1)
 46: Geronimo Plugins, System Database :: System Database (2.1)
JMS
 47: Geronimo Plugins, ActiveMQ :: Broker (2.1)
 48: Geronimo Plugins, ActiveMQ :: Console (Jetty) (2.1)
 49: Geronimo Plugins, ActiveMQ :: Resource Adapter (2.1)
JavaEE
 50: Geronimo Framework, Configs :: JavaEE Specs (2.1)
 51: Geronimo Plugins, J2EE :: Server (2.1)
 52: Geronimo Plugins, JavaMail :: JavaMail (2.1)
JavaEE deployment
 53: Geronimo Plugins, J2EE :: Deployer (2.1)
 54: Geronimo Plugins, Jasper :: Deployer (2.1)
Jetty
 55: Geronimo Plugins, Jetty :: Clustering Builder for WADI (2.1)
 56: Geronimo Plugins, Jetty :: Deployer (2.1)
 57: Geronimo Plugins, Jetty :: Jetty 6 (2.1)
 58: Geronimo Plugins, Jetty :: Jetty 6 Clustering over WADI (2.1)
Monitoring
 59: Geronimo Plugins, Monitoring :: Agent (2.1)
 60: Geronimo Plugins, Monitoring :: Console (Jetty) (2.1)
Persistence
 61: Geronimo Plugins, OpenJPA :: Deployer (2.1)
 62: Geronimo Plugins, OpenJPA :: OpenJPA (2.1)
Portals
 63: Geronimo Plugins, Pluto :: Support (2.1)
Security
 64: Geronimo Framework, Configs :: J2EE Security (2.1)
 65: Geronimo Framework, Configs :: Server Security Configuration (2.1)
 66: Geronimo Plugins, CA Helper :: Jetty (2.1)
Web Framework
 67: Geronimo Plugins, Dojo :: Jetty6 (2.1)
 68: Geronimo Plugins, Dojo Legacy :: Jetty6 (2.1)
 69: Geronimo Plugins, Jasper :: Jasper (2.1)
 70: Geronimo Plugins, MyFaces ::

Re: deploy/assemble and ERROR GroovyRuntimeException: Ambiguous method overloading for method org.apache.geronimo.kernel.repository.Artifact#

On Thu, Feb 14, 2008 at 9:18 AM, Jarek Gawor <[EMAIL PROTECTED]> wrote:
> Yes, can you file a bug on it?

https://issues.apache.org/jira/browse/GERONIMO-3854

Jacek

-- 
Jacek Laskowski
http://www.JacekLaskowski.pl

[jira] Commented: (GERONIMO-3852) Mail misses header (blank subject and sender label not defined)

2008-02-14 Thread JIRA


[ 
https://issues.apache.org/jira/browse/GERONIMO-3852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12569028#action_12569028
 ] 

Cédric Champeau commented on GERONIMO-3852:
---

Ok, I managed to reproduce the problem, and it's not exactly what I thought : I 
created a simple project with the dependencies CXF has :


org.apache.geronimo.specs
geronimo-javamail_1.4_spec
1.2


org.apache.geronimo.specs
geronimo-activation_1.1_spec
1.0.2


And it could not send any mail because it misses the SMTP transport. Then I 
looked at my original project dependencies and found that javax.mail from Sun 
was a dependency of log4j. I added the dependency to the simple test case, it 
downloaded the javax.mail and javax.activation jars, and I ran the project once 
again :

In that case, it works perfectly... I tweaked down things a little, and found 
out that if I switched the positions of Sun's mail jar and Geronimo's 
implementation. In this case, it perfectly reproduces the problem. So this 
means that dependending on what implementation of the mail API is loaded first, 
the transport layer produces a valid message or not, which to me seems to mean 
that the geronimo mail API is not compatible with the SMTP transport 
implementation from Sun.

Hope this helps.


> Mail misses header (blank subject and sender label not defined)
> ---
>
> Key: GERONIMO-3852
> URL: https://issues.apache.org/jira/browse/GERONIMO-3852
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: specs
>Affects Versions: 1.x
> Environment: Ubuntu 7.10
>Reporter: Cédric Champeau
>Assignee: Rick McGuire
>
> As described  here 
> (http://www.jroller.com/melix/entry/apache_cxf_maven_javamail_awful), e-mails 
> produced using geronimo mail are not valid (subject is missing, sender not 
> properly set) due to the content of the DATA section. While Sun's 
> implementation produces this :
> DATA
> From: "I am the sender" 
> To: recipient-AT-somewhere-DOT-com
> Message-ID: <1484678.01202984955533.JavaMail.me-AT-server-DOT-com>
> Subject: an empty subjet for starting
> the content of my mail
> Geronimo only sends this to the SMTP server :
> DATA
> the content of my mail
> Looks like the mail misses the header.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: deploy/assemble and ERROR GroovyRuntimeException: Ambiguous method overloading for method org.apache.geronimo.kernel.repository.Artifact#

Sorry. Geronimo.

Jarek

On Thu, Feb 14, 2008 at 12:47 PM, Jacek Laskowski
<[EMAIL PROTECTED]> wrote:
> On Thu, Feb 14, 2008 at 9:18 AM, Jarek Gawor <[EMAIL PROTECTED]> wrote:
>  > Yes, can you file a bug on it?
>
>  I would have, but I didn't know what area it belonged to. Is it a
>  gshell or geronimo issue?
>
>
>
>  Jacek
>
>  --
>  Jacek Laskowski
>  http://www.JacekLaskowski.pl
>

[jira] Updated: (GERONIMO-3815) ContextManager.getCurrentContext() throws NullPointerException

2008-02-14 Thread Aman Nanner (JIRA)


 [ 
https://issues.apache.org/jira/browse/GERONIMO-3815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aman Nanner updated GERONIMO-3815:
--

Attachment: GERONIMO-3815-3.debug.patch

The error occurred in the getCurrentPrincpal() method instead of the 
getCurrentContext() method this time, and so the special traces were never 
outputted to the server log.  I've attached a new patch that will also output 
the trace logs if the NullPointerException occurs in the getCurrentPrincipal() 
method.

> ContextManager.getCurrentContext() throws NullPointerException
> --
>
> Key: GERONIMO-3815
> URL: https://issues.apache.org/jira/browse/GERONIMO-3815
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: security
>Affects Versions: 2.0.2, 2.1
>Reporter: Vamsavardhana Reddy
> Fix For: 2.0.x, 2.1.1
>
> Attachments: GERONIMO-3815-2.debug.patch, 
> GERONIMO-3815-3.debug.patch, GERONIMO-3815.debug.patch
>
>
> ContextManager.getCurrentContext() is throwing a NullPointerException.  This 
> is observed only when there is heavy load on the application.  Most likely it 
> is a threading issue where one thread is unregistering the subject while 
> another is executing getCurrentContext().  Excerpt from stacktrace given 
> below.
> 
> Caused by: java.lang.NullPointerException
> at 
> org.apache.geronimo.security.ContextManager.getCurrentContext(ContextManager.java:197)
> at 
> org.apache.geronimo.openejb.GeronimoSecurityService.isCallerAuthorized(GeronimoSecurityService.java:101)
> at 
> org.apache.openejb.core.stateless.StatelessContainer.invoke(StatelessContainer.java:142)
> at 
> org.apache.openejb.core.ivm.EjbHomeProxyHandler.create(EjbHomeProxyHandler.java:267)
> at 
> org.apache.openejb.core.ivm.EjbHomeProxyHandler._invoke(EjbHomeProxyHandler.java:158)
> at 
> org.apache.openejb.core.ivm.BaseEjbProxyHandler.invoke(BaseEjbProxyHandler.java:321)
> at 
> org.apache.openejb.util.proxy.Jdk13InvocationHandler.invoke(Jdk13InvocationHandler.java:49)
> at $Proxy16.create(Unknown Source)
> ... 53 more
>  

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Created: (GERONIMO-3853) Incompatibilities between Geronimo javamail MailDateFormat and Sun version.

2008-02-14 Thread Rick McGuire (JIRA)

Incompatibilities between Geronimo javamail MailDateFormat and Sun version.
---

 Key: GERONIMO-3853
 URL: https://issues.apache.org/jira/browse/GERONIMO-3853
 Project: Geronimo
  Issue Type: Bug
  Security Level: public (Regular issues)
  Components: mail
Reporter: Rick McGuire
Assignee: Rick McGuire
Priority: Minor


There are some incompatibilities between the Geronimo version of MailDataFormat 
and the Sun version.  When formatting the date, the Sun version formats to 

Thu, 14 Feb 2008 12:45:43 -0500 (EST)

While the Geronimo version uses 

Thu, 14 Feb 2008 12:45:43 -0500

(no timezone abbreviation).  Also, on parsing, the Sun version will accept 
dates in the IMAP internal format, which uses "-" in the date fields.  The 
Geronimo parser will not correctly parse those dates. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: deploy/assemble and ERROR GroovyRuntimeException: Ambiguous method overloading for method org.apache.geronimo.kernel.repository.Artifact#

On Thu, Feb 14, 2008 at 9:18 AM, Jarek Gawor <[EMAIL PROTECTED]> wrote:
> Yes, can you file a bug on it?

I would have, but I didn't know what area it belonged to. Is it a
gshell or geronimo issue?

Jacek

-- 
Jacek Laskowski
http://www.JacekLaskowski.pl

[jira] Assigned: (GERONIMO-3802) In plugin installer, assembling a server, add a page at the end to confirm or deny the assembly of a server package.


 [ 
https://issues.apache.org/jira/browse/GERONIMO-3802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jarek Gawor reassigned GERONIMO-3802:
-

Assignee: Jarek Gawor  (was: Joseph Leong)

> In plugin installer, assembling a server, add a page at the end to confirm or 
> deny the assembly of a server package.
> 
>
> Key: GERONIMO-3802
> URL: https://issues.apache.org/jira/browse/GERONIMO-3802
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: console
>Affects Versions: 2.1, 2.1.1
>Reporter: Joseph Leong
>Assignee: Jarek Gawor
>Priority: Minor
> Fix For: 2.1.1
>
> Attachments: GERONIMO-3802.patch
>
>
> Add a type of confirmation page at the end of Assembling a server to inform 
> the user whether the creation of there server was successful or not.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (GERONIMO-3847) The .tar.gz and .zip assembly files contain unnecessary META-INF directory


[ 
https://issues.apache.org/jira/browse/GERONIMO-3847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12569013#action_12569013
 ] 

Jarek Gawor commented on GERONIMO-3847:
---

I'm totally ok with removing the exclusion support if there is an easier and 
working solution for this META-INF problem. I just figured exclusion support 
might come useful someday.


> The .tar.gz and .zip assembly files contain unnecessary META-INF directory
> --
>
> Key: GERONIMO-3847
> URL: https://issues.apache.org/jira/browse/GERONIMO-3847
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: buildsystem
>Affects Versions: 2.1, 2.1.1, 2.2
>Reporter: Jarek Gawor
>Assignee: Jarek Gawor
> Fix For: 2.1.1, 2.2
>
>


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: deploy/assemble and ERROR GroovyRuntimeException: Ambiguous method overloading for method org.apache.geronimo.kernel.repository.Artifact#

Yes, can you file a bug on it?

I was able to mostly bypass this (and another error) by specifying
some version and artifact name (-v and -a).

Jarek

On Thu, Feb 14, 2008 at 3:13 AM, Jacek Laskowski <[EMAIL PROTECTED]> wrote:
> Hi,
>
>  Does anyone know what's wrong?
>
>  [EMAIL PROTECTED]:/> deploy/assemble
>  Listing configurations from Geronimo server
>  Connecting to Geronimo server: localhost:1099
>  Username: system
>  Password: ***
>  Connection established
>  
>   1:  Geronimo Plugins, Monitoring :: Agent DataSource (2.1)
>   2:  Geronimo Plugins, Monitoring :: Console DataSource (2.1)
>  Administration
>   3:  Geronimo Plugins, Console :: Jetty (2.1)
>   4:  Geronimo Plugins, Console :: Plugin and Deployment Portlets
>  (Jetty) (2.1)
>   5:  Geronimo Plugins, Welcome :: Jetty (2.1)
>  Clustering
>   6:  Geronimo Plugins, Clustering :: Clustering (2.1)
>   7:  Geronimo Plugins, Clustering :: Farming (2.1)
>   8:  Geronimo Plugins, Clustering :: WADI (2.1)
>  Connector
>   9:  Geronimo Plugins, Connector :: Deployer (2.1)
>  Databases
>   10: Geronimo Plugins, System Database :: Console (Jetty) (2.1)
>  Debug
>   11: Geronimo Plugins, Debug Views :: Jetty (2.1)
>  Deployment
>   12: Geronimo Framework, Configs :: CLI Upgrade (2.1)
>   13: Geronimo Framework, Configs :: JSR-88 CLI (2.1)
>   14: Geronimo Framework, Configs :: JSR-88 DeploymentFactory (2.1)
>   15: Geronimo Framework, Configs :: Offline Deployer (2.1)
>   16: Geronimo Framework, Configs :: Online Deployer (2.1)
>   17: Geronimo Plugins, J2EE :: JSR-88 EAR Configurer (2.1)
>   18: Geronimo Plugins, J2EE :: JSR-88 JAR Configurer (2.1)
>   19: Geronimo Plugins, J2EE :: JSR-88 RAR Configurer (2.1)
>   20: Geronimo Plugins, J2EE :: JSR-88 WAR Configurer (2.1)
>   21: Geronimo Plugins, Remote Deploy :: Jetty (2.1)
>  Development tools
>   22: Geronimo Plugins, Plan Creator :: Jetty (2.1)
>  EJB
>   23: Geronimo Plugins, Corba :: Yoko ORB (2.1)
>   24: Geronimo Plugins, MEJB :: Config (2.1)
>  EJB Container
>   25: Geronimo Plugins, Corba :: Deployer (2.1)
>   26: Geronimo Plugins, OpenEJB :: Deployer (2.1)
>   27: Geronimo Plugins, OpenEJB :: OpenEJB (2.1)
>  Example
>   28: Geronimo Plugins, Shared Library (2.1)
>  Fluff
>   29: Geronimo Plugins, Hot Deploy :: Deployer (2.1)
>  Geronimo Core
>   30: Geronimo Assemblies :: Boilerplate Minimal (2.1)
>   31: Geronimo Framework, Configs :: Client System (2.1)
>   32: Geronimo Framework, Configs :: GBean Deployer (2.1)
>   33: Geronimo Framework, Configs :: J2EE System (2.1)
>   34: Geronimo Framework, Configs :: Plugin Management (2.1)
>   35: Geronimo Framework, Configs :: RMI Naming (2.1)
>   36: Geronimo Framework, Configs :: Shutdown (2.1)
>   37: Geronimo Framework, Configs :: Transformer Agent (2.1)
>   38: Geronimo Framework, Configs :: XMLBeans (2.1)
>   39: Geronimo Plugins, Client :: Client (2.1)
>   40: Geronimo Plugins, Client :: Deployer (2.1)
>   41: Geronimo Plugins, Client :: Security (2.1)
>   42: Geronimo Plugins, Connector :: Client transaction (2.1)
>   43: Geronimo Plugins, Connector :: Transaction Manager (JTA11) (2.1)
>   44: Geronimo Plugins, Corba :: Client Yoko (2.1)
>   45: Geronimo Plugins, Spring (2.1)
>   46: Geronimo Plugins, System Database :: System Database (2.1)
>  JMS
>   47: Geronimo Plugins, ActiveMQ :: Broker (2.1)
>   48: Geronimo Plugins, ActiveMQ :: Console (Jetty) (2.1)
>   49: Geronimo Plugins, ActiveMQ :: Resource Adapter (2.1)
>  JavaEE
>   50: Geronimo Framework, Configs :: JavaEE Specs (2.1)
>   51: Geronimo Plugins, J2EE :: Server (2.1)
>   52: Geronimo Plugins, JavaMail :: JavaMail (2.1)
>  JavaEE deployment
>   53: Geronimo Plugins, J2EE :: Deployer (2.1)
>   54: Geronimo Plugins, Jasper :: Deployer (2.1)
>  Jetty
>   55: Geronimo Plugins, Jetty :: Clustering Builder for WADI (2.1)
>   56: Geronimo Plugins, Jetty :: Deployer (2.1)
>   57: Geronimo Plugins, Jetty :: Jetty 6 (2.1)
>   58: Geronimo Plugins, Jetty :: Jetty 6 Clustering over WADI (2.1)
>  Monitoring
>   59: Geronimo Plugins, Monitoring :: Agent (2.1)
>   60: Geronimo Plugins, Monitoring :: Console (Jetty) (2.1)
>  Persistence
>   61: Geronimo Plugins, OpenJPA :: Deployer (2.1)
>   62: Geronimo Plugins, OpenJPA :: OpenJPA (2.1)
>  Portals
>   63: Geronimo Plugins, Pluto :: Support (2.1)
>  Security
>   64: Geronimo Framework, Configs :: J2EE Security (2.1)
>   65: Geronimo Framework, Configs :: Server Security Configuration (2.1)
>   66: Geronimo Plugins, CA Helper :: Jetty (2.1)
>  Web Framework
>   67: Geronimo Plugins, Dojo :: Jetty6 (2.1)
>   68: Geronimo Plugins, Dojo Legacy :: Jetty6 (2.1)
>   69: Geronimo Plugins, Jasper :: Jasper (2.1)
>   70: Geronimo Plugins, MyFaces :: Deployer (2.1)
>   71:

Re: framework assembly distribution?

2008-02-14 Thread David Jencks



On Feb 14, 2008, at 8:30 AM, Joe Bohn wrote:



With our 2.1 distribution (as with earlier distributions) we are  
only providing the javaee5 & minimal assemblies.  Are we ever  
planning to make the geronimo-framework assembly available in a  
distribution so that a user could start from scratch (not even a  
web container) and build up a server by installing plugins?


That was the original intent when we created this assembly.  I know  
that the originally framework included enough deployment capability  
to deploy plugins.  However, I'm not certain that is still the case  
(I haven't tried in a long time).  Assuming you can still install  
plugins (or we add that back in), I think it makes sense to  
distribute this assembly. BTW, I'm not proposing this for 2.1 given  
that it is nearly completely baked.


All the framework assembly can do is install plugins.  I think we  
should definitely distribute it in the future and I am proposing we  
distribute it for 2.1 as well.  IIUC in any case it will get into the  
maven repos, so adding it to the official download page shouldn't be  
too hard.


thanks for noticing it was missing :-)
david jencks



What do others think?

Joe

[jira] Commented: (GERONIMO-3852) Mail misses header (blank subject and sender label not defined)

2008-02-14 Thread Rick McGuire (JIRA)


[ 
https://issues.apache.org/jira/browse/GERONIMO-3852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12569007#action_12569007
 ] 

Rick McGuire commented on GERONIMO-3852:


Could you attach a sample program that demonstrates the issue?  I'm not seeing 
a problem with the data getting sent to the SMTP server.  Here's the session 
debug output from the latest Geronimo javamail version: 

220 relay02.pair.com ESMTP
EHLO BigRixx
250-relay02.pair.com
250-PIPELINING
250 8BITMIME
MAIL FROM: <[EMAIL PROTECTED]>
250 ok
RCPT TO: <[EMAIL PROTECTED]>
250 ok
DATA
354 Please start mail input.
Message-ID: <[EMAIL PROTECTED]>
Date: Thu, 14 Feb 2008 12:10:07 -0500
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: This is a JavaMail API Test
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Mailer: JavaMail API

..
..Sample Message
..
..
More sample message

.
250 Mail queued for delivery.



and the same session using the Sun version:  

EHLO BigRixx
250-relay02.pair.com
250-PIPELINING
250 8BITMIME
DEBUG SMTP: Found extension "PIPELINING", arg ""
DEBUG SMTP: Found extension "8BITMIME", arg ""
DEBUG SMTP: use8bit false
MAIL FROM:<[EMAIL PROTECTED]>
250 ok
RCPT TO:<[EMAIL PROTECTED]>
250 ok
DEBUG SMTP: Verified Addresses
DEBUG SMTP:   [EMAIL PROTECTED]
DATA
354 Please start mail input.
Message-ID: <[EMAIL PROTECTED]>
Date: Thu, 14 Feb 2008 12:09:47 -0500 (EST)
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: This is a JavaMail API Test
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Mailer: JavaMail API

..
..Sample Message
..
..
More sample message

.
250 Mail queued for delivery.

These are identical except for the "(EST)" that the Sun version added to the 
date string.  

> Mail misses header (blank subject and sender label not defined)
> ---
>
> Key: GERONIMO-3852
> URL: https://issues.apache.org/jira/browse/GERONIMO-3852
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: specs
>Affects Versions: 1.x
> Environment: Ubuntu 7.10
>Reporter: Cédric Champeau
>Assignee: Rick McGuire
>
> As described  here 
> (http://www.jroller.com/melix/entry/apache_cxf_maven_javamail_awful), e-mails 
> produced using geronimo mail are not valid (subject is missing, sender not 
> properly set) due to the content of the DATA section. While Sun's 
> implementation produces this :
> DATA
> From: "I am the sender" 
> To: recipient-AT-somewhere-DOT-com
> Message-ID: <1484678.01202984955533.JavaMail.me-AT-server-DOT-com>
> Subject: an empty subjet for starting
> the content of my mail
> Geronimo only sends this to the SMTP server :
> DATA
> the content of my mail
> Looks like the mail misses the header.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (GERONIMO-3847) The .tar.gz and .zip assembly files contain unnecessary META-INF directory

2008-02-14 Thread David Jencks (JIRA)


[ 
https://issues.apache.org/jira/browse/GERONIMO-3847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12569005#action_12569005
 ] 

David Jencks commented on GERONIMO-3847:


I'm not sure what I think about the additional complexity of an exclude 
specification.  I think we could also solve this particular problem by putting 
the content to be unpacked in a non-root directory in the plugin.

> The .tar.gz and .zip assembly files contain unnecessary META-INF directory
> --
>
> Key: GERONIMO-3847
> URL: https://issues.apache.org/jira/browse/GERONIMO-3847
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: buildsystem
>Affects Versions: 2.1, 2.1.1, 2.2
>Reporter: Jarek Gawor
>Assignee: Jarek Gawor
> Fix For: 2.1.1, 2.2
>
>


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Concurrency Utilities for Java EE

Folks,

For the past few weeks I've been working on the Concurrency Utilities
for Java EE specification implementation. The Concurrency Utilities
for Java EE specification is a draft specification (see
http://gee.cs.oswego.edu/dl/concurrencyee-interest/ for more info)
that is supposed to replace the JSR-236 (Timer API) and JSR-237 (Work
Manager API) specifications and become part of Java EE 6.  The
Concurrency Utilities for Java EE specification basically extends the
java.util.concurrent.Executor API and adds managed environment
qualities to the tasks executed via the Executor. That is, the
background tasks can execute with the same environment as the
application that started it.

I have a little bit of code but it's definitely not complete or fully
functional and still needs a lot of work (e.g. better integration with
Geronimo, etc.). I would like to donate this code to Geronimo, and
continue to work on it there as a community.

Now, the cool thing is that this implementation might become the
official Reference Implementation (RI) for this spec. I've talked with
the IBM co-spec lead and there is a good chance of that happening if
we also commit to writing a TCK for it. And I think that would be a
great opportunity for Geronimo to show some leadership in the Java EE
spec area.

Even if the RI thing does not work out or this specification does not
become part of Java EE 6, I still think this functionally would be a
good addition to Geronimo.

What do people think? Thoughts, any concerns?

Jarek

[jira] Assigned: (GERONIMO-3852) Mail misses header (blank subject and sender label not defined)

2008-02-14 Thread Rick McGuire (JIRA)


 [ 
https://issues.apache.org/jira/browse/GERONIMO-3852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rick McGuire reassigned GERONIMO-3852:
--

Assignee: Rick McGuire

> Mail misses header (blank subject and sender label not defined)
> ---
>
> Key: GERONIMO-3852
> URL: https://issues.apache.org/jira/browse/GERONIMO-3852
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: specs
>Affects Versions: 1.x
> Environment: Ubuntu 7.10
>Reporter: Cédric Champeau
>Assignee: Rick McGuire
>
> As described  here 
> (http://www.jroller.com/melix/entry/apache_cxf_maven_javamail_awful), e-mails 
> produced using geronimo mail are not valid (subject is missing, sender not 
> properly set) due to the content of the DATA section. While Sun's 
> implementation produces this :
> DATA
> From: "I am the sender" 
> To: recipient-AT-somewhere-DOT-com
> Message-ID: <1484678.01202984955533.JavaMail.me-AT-server-DOT-com>
> Subject: an empty subjet for starting
> the content of my mail
> Geronimo only sends this to the SMTP server :
> DATA
> the content of my mail
> Looks like the mail misses the header.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: [DISCUSS] Geronimo Server 2.1 and Geronimo TxManager 2.1.1 Releases

Also, I found something interesting with the start-server command.  If
I issue the start-server command to start the server, then I can
shutdown the server using the shutdown.bat or admin console.

However, there is no change in the start-server window which it still
says "Geronimo Application Server started" and nothing after it.
This has been very confusing to me, coz I thought my server is still
running after I forgot I've already stopped it earlier on.   Is this a
known prob?

P.S. sorry for trying these late - i just got back from a long long leave...

lin

On Thu, Feb 14, 2008 at 11:29 AM, Lin Sun <[EMAIL PROTECTED]> wrote:
> Ok if I change the default, then I won't be able to shutdown the
>  server using stop-server (with the correct or wrong credential).   In
>  this case, only shutdown.bat/sh works.
>
>  Lin
>
>
>
>  On Thu, Feb 14, 2008 at 11:23 AM, Lin Sun <[EMAIL PROTECTED]> wrote:
>  > No, I didn't change the server defaults... I can try changing the
>  >  defaults and report back.
>  >
>  >  Lin
>  >
>  >
>  >
>  >  On Thu, Feb 14, 2008 at 11:09 AM, Joe Bohn <[EMAIL PROTECTED]> wrote:
>  >  > Lin Sun wrote:
>  >  >  > I just downloaded the jee5 tomcat assembly and tried the new
>  >  >  > start-server and stop-server commands on winxp.   The stop-server
>  >  >  > commands shutdown the server with a wrong password!
>  >  >  >
>  >  >  > C:\working\gt21\bin>stop-server
>  >  >  > Stopping Geronimo server: localhost:1099
>  >  >  > Username: system
>  >  >  > Password: *
>  >  >  > Shutdown request has been issued
>  >  >  >
>  >  >  > Has anyone seen this?  Not sure if stop-server would work remotely...
>  >  >  >
>  >  >
>  >  >  This sounds like a side effect of the same problem Jarek reported.  Did
>  >  >  you change the id/pw from the default?  If stop-server always uses the
>  >  >  default credentials and you did not change the default then it would
>  >  >  shut the server down even if you specify incorrect credentials on the
>  >  >  command.
>  >  >
>  >  >  Joe
>  >  >
>  >  >
>  >  >
>  >
>

[BUILD] 2.2: Failed for Revision: 627750

2008-02-14 Thread gawor

Geronimo Revision: 627750 built with tests included
 
See the full build-0900.log file at 
http://geronimo.apache.org/maven/server/binaries/trunk/20080214/build-0900.log
 
Download the binaries from 
http://geronimo.apache.org/maven/server/binaries/trunk/20080214
[INFO] BUILD SUCCESSFUL
[INFO] 
[INFO] Total time: 30 minutes 5 seconds
[INFO] Finished at: Thu Feb 14 10:08:29 EST 2008
[INFO] Final Memory: 304M/1009M
[INFO] 
 
TESTSUITE RESULTS (Failures only)
=
See detailed results at 
http://geronimo.apache.org/maven/server/testsuite/ResultsSummary.html
 
Assembly: tomcat
=
See the full test.log file at 
http://geronimo.apache.org/maven/server/binaries/trunk/20080214/logs-0900-tomcat/test.log
 
 
Assembly: jetty
=
See the full test.log file at 
http://geronimo.apache.org/maven/server/binaries/trunk/20080214/logs-0900-jetty/test.log
 
[INFO] Running console-testsuite.advance-test
[INFO] Tests run: 13, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 71.209 
sec <<< FAILURE!

[jira] Created: (GERONIMO-3852) Mail misses header (blank subject and sender label not defined)

2008-02-14 Thread JIRA

Mail misses header (blank subject and sender label not defined)
---

 Key: GERONIMO-3852
 URL: https://issues.apache.org/jira/browse/GERONIMO-3852
 Project: Geronimo
  Issue Type: Bug
  Security Level: public (Regular issues)
  Components: specs
Affects Versions: 1.x
 Environment: Ubuntu 7.10
Reporter: Cédric Champeau


As described  here 
(http://www.jroller.com/melix/entry/apache_cxf_maven_javamail_awful), e-mails 
produced using geronimo mail are not valid (subject is missing, sender not 
properly set) due to the content of the DATA section. While Sun's 
implementation produces this :

DATA
From: "I am the sender" 
To: recipient-AT-somewhere-DOT-com
Message-ID: <1484678.01202984955533.JavaMail.me-AT-server-DOT-com>
Subject: an empty subjet for starting

the content of my mail


Geronimo only sends this to the SMTP server :

DATA
the content of my mail

Looks like the mail misses the header.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

framework assembly distribution?

2008-02-14 Thread Joe Bohn



With our 2.1 distribution (as with earlier distributions) we are only 
providing the javaee5 & minimal assemblies.  Are we ever planning to 
make the geronimo-framework assembly available in a distribution so that 
a user could start from scratch (not even a web container) and build up 
a server by installing plugins?


That was the original intent when we created this assembly.  I know that 
the originally framework included enough deployment capability to deploy 
plugins.  However, I'm not certain that is still the case (I haven't 
tried in a long time).  Assuming you can still install plugins (or we 
add that back in), I think it makes sense to distribute this assembly. 
BTW, I'm not proposing this for 2.1 given that it is nearly completely 
baked.


What do others think?

Joe

Re: [DISCUSS] Geronimo Server 2.1 and Geronimo TxManager 2.1.1 Releases

Ok if I change the default, then I won't be able to shutdown the
server using stop-server (with the correct or wrong credential).   In
this case, only shutdown.bat/sh works.

Lin

On Thu, Feb 14, 2008 at 11:23 AM, Lin Sun <[EMAIL PROTECTED]> wrote:
> No, I didn't change the server defaults... I can try changing the
>  defaults and report back.
>
>  Lin
>
>
>
>  On Thu, Feb 14, 2008 at 11:09 AM, Joe Bohn <[EMAIL PROTECTED]> wrote:
>  > Lin Sun wrote:
>  >  > I just downloaded the jee5 tomcat assembly and tried the new
>  >  > start-server and stop-server commands on winxp.   The stop-server
>  >  > commands shutdown the server with a wrong password!
>  >  >
>  >  > C:\working\gt21\bin>stop-server
>  >  > Stopping Geronimo server: localhost:1099
>  >  > Username: system
>  >  > Password: *
>  >  > Shutdown request has been issued
>  >  >
>  >  > Has anyone seen this?  Not sure if stop-server would work remotely...
>  >  >
>  >
>  >  This sounds like a side effect of the same problem Jarek reported.  Did
>  >  you change the id/pw from the default?  If stop-server always uses the
>  >  default credentials and you did not change the default then it would
>  >  shut the server down even if you specify incorrect credentials on the
>  >  command.
>  >
>  >  Joe
>  >
>  >
>  >
>

Re: [DISCUSS] Geronimo Server 2.1 and Geronimo TxManager 2.1.1 Releases

No, I didn't change the server defaults... I can try changing the
defaults and report back.

Lin

On Thu, Feb 14, 2008 at 11:09 AM, Joe Bohn <[EMAIL PROTECTED]> wrote:
> Lin Sun wrote:
>  > I just downloaded the jee5 tomcat assembly and tried the new
>  > start-server and stop-server commands on winxp.   The stop-server
>  > commands shutdown the server with a wrong password!
>  >
>  > C:\working\gt21\bin>stop-server
>  > Stopping Geronimo server: localhost:1099
>  > Username: system
>  > Password: *
>  > Shutdown request has been issued
>  >
>  > Has anyone seen this?  Not sure if stop-server would work remotely...
>  >
>
>  This sounds like a side effect of the same problem Jarek reported.  Did
>  you change the id/pw from the default?  If stop-server always uses the
>  default credentials and you did not change the default then it would
>  shut the server down even if you specify incorrect credentials on the
>  command.
>
>  Joe
>
>
>

Re: svn commit: r627785 - /geronimo/devtools/eclipse-plugin/tags/2.0.0/plugins/org.apache.geronimo.st.core/src/org/apache/geronimo/st/core/operations/SharedLibEntryCreationOperation.java

2008-02-14 Thread Donald Woods


Hey, you're not supposed to modify the contents of a Tag.

-Donald

[EMAIL PROTECTED] wrote:

Author: mcconne
Date: Thu Feb 14 07:56:36 2008
New Revision: 627785

URL: http://svn.apache.org/viewvc?rev=627785&view=rev
Log:
GERONIMODEVTOOLS-282 Fix duplicate folders in resource classpath entries

Modified:

geronimo/devtools/eclipse-plugin/tags/2.0.0/plugins/org.apache.geronimo.st.core/src/org/apache/geronimo/st/core/operations/SharedLibEntryCreationOperation.java

Modified: 
geronimo/devtools/eclipse-plugin/tags/2.0.0/plugins/org.apache.geronimo.st.core/src/org/apache/geronimo/st/core/operations/SharedLibEntryCreationOperation.java
URL: 
http://svn.apache.org/viewvc/geronimo/devtools/eclipse-plugin/tags/2.0.0/plugins/org.apache.geronimo.st.core/src/org/apache/geronimo/st/core/operations/SharedLibEntryCreationOperation.java?rev=627785&r1=627784&r2=627785&view=diff
==
--- 
geronimo/devtools/eclipse-plugin/tags/2.0.0/plugins/org.apache.geronimo.st.core/src/org/apache/geronimo/st/core/operations/SharedLibEntryCreationOperation.java
 (original)
+++ 
geronimo/devtools/eclipse-plugin/tags/2.0.0/plugins/org.apache.geronimo.st.core/src/org/apache/geronimo/st/core/operations/SharedLibEntryCreationOperation.java
 Thu Feb 14 07:56:36 2008
@@ -283,7 +283,7 @@
// if no outputlocation, output path will get 
picked up by
// default output path
if(includeOutputLocations && 
entry.getOutputLocation() != null) {
-   path = 
project.getLocation().append(entry.getOutputLocation()).addTrailingSeparator().toOSString();
+path = 
project.getLocation().removeLastSegments(1).append(entry.getOutputLocation()).addTrailingSeparator().toOSString();
}
} else {
path = resolveVarOrLibEntry(entry);





smime.p7s
Description: S/MIME Cryptographic Signature

Re: [DISCUSS] Geronimo Server 2.1 and Geronimo TxManager 2.1.1 Releases

2008-02-14 Thread Joe Bohn


Lin Sun wrote:

I just downloaded the jee5 tomcat assembly and tried the new
start-server and stop-server commands on winxp.   The stop-server
commands shutdown the server with a wrong password!

C:\working\gt21\bin>stop-server
Stopping Geronimo server: localhost:1099
Username: system
Password: *
Shutdown request has been issued

Has anyone seen this?  Not sure if stop-server would work remotely...



This sounds like a side effect of the same problem Jarek reported.  Did 
you change the id/pw from the default?  If stop-server always uses the 
default credentials and you did not change the default then it would 
shut the server down even if you specify incorrect credentials on the 
command.


Joe

[jira] Resolved: (GERONIMODEVTOOLS-282) Classpath entries to resources in SharedLIb incorrect causing them not to be found when running on the Geronimo server

2008-02-14 Thread Tim McConnell (JIRA)


 [ 
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tim McConnell resolved GERONIMODEVTOOLS-282.


Resolution: Fixed

Resolved with change to SharedLibEntryCreationOperation in revision 627785

> Classpath entries to resources in SharedLIb incorrect causing them not to be 
> found when running on the Geronimo server
> --
>
> Key: GERONIMODEVTOOLS-282
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-282
> Project: Geronimo-Devtools
>  Issue Type: Bug
>Affects Versions: 2.0.0
>Reporter: Tim McConnell
>Assignee: Tim McConnell
> Fix For: 2.0.2, 2.0.x, 2.1.0
>
>
> The GEP is duplicating the output folder in classpath entries for resources 
> in the sharedlib manifest entry. For example, for a project with a name of 
> project1 in the Eclipse workspace the classpath entry in the manifest shows 
> up as:
> file:/C:/workspace/projects/project1/target/classes/
> file:/C:/workspace/projects/project1/project1/src/main/resources/
> file:/C:/workspace/projects/project1/project1/src/test/resources/
> When they should be:
> file:/C:/workspace/projects/project1/target/classes/
> file:/C:/workspace/projects/project1/src/main/resources/
> file:/C:/workspace/projects/project1/src/test/resources/

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: [DISCUSS] Geronimo Server 2.1 and Geronimo TxManager 2.1.1 Releases

I just downloaded the jee5 tomcat assembly and tried the new
start-server and stop-server commands on winxp.   The stop-server
commands shutdown the server with a wrong password!

C:\working\gt21\bin>stop-server
Stopping Geronimo server: localhost:1099
Username: system
Password: *
Shutdown request has been issued

Has anyone seen this?  Not sure if stop-server would work remotely...

Lin


On Wed, Feb 13, 2008 at 7:20 PM, Kevan Miller <[EMAIL PROTECTED]> wrote:
>
>  On Feb 13, 2008, at 2:46 PM, Jarek Gawor wrote:
>  > -0.5.
>  >
>  > The bin/stop-server command ignores username/password values I provide
>  > and instead always uses the default credentials (system/manager).
>
>  OK. Well, that's not great, but neither is it a security exposure.
>  There's always shutdown.sh and the good old kill command. Personally,
>  I put this in a bug category...
>
>  While on the subject, gsh commands will be our preferred command
>  structure. Excepting geronimo.sh, I'd be in favor of removing the
>  deploy/startup/shutdown commands in our future releases.
>
>  >
>  >
>  > Also, looks like there is an unnecessary META-INF/ directory under the
>  > main installation directory.
>
>  K. We can look at that, next release.
>
>  --kevan
>

[jira] Created: (GERONIMODEVTOOLS-282) Classpath entries to resources in SharedLIb incorrect causing them not to be found when running on the Geronimo server

2008-02-14 Thread Tim McConnell (JIRA)

Classpath entries to resources in SharedLIb incorrect causing them not to be 
found when running on the Geronimo server
--

 Key: GERONIMODEVTOOLS-282
 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-282
 Project: Geronimo-Devtools
  Issue Type: Bug
Affects Versions: 2.0.0
Reporter: Tim McConnell
Assignee: Tim McConnell
 Fix For: 2.0.2, 2.0.x, 2.1.0


The GEP is duplicating the output folder in classpath entries for resources in 
the sharedlib manifest entry. For example, for a project with a name of 
project1 in the Eclipse workspace the classpath entry in the manifest shows up 
as:

file:/C:/workspace/projects/project1/target/classes/
file:/C:/workspace/projects/project1/project1/src/main/resources/
file:/C:/workspace/projects/project1/project1/src/test/resources/

When they should be:

file:/C:/workspace/projects/project1/target/classes/
file:/C:/workspace/projects/project1/src/main/resources/
file:/C:/workspace/projects/project1/src/test/resources/

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: daytrader not compiling in trunk

2008-02-14 Thread B.J. Reed

Chris, that's actually part of what's confusing me.  I only have the 1.5 
JDK installed.  However, when I do a mvn help:effective-pom, it looks 
like it is trying to use the 1.4 jdk for javadocs (see source line)


 
   target/site
   
 
   maven-javadoc-plugin
   2.1
   
 128m
 512
 true
 true
 false
 1.4
 true
 
   http://java.sun.com/j2se/1.5.0/docs/api/
   http://java.sun.com/j2se/1.4.2/docs/api/
   http://java.sun.com/j2se/1.3/docs/api/
   http://java.sun.com/javaee/5/docs/api/
   http://java.sun.com/j2ee/1.4/docs/api/
   http://java.sun.com/j2ee/sdk_1.3/techdocs/api/
   
http://jakarta.apache.org/commons/collections/apidocs

   http://jakarta.apache.org/commons/logging/apidocs/
   http://www.junit.org/junit/javadoc/
   http://logging.apache.org/log4j/docs/api/
   http://jakarta.apache.org/regexp/apidocs/
   http://jakarta.apache.org/velocity/api/
 
   
 

I do see a similar section for the 2.2-SNAPSHOT that has 1.5 for its 
source, but I'm not exactly sure how to get it to use that one. I'm not 
sure if I'm heading in the right direction or where this parent pom is 
found. 


--B.J.

Christopher Blythe wrote:
you need a 1.5 JDK to compile the source in trunk because of the 
annotations for EE5... if you want to use JDK 1.4.X and J2EE 1.4, i 
would suggest looking at the 1.2 branch.


hope this helps...

On Tue, Feb 5, 2008 at 12:57 PM, B.J. Reed <[EMAIL PROTECTED] 
> wrote:


Hi, I've run into a problem with building the trunk version of
daytrader.

When I do mvn site, I am getting about 15 - 20 errors all similar
to the
ones below, but I can't seem to figure out exactly what in the pom.xml
is setting the source to 1.4 and how to fix it.

First 3 errors:
Embedded error: Error rendering Maven report: Exit code: 1 -

C:\g\daytrader\trunk\modules\ejb\src\main\java\org\apache\geronimo\samples\daytrader\AccountDataBea
n.java:30: annotations are not supported in -source 1.4 (try
-source 1.5
to enable annotations)
@Entity(name = "accountejb")
 ^

C:\g\daytrader\trunk\modules\ejb\src\main\java\org\apache\geronimo\samples\daytrader\AccountDataBean.java:79:
generics are not supported in -source 1.4 (try -source 1.5 to enable
generics)
   private Collection orders;
 ^

C:\g\daytrader\trunk\modules\ejb\src\main\java\org\apache\geronimo\samples\daytrader\AccountProfileDataBean.java:23:
annotations are not supported in -source 1.4 (try -source 1.5 to
enable
annotations)
@Entity(name = "accountprofileejb")
 ^

Thanks in advance for any help,

B.J.




--
"I say never be complete, I say stop being perfect, I say let... lets 
evolve, let the chips fall where they may." - Tyler Durden

Re: Round trip debugging of Geronimo in Eclipse

2008-02-14 Thread Dan Becker

Dan Becker wrote:
> 
> I have difficulty taking the updated class back to the runtime to further
> debug it.
> 

Thanks for all the pointers and suggestions. I have updated the Development
Wiki to include a section on how to update your runtime for Eclipse:
http://cwiki.apache.org/confluence/display/GMOxDEV/Developing+Geronimo+in+Eclipse#DevelopingGeronimoinEclipse-MakingGeronimoUpdatesAppearinEclipse
Making Geronimo Updates Appear in Eclipse 

Thanks, Dan

-- 
View this message in context: 
http://www.nabble.com/Round-trip-debugging-of-Geronimo-in-Eclipse-tp15419998s134p15481215.html
Sent from the Apache Geronimo - Dev mailing list archive at Nabble.com.

Re: Geronimo in year 2008

On Tue, Feb 12, 2008 at 3:26 PM, Kevan Miller <[EMAIL PROTECTED]> wrote:
> Things that I haven't seen mentioned, yet:
>
>  EE 6 -- we should be seeing an initial EE 6 spec, soon. As other
>  projects begin implementing EE 6 capabilities, I expect that we'll be
>  rolling them into Geronimo. There are also new specifications which we
>  may need to implement ourselves. I know that Jarek has looked at the
>  Concurrency Utilities specification (which may be part of EE 6).
>  Hoping he can tell us about that...

Yes. I'll start a new thread on that topic.

Jarek

[jira] Commented: (GERONIMO-3728) Improve visibility of installed apps from the console


[ 
https://issues.apache.org/jira/browse/GERONIMO-3728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12568955#action_12568955
 ] 

Joseph Leong commented on GERONIMO-3728:


Thanks Joe!

Looks like this will give me a lead to separate the two groups.

Currently working on condensing everything and then I will implement separating 
them.

> Improve visibility of installed apps from the console
> -
>
> Key: GERONIMO-3728
> URL: https://issues.apache.org/jira/browse/GERONIMO-3728
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: console
>Reporter: Hernan Cunico
>Assignee: Joseph Leong
>Priority: Minor
>
> Currently, out of the box, there are enough installed apps that require 
> scrolling to browse them all. 
> It would improve visibility if we can reduce the amount of info displayed on 
> the first screen. Listing just application "names" and status while providing 
> links to app details would help. Adding check boxes for commands will help 
> too allowing performing the same command on multiple apps.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: daytrader not compiling in trunk

2008-02-14 Thread Christopher Blythe

you need a 1.5 JDK to compile the source in trunk because of the annotations
for EE5... if you want to use JDK 1.4.X and J2EE 1.4, i would suggest
looking at the 1.2 branch.

hope this helps...

On Tue, Feb 5, 2008 at 12:57 PM, B.J. Reed <[EMAIL PROTECTED]> wrote:

> Hi, I've run into a problem with building the trunk version of daytrader.
>
> When I do mvn site, I am getting about 15 - 20 errors all similar to the
> ones below, but I can't seem to figure out exactly what in the pom.xml
> is setting the source to 1.4 and how to fix it.
>
> First 3 errors:
> Embedded error: Error rendering Maven report: Exit code: 1 -
>
> C:\g\daytrader\trunk\modules\ejb\src\main\java\org\apache\geronimo\samples\daytrader\AccountDataBea
> n.java:30: annotations are not supported in -source 1.4 (try -source 1.5
> to enable annotations)
> @Entity(name = "accountejb")
>  ^
>
> C:\g\daytrader\trunk\modules\ejb\src\main\java\org\apache\geronimo\samples\daytrader\AccountDataBean.java:79:
> generics are not supported in -source 1.4 (try -source 1.5 to enable
> generics)
>private Collection orders;
>  ^
>
> C:\g\daytrader\trunk\modules\ejb\src\main\java\org\apache\geronimo\samples\daytrader\AccountProfileDataBean.java:23:
> annotations are not supported in -source 1.4 (try -source 1.5 to enable
> annotations)
> @Entity(name = "accountprofileejb")
>  ^
>
> Thanks in advance for any help,
>
> B.J.
>



-- 
"I say never be complete, I say stop being perfect, I say let... lets
evolve, let the chips fall where they may." - Tyler Durden

Re: [Fwd: Geronimo Documentation - 5-minute Tutorial on Enterprise Application Development with Eclipse and Geronimo]

2008-02-14 Thread Hernan Cunico




Jacek Laskowski wrote:

On Feb 12, 2008 10:39 AM, Hernan Cunico <[EMAIL PROTECTED]> wrote:

Ok, so I'll start updating the tutorial then.

I'll put it in a new home under Tutorials -> EJB applications.


You mean the 5-minute tutorial? I'm fine with it.



yes, I retested/updated it and put it under Tutorials ->EJB, here is the link 
http://cwiki.apache.org/GMOxDOC21/5-minute-tutorial-on-enterprise-application-development-with-eclipse-and-geronimo.html

I'm gonna start linking the tutorials from the Samples space too as we did in 
previous releases.

Cheers!
Hernan


Jacek

Re: [VOTE] Geronimo Server 2.1 and Geronimo TxManager 2.1.1 Releases

2008-02-14 Thread Paul McMahan


+1


Looks good except for the Plugins portlet which is not working for  
me.  Several actions in that portlet lead to:

javax.portlet.PortletSecurityException: No Supported
	 
org.apache.pluto.driver.services.container.PortletURLProviderImpl.setSec 
ure(PortletURLProviderImpl.java:67)
	org.apache.pluto.core.PortletContainerImpl.doAction 
(PortletContainerImpl.java:261)
	org.apache.pluto.driver.PortalDriverServlet.doGet 
(PortalDriverServlet.java:112)
	org.apache.pluto.driver.PortalDriverServlet.doPost 
(PortalDriverServlet.java:158)

javax.servlet.http.HttpServlet.service(HttpServlet.java:713)
javax.servlet.http.HttpServlet.service(HttpServlet.java:806)

But I don't think that defect should hold up the release since the  
cli is still available and appears to be working ok.



Best wishes,
Paul

On Feb 10, 2008, at 10:46 PM, Kevan Miller wrote:


All,
I've prepared a 2.1 release candidate for your review and vote.  
I've also prepared a 2.1.1 TxManager release candidate for review  
and vote. For simplicity, I'm holding a single vote for both  
releases. The Geronimo server release is dependent upon the  
TxManager 2.1.1 release.


The source for the Geronimo 2.1 release currently resides here:
https://svn.apache.org/repos/asf/geronimo/server/branches/2.1.0

When the release vote is approved, I will svn mv the code to
https://svn.apache.org/repos/asf/geronimo/server/tags/2.1.0

An archive of this source code can be found here:
http://people.apache.org/~kevan/release-votes/G-2.1/geronimo-2.1- 
dist/geronimo-2.1-src.tar.gz


http://people.apache.org/~kevan/release-votes/G-2.1/geronimo-2.1- 
dist/ contains the 8 Java EE and Minimal server binary  
distributions to be released (tomcat/jetty, Java EE/Minimal, tar/ 
zip) as well as the RELEASE_NOTES and source code archives for the  
release.


For your convenience, here are pointers to the urls for the  
distributions in zip format:
http://people.apache.org/~kevan/release-votes/G-2.1/geronimo-2.1- 
dist/geronimo-jetty6-javaee5-2.1-bin.zip
http://people.apache.org/~kevan/release-votes/G-2.1/geronimo-2.1- 
dist/geronimo-jetty6-minimal-2.1-bin.zip
http://people.apache.org/~kevan/release-votes/G-2.1/geronimo-2.1- 
dist/geronimo-tomcat6-javaee5-2.1-bin.zip
http://people.apache.org/~kevan/release-votes/G-2.1/geronimo-2.1- 
dist/geronimo-tomcat6-minimal-2.1-bin.zip


The maven artifacts for the release can be found here:
http://people.apache.org/~kevan/release-votes/G-2.1/geronimo-2.1/

or in the following archive (warning, this file is 458 megs):
http://people.apache.org/~kevan/release-votes/G-2.1/geronimo-2.1- 
dist.tar.gz


When the release vote is approved, these maven artifacts will be  
moved to the m2-ibiblio-rsync-repository at Apache.


Due to the discovery of a bug in the Connector component of  
Geronimo TxManager, a new release of TxManager was needed.  
TxManager 2.1.1 is also part of this vote.


The source code for the TxManager 2.1.1 release can be found here:
https://svn.apache.org/repos/asf/geronimo/components/txmanager/tags/ 
geronimo-txmanager-parent-2.1.1


The maven artifacts for TxManager 2.1.1 can be found here:
http://people.apache.org/~kevan/release-votes/G-2.1/geronimo- 
txmanager-2.1.1/


When the release vote is approved, these maven artifacts will be  
moved to the m2-ibiblio-rsync-repository at Apache.


Please review these releases and register your vote.

[ ] +1 Release Geronimo 2.1 and TxManager 2.1.1
[ ] 0 No opinion
[ ] -1 Do not release Geronimo 2.1 and TxManager 2.1.1 (please  
provide rationale)


I'll plan on calling this vote on Wednesday evening (11 PM EST).

--kevan

Re: [VOTE] Geronimo Server 2.1 and Geronimo TxManager 2.1.1 Releases

2008-02-14 Thread Vamsavardhana Reddy

+1

++Vamsi

On Mon, Feb 11, 2008 at 9:16 AM, Kevan Miller <[EMAIL PROTECTED]>
wrote:

> All,
> I've prepared a 2.1 release candidate for your review and vote. I've also
> prepared a 2.1.1 TxManager release candidate for review and vote. For
> simplicity, I'm holding a single vote for both releases. The Geronimo server
> release is dependent upon the TxManager 2.1.1 release.
> The source for the Geronimo 2.1 release currently resides here:
> https://svn.apache.org/repos/asf/geronimo/server/branches/2.1.0
>
> When the release vote is approved, I will svn mv the code to
> https://svn.apache.org/repos/asf/geronimo/server/tags/2.1.0
>
> An archive of this source code can be found here:
>
> http://people.apache.org/~kevan/release-votes/G-2.1/geronimo-2.1-dist/geronimo-2.1-src.tar.gz
>
> http://people.apache.org/~kevan/release-votes/G-2.1/geronimo-2.1-dist/contains
>  the 8 Java EE and Minimal server binary distributions to be
> released (tomcat/jetty, Java EE/Minimal, tar/zip) as well as the
> RELEASE_NOTES and source code archives for the release.
>
> For your convenience, here are pointers to the urls for the distributions
> in zip format:
>
> http://people.apache.org/~kevan/release-votes/G-2.1/geronimo-2.1-dist/geronimo-jetty6-javaee5-2.1-bin.zip
>
> http://people.apache.org/~kevan/release-votes/G-2.1/geronimo-2.1-dist/geronimo-jetty6-minimal-2.1-bin.zip
>
> http://people.apache.org/~kevan/release-votes/G-2.1/geronimo-2.1-dist/geronimo-tomcat6-javaee5-2.1-bin.zip
>
> http://people.apache.org/~kevan/release-votes/G-2.1/geronimo-2.1-dist/geronimo-tomcat6-minimal-2.1-bin.zip
>
> The maven artifacts for the release can be found here:
> http://people.apache.org/~kevan/release-votes/G-2.1/geronimo-2.1/
>
> or in the following archive (warning, this file is 458 megs):
>
> http://people.apache.org/~kevan/release-votes/G-2.1/geronimo-2.1-dist.tar.gz
>
> When the release vote is approved, these maven artifacts will be moved to the 
> m2-ibiblio-rsync-repository
> at Apache.
>
> Due to the discovery of a bug in the Connector component of Geronimo
> TxManager, a new release of TxManager was needed. TxManager 2.1.1 is also
> part of this vote.
>
> The source code for the TxManager 2.1.1 release can be found here:
>
> https://svn.apache.org/repos/asf/geronimo/components/txmanager/tags/geronimo-txmanager-parent-2.1.1
>
> The maven artifacts for TxManager 2.1.1 can be found here:
>
> http://people.apache.org/~kevan/release-votes/G-2.1/geronimo-txmanager-2.1.1/
>
> When the release vote is approved, these maven artifacts will be moved to the 
> m2-ibiblio-rsync-repository
> at Apache.
>
> Please review these releases and register your vote.
>
> [ ] +1 Release Geronimo 2.1 and TxManager 2.1.1
> [ ] 0 No opinion
> [ ] -1 Do not release Geronimo 2.1 and TxManager 2.1.1 (please provide
> rationale)
>
> I'll plan on calling this vote on Wednesday evening (11 PM EST).
>
> --kevan
>

[jira] Updated: (GERONIMO-3851) Plan Creator cannot recognize classes inside compressed JARs of WEB-INF/lib


 [ 
https://issues.apache.org/jira/browse/GERONIMO-3851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Shiva Kumar H R updated GERONIMO-3851:
--

Attachment: jaxws-calculator-war-2.1-SNAPSHOT.war

Test web-app for the failing scenario. Try inputting this WAR to Plan Creator. 
Although this web-app requires references to be resolved, no "WAR-References" 
page will be shown.

> Plan Creator cannot recognize classes inside compressed JARs of WEB-INF/lib
> ---
>
> Key: GERONIMO-3851
> URL: https://issues.apache.org/jira/browse/GERONIMO-3851
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: console
>Affects Versions: 2.1
>Reporter: Shiva Kumar H R
>Assignee: Shiva Kumar H R
> Fix For: 2.1.1
>
> Attachments: jaxws-calculator-war-2.1-SNAPSHOT.war
>
>
> If a servlet class is packaged as a compressed JAR and put in WEB-INF/lib 
> directory of a WAR, then plan creator will fail to recognize such class.
> Due to GERONIMO-3850, you may *not* notice any exceptions on console, rather 
> Plan Creator would have simply failed to detect any references/security 
> configurations required for the web-app. 
> When you input such WARs to Plan Creator, you will see that after "WAR - 
> Environment" page you will directly move to "WAR - Dependencies" page. i.e. 
> *no* "WAR-References" or "WAR-Security" page will be shown even though the 
> web-app requires certain references to be resolved or security roles to be 
> defined.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Created: (GERONIMO-3851) Plan Creator cannot recognize classes inside compressed JARs of WEB-INF/lib

Plan Creator cannot recognize classes inside compressed JARs of WEB-INF/lib
---

 Key: GERONIMO-3851
 URL: https://issues.apache.org/jira/browse/GERONIMO-3851
 Project: Geronimo
  Issue Type: Bug
  Security Level: public (Regular issues)
  Components: console
Affects Versions: 2.1
Reporter: Shiva Kumar H R
Assignee: Shiva Kumar H R
 Fix For: 2.1.1


If a servlet class is packaged as a compressed JAR and put in WEB-INF/lib 
directory of a WAR, then plan creator will fail to recognize such class.

Due to GERONIMO-3850, you may *not* notice any exceptions on console, rather 
Plan Creator would have simply failed to detect any references/security 
configurations required for the web-app. 

When you input such WARs to Plan Creator, you will see that after "WAR - 
Environment" page you will directly move to "WAR - Dependencies" page. i.e. 
*no* "WAR-References" or "WAR-Security" page will be shown even though the 
web-app requires certain references to be resolved or security roles to be 
defined.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: [VOTE] Geronimo Server 2.1 and Geronimo TxManager 2.1.1 Releases

2008-02-14 Thread Rick McGuire


+1

Kevan Miller wrote:

All,
I've prepared a 2.1 release candidate for your review and vote. I've 
also prepared a 2.1.1 TxManager release candidate for review and vote. 
For simplicity, I'm holding a single vote for both releases. The 
Geronimo server release is dependent upon the TxManager 2.1.1 release. 

The source for the Geronimo 2.1 release currently resides here: 
https://svn.apache.org/repos/asf/geronimo/server/branches/2.1.0


When the release vote is approved, I will svn mv the code to 
https://svn.apache.org/repos/asf/geronimo/server/tags/2.1.0


An archive of this source code can be found here:  
http://people.apache.org/~kevan/release-votes/G-2.1/geronimo-2.1-dist/geronimo-2.1-src.tar.gz 

 
http://people.apache.org/~kevan/release-votes/G-2.1/geronimo-2.1-dist/ 
 
contains the 8 Java EE and Minimal server binary distributions to be 
released (tomcat/jetty, Java EE/Minimal, tar/zip) as well as the 
RELEASE_NOTES and source code archives for the release. 

For your convenience, here are pointers to the urls for the 
distributions in zip format:
http://people.apache.org/~kevan/release-votes/G-2.1/geronimo-2.1-dist/geronimo-jetty6-javaee5-2.1-bin.zip 

http://people.apache.org/~kevan/release-votes/G-2.1/geronimo-2.1-dist/geronimo-jetty6-minimal-2.1-bin.zip 

http://people.apache.org/~kevan/release-votes/G-2.1/geronimo-2.1-dist/geronimo-tomcat6-javaee5-2.1-bin.zip 

http://people.apache.org/~kevan/release-votes/G-2.1/geronimo-2.1-dist/geronimo-tomcat6-minimal-2.1-bin.zip 



The maven artifacts for the release can be found here: 
http://people.apache.org/~kevan/release-votes/G-2.1/geronimo-2.1/ 



or in the following archive (warning, this file is 458 megs):
http://people.apache.org/~kevan/release-votes/G-2.1/geronimo-2.1-dist.tar.gz 



When the release vote is approved, these maven artifacts will be moved to the m2-ibiblio-rsync-repository 
at Apache.


Due to the discovery of a bug in the Connector component of Geronimo 
TxManager, a new release of TxManager was needed. TxManager 2.1.1 is 
also part of this vote.


The source code for the TxManager 2.1.1 release can be found here: 
https://svn.apache.org/repos/asf/geronimo/components/txmanager/tags/geronimo-txmanager-parent-2.1.1


The maven artifacts for TxManager 2.1.1 can be found here:
http://people.apache.org/~kevan/release-votes/G-2.1/geronimo-txmanager-2.1.1/ 



When the release vote is approved, these maven artifacts will be moved to the m2-ibiblio-rsync-repository 
at Apache.
 
Please review these releases and register your vote.


[ ] +1 Release Geronimo 2.1 and TxManager 2.1.1
[ ] 0 No opinion
[ ] -1 Do not release Geronimo 2.1 and TxManager 2.1.1 (please provide 
rationale)


I'll plan on calling this vote on Wednesday evening (11 PM EST).

--kevan

[jira] Created: (GERONIMO-3850) Plan Creator suppresses exceptions rather than showing it to user

Plan Creator suppresses exceptions rather than showing it to user
-

 Key: GERONIMO-3850
 URL: https://issues.apache.org/jira/browse/GERONIMO-3850
 Project: Geronimo
  Issue Type: Bug
  Security Level: public (Regular issues)
  Components: console
Affects Versions: 2.1
Reporter: Shiva Kumar H R
Assignee: Shiva Kumar H R
 Fix For: 2.1.1


Various exceptions could be encountered during plan creation phase. Rather than 
showing it to user via Admin Console page, plan creator is currently 
suppressing them.

Location to be fixed:
org.apache.geronimo.console.configcreator.JSR88_Util.parseWarReferences() 
function of "plancreator-portlets" module.
try {
classFinder = 
AbstractWebModuleBuilder.createWebAppClassFinder(webApp, classLoader);
} catch (DeploymentException e2) {
return;
}

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: [VOTE] Geronimo Server 2.1 and Geronimo TxManager 2.1.1 Releases

2008-02-14 Thread Gianny Damour


+1

Thanks,
Gianny

On 14/02/2008, at 2:12 PM, Matt Hogstrom wrote:


+1

I tested the Tomcat JEE version and was able to deploy DayTrader  
2.0 and run through all scenarios.


pgp signatures verified ok

gpg: Signature made Sun Feb 10 15:21:19 2008 EST using DSA key ID  
86859358

gpg: Good signature from "Kevan Miller <[EMAIL PROTECTED]>"

Other items in NOTICES and such look good too.


On Feb 10, 2008, at 10:46 PM, Kevan Miller wrote:


All,
I've prepared a 2.1 release candidate for your review and vote.  
I've also prepared a 2.1.1 TxManager release candidate for review  
and vote. For simplicity, I'm holding a single vote for both  
releases. The Geronimo server release is dependent upon the  
TxManager 2.1.1 release.


The source for the Geronimo 2.1 release currently resides here:
https://svn.apache.org/repos/asf/geronimo/server/branches/2.1.0

When the release vote is approved, I will svn mv the code to
https://svn.apache.org/repos/asf/geronimo/server/tags/2.1.0

An archive of this source code can be found here:
http://people.apache.org/~kevan/release-votes/G-2.1/geronimo-2.1- 
dist/geronimo-2.1-src.tar.gz


http://people.apache.org/~kevan/release-votes/G-2.1/geronimo-2.1- 
dist/ contains the 8 Java EE and Minimal server binary  
distributions to be released (tomcat/jetty, Java EE/Minimal, tar/ 
zip) as well as the RELEASE_NOTES and source code archives for the  
release.


For your convenience, here are pointers to the urls for the  
distributions in zip format:
http://people.apache.org/~kevan/release-votes/G-2.1/geronimo-2.1- 
dist/geronimo-jetty6-javaee5-2.1-bin.zip
http://people.apache.org/~kevan/release-votes/G-2.1/geronimo-2.1- 
dist/geronimo-jetty6-minimal-2.1-bin.zip
http://people.apache.org/~kevan/release-votes/G-2.1/geronimo-2.1- 
dist/geronimo-tomcat6-javaee5-2.1-bin.zip
http://people.apache.org/~kevan/release-votes/G-2.1/geronimo-2.1- 
dist/geronimo-tomcat6-minimal-2.1-bin.zip


The maven artifacts for the release can be found here:
http://people.apache.org/~kevan/release-votes/G-2.1/geronimo-2.1/

or in the following archive (warning, this file is 458 megs):
http://people.apache.org/~kevan/release-votes/G-2.1/geronimo-2.1- 
dist.tar.gz


When the release vote is approved, these maven artifacts will be  
moved to the m2-ibiblio-rsync-repository at Apache.


Due to the discovery of a bug in the Connector component of  
Geronimo TxManager, a new release of TxManager was needed.  
TxManager 2.1.1 is also part of this vote.


The source code for the TxManager 2.1.1 release can be found here:
https://svn.apache.org/repos/asf/geronimo/components/txmanager/ 
tags/geronimo-txmanager-parent-2.1.1


The maven artifacts for TxManager 2.1.1 can be found here:
http://people.apache.org/~kevan/release-votes/G-2.1/geronimo- 
txmanager-2.1.1/


When the release vote is approved, these maven artifacts will be  
moved to the m2-ibiblio-rsync-repository at Apache.


Please review these releases and register your vote.

[ ] +1 Release Geronimo 2.1 and TxManager 2.1.1
[ ] 0 No opinion
[ ] -1 Do not release Geronimo 2.1 and TxManager 2.1.1 (please  
provide rationale)


I'll plan on calling this vote on Wednesday evening (11 PM EST).

--kevan

[BUILD] 2.2: Failed for Revision: 627677

2008-02-14 Thread gawor

Geronimo Revision: 627677 built with tests included
 
See the full build-0300.log file at 
http://geronimo.apache.org/maven/server/binaries/trunk/20080214/build-0300.log
 
Download the binaries from 
http://geronimo.apache.org/maven/server/binaries/trunk/20080214
[INFO] BUILD SUCCESSFUL
[INFO] 
[INFO] Total time: 29 minutes 34 seconds
[INFO] Finished at: Thu Feb 14 03:40:16 EST 2008
[INFO] Final Memory: 307M/621M
[INFO] 
 
TESTSUITE RESULTS (Failures only)
=
See detailed results at 
http://geronimo.apache.org/maven/server/testsuite/ResultsSummary.html
 
Assembly: tomcat
=
See the full test.log file at 
http://geronimo.apache.org/maven/server/binaries/trunk/20080214/logs-0300-tomcat/test.log
 
 
Assembly: jetty
=
See the full test.log file at 
http://geronimo.apache.org/maven/server/binaries/trunk/20080214/logs-0300-jetty/test.log
 
[INFO] Running console-testsuite.advance-test
[INFO] Tests run: 13, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 75.278 
sec <<< FAILURE!

deploy/assemble and ERROR GroovyRuntimeException: Ambiguous method overloading for method org.apache.geronimo.kernel.repository.Artifact#