[BUILD] branches/2.1: Failed for Revision: 990319

2010-08-27 Thread gawor
Geronimo Revision: 990319 built with tests included
 
See the full build-0200.log file at 
http://people.apache.org/builds/geronimo/server/binaries/2.1/20100828/build-0200.log
 
 
See the unit test reports at 
http://people.apache.org/builds/geronimo/server/binaries/2.1/20100828/unit-test-reports
 


this realm = plexus.core
urls[0] = file:/usr/local/maven/lib/maven-2.0.9-uber.jar
Number of imports: 6
import: org.codehaus.classworlds.en...@4891bb28
import: org.codehaus.classworlds.en...@f8e44ca4
import: org.codehaus.classworlds.en...@c51bc9e7
import: org.codehaus.classworlds.en...@bece5185
import: org.codehaus.classworlds.en...@3fee8e37
import: org.codehaus.classworlds.en...@3fee19d8
-
[INFO] 
[ERROR] BUILD ERROR
[INFO] 
[INFO] Internal error in the plugin manager executing goal 
'org.codehaus.mojo.jspc:jspc-maven-plugin:2.0-alpha-2:compile': Unable to find 
the mojo 'org.codehaus.mojo.jspc:jspc-maven-plugin:2.0-alpha-2:compile' in the 
plugin 'org.codehaus.mojo.jspc:jspc-maven-plugin'
Lorg/codehaus/mojo/jspc/compiler/JspCompiler;
[INFO] 
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Internal error in the 
plugin manager executing goal 
'org.codehaus.mojo.jspc:jspc-maven-plugin:2.0-alpha-2:compile': Unable to find 
the mojo 'org.codehaus.mojo.jspc:jspc-maven-plugin:2.0-alpha-2:compile' in the 
plugin 'org.codehaus.mojo.jspc:jspc-maven-plugin'
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:562)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.plugin.PluginManagerException: Unable to find the 
mojo 'org.codehaus.mojo.jspc:jspc-maven-plugin:2.0-alpha-2:compile' in the 
plugin 'org.codehaus.mojo.jspc:jspc-maven-plugin'
at 
org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPluginManager.java:618)
at 
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:429)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
... 16 more
Caused by: 
org.codehaus.plexus.component.repository.exception.ComponentLookupException: 
Unable to lookup component 
'org.apache.maven.plugin.Mojoorg.codehaus.mojo.jspc:jspc-maven-plugin:2.0-alpha-2:compile',
 it could not be created
at 
org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:335)
at 
org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:440)
at 
org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPluginManager.java:609)
... 18 more
Caused by: 
org.codehaus.plexus.component.factory.ComponentInstantiationException: Could 
not instanciate component: role: 'null', implementation: 
'org.codehaus.mojo.jspc.CompileMojo'
at 
org.codehaus.plexus.component.factory.java.JavaComponentFactory.makeException(JavaComponentFactory.java:77)
at 
org.codehaus.plexus.component.factory.java.JavaComponentFactory.newInstance(JavaComponentFactory.java:62)
at 
org.codehaus.plexus.DefaultPlexusContainer.createComponentInstance(DefaultPlexusContainer.java:1464)
at 
org.codehaus.plexus.component.manager.AbstractComponentManager.createComponentInstance(AbstractComponentManager.java:93)
at 
org.codehaus.plexus.component.manager

[BUILD] trunk: Failed for Revision: 990310

2010-08-27 Thread gawor
Geronimo Revision: 990310 built with tests included
 
See the full build-2100.log file at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100827/build-2100.log
 
Download the binaries from 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100827
[INFO] BUILD SUCCESSFUL
[INFO] 
[INFO] Total time: 42 minutes 50 seconds
[INFO] Finished at: Fri Aug 27 21:47:30 EDT 2010
[INFO] Final Memory: 512M/987M
[INFO] 
 
TESTSUITE RESULTS (Failures only)
=
 
Assembly: tomcat
=
See full test results and logs at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100827/logs-2100-tomcat/
 
Running TestSuite
Tests run: 3, Failures: 3, Errors: 0, Skipped: 0, Time elapsed: 11.238 sec <<< 
FAILURE!
 
Assembly: jetty
=
See full test results and logs at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100827/logs-2100-jetty/
 
Running TestSuite
Tests run: 3, Failures: 3, Errors: 0, Skipped: 0, Time elapsed: 10.825 sec <<< 
FAILURE!
Running TestSuite
Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 5.252 sec <<< 
FAILURE!
 
Samples: trunk
=
Log: 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100827/samples-2100.log
 
Build status: OK
 


[BUILD] branches/2.2: Failed for Revision: 990302

2010-08-27 Thread gawor
Geronimo Revision: 990302 built with tests included
 
See the full build-2000.log file at 
http://people.apache.org/builds/geronimo/server/binaries/2.2/20100827/build-2000.log
 
 
See the unit test reports at 
http://people.apache.org/builds/geronimo/server/binaries/2.2/20100827/unit-test-reports
 
import: org.codehaus.classworlds.en...@f8e44ca4
import: org.codehaus.classworlds.en...@92758522
import: org.codehaus.classworlds.en...@ebf2705b
import: org.codehaus.classworlds.en...@bb25e54
import: org.codehaus.classworlds.en...@bece5185
import: org.codehaus.classworlds.en...@3fee8e37
import: org.codehaus.classworlds.en...@3fee19d8
-
[INFO] 
[ERROR] BUILD ERROR
[INFO] 
[INFO] Internal error in the plugin manager executing goal 
'org.codehaus.mojo.jspc:jspc-maven-plugin:2.0-alpha-2:compile': Unable to find 
the mojo 'org.codehaus.mojo.jspc:jspc-maven-plugin:2.0-alpha-2:compile' in the 
plugin 'org.codehaus.mojo.jspc:jspc-maven-plugin'
org.codehaus.mojo.jspc.compiler.JspCompiler
[INFO] 
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Internal error in the 
plugin manager executing goal 
'org.codehaus.mojo.jspc:jspc-maven-plugin:2.0-alpha-2:compile': Unable to find 
the mojo 'org.codehaus.mojo.jspc:jspc-maven-plugin:2.0-alpha-2:compile' in the 
plugin 'org.codehaus.mojo.jspc:jspc-maven-plugin'
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:563)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:500)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:479)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:331)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:292)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:301)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:618)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.plugin.PluginManagerException: Unable to find the 
mojo 'org.codehaus.mojo.jspc:jspc-maven-plugin:2.0-alpha-2:compile' in the 
plugin 'org.codehaus.mojo.jspc:jspc-maven-plugin'
at 
org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPluginManager.java:620)
at 
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:431)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:559)
... 16 more
Caused by: 
org.codehaus.plexus.component.repository.exception.ComponentLookupException: 
Unable to lookup component 
'org.apache.maven.plugin.Mojoorg.codehaus.mojo.jspc:jspc-maven-plugin:2.0-alpha-2:compile',
 it could not be created
at 
org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:335)
at 
org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:440)
at 
org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPluginManager.java:611)
... 18 more
Caused by: 
org.codehaus.plexus.component.factory.ComponentInstantiationException: Could 
not instanciate component: role: 'null', implementation: 
'org.codehaus.mojo.jspc.CompileMojo'
at 
org.codehaus.plexus.component.factory.java.JavaComponentFactory.makeException(JavaComponentFactory.java:77)
at 
org.codehaus.plexus.component.factory.java.JavaComponentFactory.newInstance(JavaComponentFactory.java:62)
at 
org.codehaus.plexus.DefaultPlexusContainer.createComponentInstance(DefaultPlexusContainer.java:1464)
at 
org.codehaus.plexus.component.manager.AbstractComponentManager.createComponentInstance(AbstractComp

[BUILD] trunk: Failed for Revision: 990229

2010-08-27 Thread gawor
Geronimo Revision: 990229 built with tests included
 
See the full build-1500.log file at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100827/build-1500.log
 
Download the binaries from 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100827
[INFO] BUILD SUCCESSFUL
[INFO] 
[INFO] Total time: 38 minutes 33 seconds
[INFO] Finished at: Fri Aug 27 15:43:50 EDT 2010
[INFO] Final Memory: 486M/992M
[INFO] 
 
TESTSUITE RESULTS (Failures only)
=
 
Assembly: tomcat
=
See full test results and logs at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100827/logs-1500-tomcat/
 
Running TestSuite
Tests run: 3, Failures: 3, Errors: 0, Skipped: 0, Time elapsed: 10.926 sec <<< 
FAILURE!
 
Assembly: jetty
=
See full test results and logs at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100827/logs-1500-jetty/
 
Running TestSuite
Tests run: 3, Failures: 3, Errors: 0, Skipped: 0, Time elapsed: 10.964 sec <<< 
FAILURE!
Running TestSuite
Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 5.269 sec <<< 
FAILURE!
 
[org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connecting to: 
service:jmx:rmi://localhost/jndi/rmi://localhost:1099/JMXConnector
[org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connection failure; 
ignoring: java.io.IOException: Failed to retrieve RMIServer stub: 
javax.naming.ServiceUnavailableException [Root exception is 
java.rmi.ConnectException: Connection refused to host: localhost; nested 
exception is: 
java.net.ConnectException: Connection refused]
[org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connecting to: 
service:jmx:rmi://localhost/jndi/rmi://localhost:1099/JMXConnector
[org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connection failure; 
ignoring: java.io.IOException: Failed to retrieve RMIServer stub: 
javax.naming.ServiceUnavailableException [Root exception is 
java.rmi.ConnectException: Connection refused to host: localhost; nested 
exception is: 
java.net.ConnectException: Connection refused]
[org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connecting to: 
service:jmx:rmi://localhost/jndi/rmi://localhost:1099/JMXConnector
[org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connection failure; 
ignoring: java.io.IOException: Failed to retrieve RMIServer stub: 
javax.naming.ServiceUnavailableException [Root exception is 
java.rmi.ConnectException: Connection refused to host: localhost; nested 
exception is: 
java.net.ConnectException: Connection refused]
[org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connecting to: 
service:jmx:rmi://localhost/jndi/rmi://localhost:1099/JMXConnector
[org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connection failure; 
ignoring: java.io.IOException: Failed to retrieve RMIServer stub: 
javax.naming.ServiceUnavailableException [Root exception is 
java.rmi.ConnectException: Connection refused to host: localhost; nested 
exception is: 
java.net.ConnectException: Connection refused]
[org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connecting to: 
service:jmx:rmi://localhost/jndi/rmi://localhost:1099/JMXConnector
[org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connection failure; 
ignoring: java.io.IOException: Failed to retrieve RMIServer stub: 
javax.naming.ServiceUnavailableException [Root exception is 
java.rmi.ConnectException: Connection refused to host: localhost; nested 
exception is: 
java.net.ConnectException: Connection refused]
[org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connecting to: 
service:jmx:rmi://localhost/jndi/rmi://localhost:1099/JMXConnector
[org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connection failure; 
ignoring: java.io.IOException: Failed to retrieve RMIServer stub: 
javax.naming.ServiceUnavailableException [Root exception is 
java.rmi.ConnectException: Connection refused to host: localhost; nested 
exception is: 
java.net.ConnectException: Connection refused]
[org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connecting to: 
service:jmx:rmi://localhost/jndi/rmi://localhost:1099/JMXConnector
[org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connection failure; 
ignoring: java.io.IOException: Failed to retrieve RMIServer stub: 
javax.naming.ServiceUnavailableException [Root exception is 
java.rmi.ConnectException: Connection refused to host: localhost; nested 
exception is: 
java.net.ConnectException: Connection refused]
[org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connecting to: 
service:jmx:rmi://localhost/jndi/rmi://localhost:1099/JMXConnector
[org.apache.geronimo.mavenplugins.geronimo.Server

[jira] Commented: (GERONIMO-5553) Fail to enchance entities on Geronimo

2010-08-27 Thread Donald Woods (JIRA)

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

Donald Woods commented on GERONIMO-5553:


Thanks Lin.  I missed that.
But, this was unexpected behavior for OpenJPA due to Geronimo using the 
javaagent, which only enhances the classes listed in the persistence.xml 
whereas the dynamic enhancer will find other classes to enhance unless 
 is specified.  If no classes are specified, then all 
of the classes will get enhanced whether the dynamic or javaagent methods are 
used.  So, we have a difference in enhancement behavior here


> Fail to enchance entities on Geronimo
> -
>
> Key: GERONIMO-5553
> URL: https://issues.apache.org/jira/browse/GERONIMO-5553
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: persistence
>Affects Versions: 3.0
> Environment: OS:win xp
> Geronimo :3.0 20100824 build
>Reporter: Lu Jiang
>Assignee: Rick McGuire
> Fix For: 3.0
>
> Attachments: booknew.war
>
>
> I tried to deploy a simple jpa sample on geronimo.But when persist data into 
> database.
> Following exception will occur.
>  
> org.apache.openjpa.persistence.ArgumentException: Attempt to cast instance 
> "org.apache.sample.entities.b...@97781f" to PersistenceCapable failed.  
> Ensure that it has been enhanced.
> FailedObject: org.apache.sample.entities.b...@97781f

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



[jira] Commented: (GERONIMO-5553) Fail to enchance entities on Geronimo

2010-08-27 Thread Lin Sun (JIRA)

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

Lin Sun commented on GERONIMO-5553:
---

Hi

After some initial investigate, it turned out to be a user error in 
persistence.xml.   The class should be:

 org.apache.sample.entities.Book

while the one in the attached war has it configured as 
org.apache.geronimo.sample.entities.Book

This is causing the entity enhancement error as it was tried to enhance the 
wrong class.

After I made the above change, I am not seeing the entity didn't enhance error. 
 

P.S. This user case (a PU in war file) has to be a war file.  If it is a WAB, 
it won't work, as the aries JPA doesn't support PU in WAB.

Please advise if this answer is satisfactory.  If so, you may close the bug.

Thanks

Lin

> Fail to enchance entities on Geronimo
> -
>
> Key: GERONIMO-5553
> URL: https://issues.apache.org/jira/browse/GERONIMO-5553
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: persistence
>Affects Versions: 3.0
> Environment: OS:win xp
> Geronimo :3.0 20100824 build
>Reporter: Lu Jiang
>Assignee: Rick McGuire
> Fix For: 3.0
>
> Attachments: booknew.war
>
>
> I tried to deploy a simple jpa sample on geronimo.But when persist data into 
> database.
> Following exception will occur.
>  
> org.apache.openjpa.persistence.ArgumentException: Attempt to cast instance 
> "org.apache.sample.entities.b...@97781f" to PersistenceCapable failed.  
> Ensure that it has been enhanced.
> FailedObject: org.apache.sample.entities.b...@97781f

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



[BUILD] branches/2.2: Failed for Revision: 990214

2010-08-27 Thread gawor
Geronimo Revision: 990214 built with tests included
 
See the full build-1400.log file at 
http://people.apache.org/builds/geronimo/server/binaries/2.2/20100827/build-1400.log
 
 
See the unit test reports at 
http://people.apache.org/builds/geronimo/server/binaries/2.2/20100827/unit-test-reports
 
Number of imports: 10
import: org.codehaus.classworlds.en...@a6c57a42
import: org.codehaus.classworlds.en...@12f43f3b
import: org.codehaus.classworlds.en...@20025374
import: org.codehaus.classworlds.en...@f8e44ca4
import: org.codehaus.classworlds.en...@92758522
import: org.codehaus.classworlds.en...@ebf2705b
import: org.codehaus.classworlds.en...@bb25e54
import: org.codehaus.classworlds.en...@bece5185
import: org.codehaus.classworlds.en...@3fee8e37
import: org.codehaus.classworlds.en...@3fee19d8
-
[INFO] 
[ERROR] BUILD ERROR
[INFO] 
[INFO] Internal error in the plugin manager executing goal 
'org.codehaus.mojo.jspc:jspc-maven-plugin:2.0-alpha-2:compile': Unable to find 
the mojo 'org.codehaus.mojo.jspc:jspc-maven-plugin:2.0-alpha-2:compile' in the 
plugin 'org.codehaus.mojo.jspc:jspc-maven-plugin'
Lorg/codehaus/mojo/jspc/compiler/JspCompiler;
[INFO] 
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Internal error in the 
plugin manager executing goal 
'org.codehaus.mojo.jspc:jspc-maven-plugin:2.0-alpha-2:compile': Unable to find 
the mojo 'org.codehaus.mojo.jspc:jspc-maven-plugin:2.0-alpha-2:compile' in the 
plugin 'org.codehaus.mojo.jspc:jspc-maven-plugin'
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:563)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:500)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:479)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:331)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:292)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:301)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.plugin.PluginManagerException: Unable to find the 
mojo 'org.codehaus.mojo.jspc:jspc-maven-plugin:2.0-alpha-2:compile' in the 
plugin 'org.codehaus.mojo.jspc:jspc-maven-plugin'
at 
org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPluginManager.java:620)
at 
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:431)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:559)
... 16 more
Caused by: 
org.codehaus.plexus.component.repository.exception.ComponentLookupException: 
Unable to lookup component 
'org.apache.maven.plugin.Mojoorg.codehaus.mojo.jspc:jspc-maven-plugin:2.0-alpha-2:compile',
 it could not be created
at 
org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:335)
at 
org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:440)
at 
org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPluginManager.java:611)
... 18 more
Caused by: 
org.codehaus.plexus.component.factory.ComponentInstantiationException: Could 
not instanciate component: role: 'null', implementation: 
'org.codehaus.mojo.jspc.CompileMojo'
at 
org.codehaus.plexus.component.factory.java.JavaComponentFactory.makeException(JavaComponentFactory.java:77)
at 
org.codehaus.plexus.component.factory.java.JavaComponentFactory.newInstance(JavaComponentFactory.java:62)
at 
o

[BUILD] trunk: Failed for Revision: 990137

2010-08-27 Thread gawor
Geronimo Revision: 990137 built with tests included
 
See the full build-0900.log file at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100827/build-0900.log
 
Download the binaries from 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100827
[INFO] BUILD SUCCESSFUL
[INFO] 
[INFO] Total time: 40 minutes 42 seconds
[INFO] Finished at: Fri Aug 27 09:46:02 EDT 2010
[INFO] Final Memory: 453M/1013M
[INFO] 
 
TESTSUITE RESULTS (Failures only)
=
 
Assembly: tomcat
=
See full test results and logs at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100827/logs-0900-tomcat/
 
Running TestSuite
Tests run: 3, Failures: 3, Errors: 0, Skipped: 0, Time elapsed: 10.882 sec <<< 
FAILURE!
 
Assembly: jetty
=
See full test results and logs at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100827/logs-0900-jetty/
 
Running TestSuite
Tests run: 3, Failures: 3, Errors: 0, Skipped: 0, Time elapsed: 10.973 sec <<< 
FAILURE!
Running TestSuite
Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 5.007 sec <<< 
FAILURE!
 
Samples: trunk
=
Log: 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100827/samples-0900.log
 
Build status: OK
 


[jira] Commented: (GERONIMO-5553) Fail to enchance entities on Geronimo

2010-08-27 Thread Jarek Gawor (JIRA)

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

Jarek Gawor commented on GERONIMO-5553:
---

Once again, the Aries JPA is not used in this case. So no need to worry about 
it. But if you are interested, this works in exactly the same way as it works 
for regular Java EE apps. OpenJPA calls PersistenceUntInfo.addTransfomer() 
which then registers the transformer with the agent which later on causes the 
enhancement to be done. 

Everything is a bundle in Geronimo 3.0. I'm pretty sure the PU provides the 
classloader it wants to use via PersistenceUnitInfo.getClassLoader().


> Fail to enchance entities on Geronimo
> -
>
> Key: GERONIMO-5553
> URL: https://issues.apache.org/jira/browse/GERONIMO-5553
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: persistence
>Affects Versions: 3.0
> Environment: OS:win xp
> Geronimo :3.0 20100824 build
>Reporter: Lu Jiang
>Assignee: Rick McGuire
> Fix For: 3.0
>
> Attachments: booknew.war
>
>
> I tried to deploy a simple jpa sample on geronimo.But when persist data into 
> database.
> Following exception will occur.
>  
> org.apache.openjpa.persistence.ArgumentException: Attempt to cast instance 
> "org.apache.sample.entities.b...@97781f" to PersistenceCapable failed.  
> Ensure that it has been enhanced.
> FailedObject: org.apache.sample.entities.b...@97781f

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



[jira] Commented: (GERONIMO-5553) Fail to enchance entities on Geronimo

2010-08-27 Thread Donald Woods (JIRA)

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

Donald Woods commented on GERONIMO-5553:


OK, so this dual personality is really confusing...  Looking back at ARIES-320, 
you added and them removed code to enable the javaagent support and instead in 
geronimo-aries-jpa created "GeronimoManagedPersistenceUnitInfoFactory extends 
ManagedPersistenceUnitInfoFactoryImpl".  How did this enable the javaagent for 
Aries apps???

Guess I'm wondering, if the app is being loaded as a bundle, is OpenJPA being 
loaded as a bundle?  We have tons of places in OpenJPA where we're looking up 
classloaders, but only one place (broker factory creation) that we try to use 
the bundle context if available (which was OPENJPA-1491 for Aries.)  So, if the 
OpenJPA transformer uses the bundle context, what is the runtime using and are 
we seeing two copies of the class, one enhanced and one not?


> Fail to enchance entities on Geronimo
> -
>
> Key: GERONIMO-5553
> URL: https://issues.apache.org/jira/browse/GERONIMO-5553
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: persistence
>Affects Versions: 3.0
> Environment: OS:win xp
> Geronimo :3.0 20100824 build
>Reporter: Lu Jiang
>Assignee: Rick McGuire
> Fix For: 3.0
>
> Attachments: booknew.war
>
>
> I tried to deploy a simple jpa sample on geronimo.But when persist data into 
> database.
> Following exception will occur.
>  
> org.apache.openjpa.persistence.ArgumentException: Attempt to cast instance 
> "org.apache.sample.entities.b...@97781f" to PersistenceCapable failed.  
> Ensure that it has been enhanced.
> FailedObject: org.apache.sample.entities.b...@97781f

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



[jira] Commented: (GERONIMO-5469) Add EJB cluster testsuite

2010-08-27 Thread Shawn Jiang (JIRA)

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

Shawn Jiang commented on GERONIMO-5469:
---

Patch committed to  22bra...@r990156.   Thanks Viola for the patch !

> Add EJB cluster testsuite
> -
>
> Key: GERONIMO-5469
> URL: https://issues.apache.org/jira/browse/GERONIMO-5469
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: testsuite
>Affects Versions: 2.2.2
>Reporter: viola.lu
>Assignee: viola.lu
>Priority: Minor
> Fix For: 2.2.2
>
> Attachments: G5469.patch, G5469.patch
>
>
> 1.Create two servers with maven ant plugin which will copy servers from 
> geornimo tomcat javaee assemly and overridde config-subsitution.properties to 
> each server
> 2.Start two server instances , deploy loadbean to two servers, run ejb client 
> against two: failover:ejbd://127.0.0.1:4202,ejbd://127.0.0.1:4211"
> 3.Stop one server and run ejb client again. It still work, just on warning: 
> one server down. 

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



[jira] Commented: (GERONIMO-5553) Fail to enchance entities on Geronimo

2010-08-27 Thread Jarek Gawor (JIRA)

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

Jarek Gawor commented on GERONIMO-5553:
---

First, let me correct something. Aries JPA kicks in when a bundle with 
Meta-Persistence header is deployed. So it's not really about application being 
deployed as a wab. Either way, however, Aries JPA will not be used when 
deploying a regular Java EE web application.

Second, everything is turned into a bundle during deployment so even a war 
module should have a classloader that implements the BundleReference interface. 
But this is probably good place to put a break point to see if transform() is 
being called.

Third, I know that JPA runtime enhancement is working fine in Geronimo for 
Aries applications at least because the testsuites/aries-testsuites/jpa tests 
are passing.


> Fail to enchance entities on Geronimo
> -
>
> Key: GERONIMO-5553
> URL: https://issues.apache.org/jira/browse/GERONIMO-5553
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: persistence
>Affects Versions: 3.0
> Environment: OS:win xp
> Geronimo :3.0 20100824 build
>Reporter: Lu Jiang
>Assignee: Rick McGuire
> Fix For: 3.0
>
> Attachments: booknew.war
>
>
> I tried to deploy a simple jpa sample on geronimo.But when persist data into 
> database.
> Following exception will occur.
>  
> org.apache.openjpa.persistence.ArgumentException: Attempt to cast instance 
> "org.apache.sample.entities.b...@97781f" to PersistenceCapable failed.  
> Ensure that it has been enhanced.
> FailedObject: org.apache.sample.entities.b...@97781f

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



[jira] Commented: (GERONIMO-5553) Fail to enchance entities on Geronimo

2010-08-27 Thread Donald Woods (JIRA)

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

Donald Woods commented on GERONIMO-5553:


In geronimo-transformer, the TransformerWrapper class is commented out and no 
longer used, but geronimo-persistence-jpa20 and geronimo-aries-jpa contains its 
own implementation of TransformerWrapper, which only calls the transformer if 
the provided classloader is an instance of BundleReference?  Is that the right 
behavior for geronimo-persistence-jpa20 for a WAR case, where it is not a 
Bundle? Seems okay for the Aries case...

public byte[] transform(ClassLoader loader, String className, Class 
classBeingRedefined, ProtectionDomain protectionDomain, byte[] classfileBuffer) 
throws IllegalClassFormatException {
if (loader instanceof BundleReference && ((BundleReference) 
loader).getBundle() == bundle) {
try {
return classTransformer.transform(loader, className, 
classBeingRedefined, protectionDomain, classfileBuffer);
} catch (IllegalClassFormatException e) {
throw e;
} catch (RuntimeException e) {
return null;
}
}
return null;
}


> Fail to enchance entities on Geronimo
> -
>
> Key: GERONIMO-5553
> URL: https://issues.apache.org/jira/browse/GERONIMO-5553
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: persistence
>Affects Versions: 3.0
> Environment: OS:win xp
> Geronimo :3.0 20100824 build
>Reporter: Lu Jiang
>Assignee: Rick McGuire
> Fix For: 3.0
>
> Attachments: booknew.war
>
>
> I tried to deploy a simple jpa sample on geronimo.But when persist data into 
> database.
> Following exception will occur.
>  
> org.apache.openjpa.persistence.ArgumentException: Attempt to cast instance 
> "org.apache.sample.entities.b...@97781f" to PersistenceCapable failed.  
> Ensure that it has been enhanced.
> FailedObject: org.apache.sample.entities.b...@97781f

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



[jira] Commented: (GERONIMO-5553) Fail to enchance entities on Geronimo

2010-08-27 Thread Donald Woods (JIRA)

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

Donald Woods commented on GERONIMO-5553:


I checked with Jeremy on the OpenJPA team yesterday and he agreed that the 
openjpa.RuntimeUnenhancedClasses property is ignored for the javaagent code and 
only used for dynamic runtime enhancement (subclassing), so setting that value 
in the EMF Map should not be required and is discouraged, as we tell OpenJPA 
users all the time NOT to use dynamic runtime enhancement.

For the javaagent, classLoadEnhancement=true is the default, which controls 
whether OpenJPA load-time class enhancement should be available in this JVM 
execution.

Starting in OpenJPA 2.0 - If a javaagent is not provided via the command line 
and OpenJPA is running on the Sun 1.6 SDK or IBM 1.6 JDK (SR8+), OpenJPA will 
attempt to dynamically load the runtime Enhancer. This support is provided as 
an ease of use feature and it is not recommended for use in a production 
system.  Setting the property openjpa.DynamicEnhancementAgent to false will 
disable this function.

When then dynamic enhancer is loaded, the following informational message is 
logged:
[java] jpa.enhancement  INFO   [main] openjpa.Runtime - OpenJPA dynamically 
loaded the class enhancer. Any classes that were not enhanced at build time 
will be enhanced when they are loaded by the JVM.

So, is another module (like a deployer, annotation scanner or Tomcat) possibly 
loading the classes before the OpenJPA GBean is being loaded and having a 
chance to register the TransformerAgent?


> Fail to enchance entities on Geronimo
> -
>
> Key: GERONIMO-5553
> URL: https://issues.apache.org/jira/browse/GERONIMO-5553
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: persistence
>Affects Versions: 3.0
> Environment: OS:win xp
> Geronimo :3.0 20100824 build
>Reporter: Lu Jiang
>Assignee: Rick McGuire
> Fix For: 3.0
>
> Attachments: booknew.war
>
>
> I tried to deploy a simple jpa sample on geronimo.But when persist data into 
> database.
> Following exception will occur.
>  
> org.apache.openjpa.persistence.ArgumentException: Attempt to cast instance 
> "org.apache.sample.entities.b...@97781f" to PersistenceCapable failed.  
> Ensure that it has been enhanced.
> FailedObject: org.apache.sample.entities.b...@97781f

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



[jira] Commented: (GERONIMO-5553) Fail to enchance entities on Geronimo

2010-08-27 Thread Rick McGuire (JIRA)

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

Rick McGuire commented on GERONIMO-5553:


Could the solution to this be as simple as adding 
openjpa.RuntimeUnenhancedClasses supported to the property bundle we use when 
calling createContainerEntityManagerFactory()?  A cursory look at the openjpa 
code seems to suggest this is supported both in property and xml form. 

> Fail to enchance entities on Geronimo
> -
>
> Key: GERONIMO-5553
> URL: https://issues.apache.org/jira/browse/GERONIMO-5553
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: persistence
>Affects Versions: 3.0
> Environment: OS:win xp
> Geronimo :3.0 20100824 build
>Reporter: Lu Jiang
>Assignee: Rick McGuire
> Fix For: 3.0
>
> Attachments: booknew.war
>
>
> I tried to deploy a simple jpa sample on geronimo.But when persist data into 
> database.
> Following exception will occur.
>  
> org.apache.openjpa.persistence.ArgumentException: Attempt to cast instance 
> "org.apache.sample.entities.b...@97781f" to PersistenceCapable failed.  
> Ensure that it has been enhanced.
> FailedObject: org.apache.sample.entities.b...@97781f

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



[BUILD] branches/2.2: Failed for Revision: 989978

2010-08-27 Thread gawor
Geronimo Revision: 989978 built with tests included
 
See the full build-2000.log file at 
http://people.apache.org/builds/geronimo/server/binaries/2.2/20100826/build-2000.log
 
Download the binaries from 
http://people.apache.org/builds/geronimo/server/binaries/2.2/20100826
[INFO] BUILD SUCCESSFUL
[INFO] 
[INFO] Total time: 37 minutes 31 seconds
[INFO] Finished at: Thu Aug 26 20:43:09 EDT 2010
[INFO] Final Memory: 326M/913M
[INFO] 
 
TESTSUITE RESULTS (Failures only)
=
 
Assembly: tomcat
=
See full test results and logs at 
http://people.apache.org/builds/geronimo/server/binaries/2.2/20100826/logs-2000-tomcat/
 
[INFO] Running TestSuite
[INFO] Tests run: 40, Failures: 35, Errors: 0, Skipped: 0, Time elapsed: 
165.984 sec <<< FAILURE!
[INFO] Running TestSuite
[INFO] Tests run: 12, Failures: 7, Errors: 0, Skipped: 0, Time elapsed: 63.588 
sec <<< FAILURE!
--
[INFO] Running TestSuite
[INFO] Tests run: 36, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 69.333 
sec <<< FAILURE!
 
Assembly: jetty
=
See full test results and logs at 
http://people.apache.org/builds/geronimo/server/binaries/2.2/20100826/logs-2000-jetty/
 
[INFO] Running TestSuite
[INFO] Tests run: 40, Failures: 23, Errors: 0, Skipped: 0, Time elapsed: 
213.102 sec <<< FAILURE!
[INFO] Running TestSuite
[INFO] Tests run: 12, Failures: 10, Errors: 0, Skipped: 0, Time elapsed: 65.975 
sec <<< FAILURE!
 
[INFO] [INFO] Starting Xvfb...
[INFO] [INFO] Using display: :20
[INFO] [INFO] Using Xauthority file: /tmp/Xvfb1414528678591882973.Xauthority
[INFO] Deleting: /tmp/Xvfb1414528678591882973.Xauthority
[INFO] /usr/X11R6/bin/xauth:  creating new authority file 
/tmp/Xvfb1414528678591882973.Xauthority
[INFO] Launching Xvfb
[INFO] Waiting for Xvfb...
[INFO] [INFO] Redirecting output to: 
/home/geronimo/geronimo/2.2/testsuite/console-testsuite/advanced/target/selenium/xvfb.log
[INFO] Xvfb started
[INFO] [INFO] [resources:testResources]
[INFO] [INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] [INFO] Copying 1 resource
[INFO] [INFO] skip non existing resourceDirectory 
/home/geronimo/geronimo/2.2/testsuite/console-testsuite/advanced/src/test/filtered-resources
[INFO] [INFO] Copying 3 resources
[INFO] [INFO] [compiler:testCompile]
[INFO] [INFO] Nothing to compile - all classes are up to date
[INFO] [INFO] [surefire:test]
[INFO] [INFO] Tests are skipped.
[INFO] [INFO] [jar:jar]
[INFO] [INFO] Building jar: 
/home/geronimo/geronimo/2.2/testsuite/console-testsuite/advanced/target/advanced-2.2.2-SNAPSHOT.jar
[INFO] [INFO] [selenium:start-server {execution: start}]
[INFO] Launching Selenium Server
[INFO] Waiting for Selenium Server...
[INFO] [INFO] Including display properties from: 
/home/geronimo/geronimo/2.2/testsuite/console-testsuite/advanced/target/selenium/display.properties
[INFO] [INFO] Redirecting output to: 
/home/geronimo/geronimo/2.2/testsuite/console-testsuite/advanced/target/selenium/server.log
[INFO] [INFO] User extensions: 
/home/geronimo/geronimo/2.2/testsuite/console-testsuite/advanced/target/selenium/user-extensions.js
[INFO] Selenium Server started
[INFO] [INFO] [failsafe:integration-test {execution: integration-test}]
[INFO] [INFO] Failsafe report directory: 
/home/geronimo/geronimo/2.2/testsuite/console-testsuite/advanced/target/failsafe-reports
[INFO] 
[INFO] ---
[INFO]  T E S T S
[INFO] ---
[INFO] Running TestSuite
[INFO] Tests run: 12, Failures: 10, Errors: 0, Skipped: 0, Time elapsed: 65.975 
sec <<< FAILURE!
[INFO] 
[INFO] Results :
[INFO] 
[INFO] Failed tests: 
[INFO]   testNewUser(org.apache.geronimo.testsuite.console.ConsoleRealmTest)
[INFO]   testRunSQL(org.apache.geronimo.testsuite.console.DBManagerTest)
[INFO]   testRunSQLDS(org.apache.geronimo.testsuite.console.DatabasePoolTest)
[INFO]   testNewDBPool(org.apache.geronimo.testsuite.console.DatabasePoolTest)
[INFO]   
testEmptyDeployment(org.apache.geronimo.testsuite.console.DeploymentTest)
[INFO]   
testNewJMSResource(org.apache.geronimo.testsuite.console.JMSResourcesTest)
[INFO]   testListPlugins(org.apache.geronimo.testsuite.console.PluginsTest)
[INFO]   
testStartStopConnector(org.apache.geronimo.testsuite.console.WebServerTest)
[INFO]   testNewConnector(org.apache.geronimo.testsuite.console.WebServerTest)
[INFO]   testEditConnector(org.apache.geronimo.testsuite.console.WebServerTest)
[INFO] 
[INFO] Tests run: 12, Failures: 10, Errors: 0, Skipped: 0
[INFO] 
[INFO] [WARNING] File encoding has not been set, using platform encoding 
ANSI_X3.4-1968, i.e. build is platform dependent!
[INFO] [INFO] [selenium:stop-server {execution: stop}]
[INFO] Stopping Selenium server...
[INFO] Stop request sent
[INFO] [INFO] [ianal:verify-legal-f

[jira] Resolved: (GERONIMO-5227) Add ValidatorFactory to servlet context for JSF usage.

2010-08-27 Thread Rick McGuire (JIRA)

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

Rick McGuire resolved GERONIMO-5227.


Resolution: Fixed

Committed revision 990110.

> Add ValidatorFactory to servlet context for JSF usage. 
> ---
>
> Key: GERONIMO-5227
> URL: https://issues.apache.org/jira/browse/GERONIMO-5227
> Project: Geronimo
>  Issue Type: Sub-task
>  Security Level: public(Regular issues) 
>  Components: javaee6, naming
>Affects Versions: 3.0
>Reporter: Rick McGuire
> Fix For: 3.0
>
> Attachments: GERONIMO-5227-jetty.patch, GERONIMO-5227-tomcat.patch
>
>


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



[BUILD] trunk: Failed for Revision: 990054

2010-08-27 Thread gawor
Geronimo Revision: 990054 built with tests included
 
See the full build-0300.log file at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100827/build-0300.log
 
Download the binaries from 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100827
[INFO] BUILD SUCCESSFUL
[INFO] 
[INFO] Total time: 46 minutes 16 seconds
[INFO] Finished at: Fri Aug 27 03:51:34 EDT 2010
[INFO] Final Memory: 463M/1002M
[INFO] 
 
TESTSUITE RESULTS (Failures only)
=
 
Assembly: tomcat
=
See full test results and logs at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100827/logs-0300-tomcat/
 
Running TestSuite
Tests run: 3, Failures: 3, Errors: 0, Skipped: 0, Time elapsed: 16.401 sec <<< 
FAILURE!
--
Running TestSuite
Tests run: 9, Failures: 9, Errors: 0, Skipped: 0, Time elapsed: 61.74 sec <<< 
FAILURE!
--
Running TestSuite
Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 28.651 sec <<< 
FAILURE!
 
Assembly: jetty
=
See full test results and logs at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100827/logs-0300-jetty/
 
Running TestSuite
Tests run: 3, Failures: 3, Errors: 0, Skipped: 0, Time elapsed: 11.05 sec <<< 
FAILURE!
Running TestSuite
Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 5.03 sec <<< 
FAILURE!
--
Running TestSuite
Tests run: 9, Failures: 9, Errors: 0, Skipped: 0, Time elapsed: 49.614 sec <<< 
FAILURE!
 
Samples: trunk
=
Log: 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100827/samples-0300.log
 
Build status: OK
 


[jira] Commented: (GERONIMO-5558) Transaction Commit status is not configured correctly

2010-08-27 Thread Ivan (JIRA)

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

Ivan commented on GERONIMO-5558:


Commit changes to 2.1 branch at rev 990077, those Geronimo 2.2 TCK failure 
cases pass on my workstation.
After we have a full around TCK for 2.2.2, I would commit it to trunk, any 
problem, please let me know !

> Transaction Commit status is not configured correctly
> -
>
> Key: GERONIMO-5558
> URL: https://issues.apache.org/jira/browse/GERONIMO-5558
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: transaction manager
>Affects Versions: 2.2.2, 3.0
>Reporter: Ivan
>Assignee: Ivan
>
> Transaction Commit status is not configured correctly

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



[jira] Assigned: (GERONIMO-5559) "javax.jms.JMSException: Could not connect to broker URL" server startup error exists after change default PortOffset value

2010-08-27 Thread viola.lu (JIRA)

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

viola.lu reassigned GERONIMO-5559:
--

Assignee: viola.lu

> "javax.jms.JMSException: Could not connect to broker URL" server startup 
> error exists after change default PortOffset value
> ---
>
> Key: GERONIMO-5559
> URL: https://issues.apache.org/jira/browse/GERONIMO-5559
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: ActiveMQ
>Affects Versions: 3.0
> Environment: winxp, suse 10 sp2, jdk : jdk 1.6.0_22
>Reporter: viola.lu
>Assignee: viola.lu
>Priority: Minor
> Fix For: 3.0
>
>
> 1. Change PortOffset=0 to  PortOffset=1 under $geronimo_home/ 
> var/config/config-substitutions.properties
> 2.Startup server, start successfully, but a lot of erros popup:
> 2010-08-27 17:26:05,859 ERROR [RecoveryController] Recovery error: Could not 
> get XAResource for recovery for mcf: 
> geronimo:J2EEApplication=null,J2EEServer=geronimo,JCAConnectionFactory=DefaultActiveMQConnectionFactory,JCAManagedConnectionFactory=DefaultActiveMQConnectionFactory,JCAResource=geronimo-activemq-ra-3.0-SNAPSHOT,ResourceAdapter=geronimo-activemq-ra-3.0-SNAPSHOT,ResourceAdapterModule=org.apache.geronimo.configs/activemq-ra/3.0-SNAPSHOT/car,j2eeType=JCAConnectionManager,name=DefaultActiveMQConnectionFactory
> 2010-08-27 17:27:10,937 ERROR [MCFConnectionInterceptor] Error occurred 
> creating ManagedConnection for 
> org.apache.geronimo.connector.outbound.connectioni...@5de7f1
> javax.resource.ResourceException: Could not create connection.
>   at 
> org.apache.activemq.ra.ActiveMQManagedConnectionFactory.createManagedConnection(ActiveMQManagedConnectionFactory.java:171)
>   at 
> org.apache.geronimo.connector.outbound.MCFConnectionInterceptor.getConnection(MCFConnectionInterceptor.java:48)
>   at 
> org.apache.geronimo.connector.outbound.XAResourceInsertionInterceptor.getConnection(XAResourceInsertionInterceptor.java:41)
>   at 
> org.apache.geronimo.connector.outbound.SinglePoolConnectionInterceptor.internalGetConnection(SinglePoolConnectionInterceptor.java:69)
>   at 
> org.apache.geronimo.connector.outbound.AbstractSinglePoolConnectionInterceptor.getConnection(AbstractSinglePoolConnectionInterceptor.java:80)
>   at 
> org.apache.geronimo.connector.outbound.TransactionEnlistingInterceptor.getConnection(TransactionEnlistingInterceptor.java:46)
>   at 
> org.apache.geronimo.connector.outbound.TransactionCachingInterceptor.getConnection(TransactionCachingInterceptor.java:103)
>   at 
> org.apache.geronimo.connector.outbound.TCCLInterceptor.getConnection(TCCLInterceptor.java:39)
>   at 
> org.apache.geronimo.connector.outbound.OutboundNamedXAResourceFactory.getNamedXAResource(OutboundNamedXAResourceFactory.java:56)
>   at 
> org.apache.geronimo.transaction.manager.RecoverTask.run(RecoverTask.java:49)
>   at 
> org.apache.geronimo.transaction.manager.ExponentialtIntervalRetryScheduler$TaskWrapper.run(ExponentialtIntervalRetryScheduler.java:50)
>   at java.util.TimerThread.mainLoop(Timer.java:512)
>   at java.util.TimerThread.run(Timer.java:462)
> Caused by: javax.jms.JMSException: Could not connect to broker URL: 
> tcp://localhost:61617. Reason: java.net.ConnectException: Connection refused: 
> connect
>   at 
> org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:35)
>   at 
> org.apache.activemq.ActiveMQConnectionFactory.createActiveMQConnection(ActiveMQConnectionFactory.java:286)
>   at 
> org.apache.activemq.ActiveMQConnectionFactory.createConnection(ActiveMQConnectionFactory.java:185)
>   at 
> org.apache.activemq.ra.ActiveMQConnectionSupport.makeConnection(ActiveMQConnectionSupport.java:79)
>   at 
> org.apache.activemq.ra.ActiveMQConnectionSupport.makeConnection(ActiveMQConnectionSupport.java:61)
>   at 
> org.apache.activemq.ra.ActiveMQManagedConnectionFactory.createManagedConnection(ActiveMQManagedConnectionFactory.java:169)
>   ... 12 more
> Caused by: java.net.ConnectException: Connection refused: connect
>   at java.net.PlainSocketImpl.socketConnect(Native Method)
>   at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
>   at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
>   at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
>   at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
>   at java.net.Socket.connect(Socket.java:529)
>   at 
> org.apache.activemq.transport.tcp.TcpTransport.connect(TcpTransport.java:483)
>   at 
> org.apache.activemq.transport.tcp.TcpTransport.doStart(TcpTransport.ja

[jira] Created: (GERONIMO-5559) "javax.jms.JMSException: Could not connect to broker URL" server startup error exists after change default PortOffset value

2010-08-27 Thread viola.lu (JIRA)
"javax.jms.JMSException: Could not connect to broker URL" server startup error 
exists after change default PortOffset value
---

 Key: GERONIMO-5559
 URL: https://issues.apache.org/jira/browse/GERONIMO-5559
 Project: Geronimo
  Issue Type: Bug
  Security Level: public (Regular issues)
  Components: ActiveMQ
Affects Versions: 3.0
 Environment: winxp, suse 10 sp2, jdk : jdk 1.6.0_22
Reporter: viola.lu
Priority: Minor
 Fix For: 3.0


1. Change PortOffset=0 to  PortOffset=1 under $geronimo_home/ 
var/config/config-substitutions.properties
2.Startup server, start successfully, but a lot of erros popup:

2010-08-27 17:26:05,859 ERROR [RecoveryController] Recovery error: Could not 
get XAResource for recovery for mcf: 
geronimo:J2EEApplication=null,J2EEServer=geronimo,JCAConnectionFactory=DefaultActiveMQConnectionFactory,JCAManagedConnectionFactory=DefaultActiveMQConnectionFactory,JCAResource=geronimo-activemq-ra-3.0-SNAPSHOT,ResourceAdapter=geronimo-activemq-ra-3.0-SNAPSHOT,ResourceAdapterModule=org.apache.geronimo.configs/activemq-ra/3.0-SNAPSHOT/car,j2eeType=JCAConnectionManager,name=DefaultActiveMQConnectionFactory
2010-08-27 17:27:10,937 ERROR [MCFConnectionInterceptor] Error occurred 
creating ManagedConnection for 
org.apache.geronimo.connector.outbound.connectioni...@5de7f1
javax.resource.ResourceException: Could not create connection.
at 
org.apache.activemq.ra.ActiveMQManagedConnectionFactory.createManagedConnection(ActiveMQManagedConnectionFactory.java:171)
at 
org.apache.geronimo.connector.outbound.MCFConnectionInterceptor.getConnection(MCFConnectionInterceptor.java:48)
at 
org.apache.geronimo.connector.outbound.XAResourceInsertionInterceptor.getConnection(XAResourceInsertionInterceptor.java:41)
at 
org.apache.geronimo.connector.outbound.SinglePoolConnectionInterceptor.internalGetConnection(SinglePoolConnectionInterceptor.java:69)
at 
org.apache.geronimo.connector.outbound.AbstractSinglePoolConnectionInterceptor.getConnection(AbstractSinglePoolConnectionInterceptor.java:80)
at 
org.apache.geronimo.connector.outbound.TransactionEnlistingInterceptor.getConnection(TransactionEnlistingInterceptor.java:46)
at 
org.apache.geronimo.connector.outbound.TransactionCachingInterceptor.getConnection(TransactionCachingInterceptor.java:103)
at 
org.apache.geronimo.connector.outbound.TCCLInterceptor.getConnection(TCCLInterceptor.java:39)
at 
org.apache.geronimo.connector.outbound.OutboundNamedXAResourceFactory.getNamedXAResource(OutboundNamedXAResourceFactory.java:56)
at 
org.apache.geronimo.transaction.manager.RecoverTask.run(RecoverTask.java:49)
at 
org.apache.geronimo.transaction.manager.ExponentialtIntervalRetryScheduler$TaskWrapper.run(ExponentialtIntervalRetryScheduler.java:50)
at java.util.TimerThread.mainLoop(Timer.java:512)
at java.util.TimerThread.run(Timer.java:462)
Caused by: javax.jms.JMSException: Could not connect to broker URL: 
tcp://localhost:61617. Reason: java.net.ConnectException: Connection refused: 
connect
at 
org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:35)
at 
org.apache.activemq.ActiveMQConnectionFactory.createActiveMQConnection(ActiveMQConnectionFactory.java:286)
at 
org.apache.activemq.ActiveMQConnectionFactory.createConnection(ActiveMQConnectionFactory.java:185)
at 
org.apache.activemq.ra.ActiveMQConnectionSupport.makeConnection(ActiveMQConnectionSupport.java:79)
at 
org.apache.activemq.ra.ActiveMQConnectionSupport.makeConnection(ActiveMQConnectionSupport.java:61)
at 
org.apache.activemq.ra.ActiveMQManagedConnectionFactory.createManagedConnection(ActiveMQManagedConnectionFactory.java:169)
... 12 more
Caused by: java.net.ConnectException: Connection refused: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
at java.net.Socket.connect(Socket.java:529)
at 
org.apache.activemq.transport.tcp.TcpTransport.connect(TcpTransport.java:483)
at 
org.apache.activemq.transport.tcp.TcpTransport.doStart(TcpTransport.java:446)
at org.apache.activemq.util.ServiceSupport.start(ServiceSupport.java:53)
at 
org.apache.activemq.transport.TransportFilter.start(TransportFilter.java:58)
at 
org.apache.activemq.transport.TransportFilter.start(TransportFilter.java:58)
at 
org.apache.activemq.transport.WireFormatNegotiator.start(WireFor

[jira] Created: (GERONIMO-5558) Transaction Commit status is not configured correctly

2010-08-27 Thread Ivan (JIRA)
Transaction Commit status is not configured correctly
-

 Key: GERONIMO-5558
 URL: https://issues.apache.org/jira/browse/GERONIMO-5558
 Project: Geronimo
  Issue Type: Bug
  Security Level: public (Regular issues)
  Components: transaction manager
Affects Versions: 2.2.2, 3.0
Reporter: Ivan
Assignee: Ivan


Transaction Commit status is not configured correctly

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



[jira] Updated: (GERONIMO-5469) Add EJB cluster testsuite

2010-08-27 Thread viola.lu (JIRA)

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

viola.lu updated GERONIMO-5469:
---

Attachment: G5469.patch

Based on Shawn's suggestion, create a new patch, pls review it, thanks in 
advance!

> Add EJB cluster testsuite
> -
>
> Key: GERONIMO-5469
> URL: https://issues.apache.org/jira/browse/GERONIMO-5469
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: testsuite
>Affects Versions: 2.2.2
>Reporter: viola.lu
>Assignee: viola.lu
>Priority: Minor
> Fix For: 2.2.2
>
> Attachments: G5469.patch, G5469.patch
>
>
> 1.Create two servers with maven ant plugin which will copy servers from 
> geornimo tomcat javaee assemly and overridde config-subsitution.properties to 
> each server
> 2.Start two server instances , deploy loadbean to two servers, run ejb client 
> against two: failover:ejbd://127.0.0.1:4202,ejbd://127.0.0.1:4211"
> 3.Stop one server and run ejb client again. It still work, just on warning: 
> one server down. 

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



[jira] Assigned: (GERONIMO-5557) Add more context level configurations for Tomcat

2010-08-27 Thread viola.lu (JIRA)

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

viola.lu reassigned GERONIMO-5557:
--

Assignee: viola.lu

> Add more context level configurations for Tomcat
> 
>
> Key: GERONIMO-5557
> URL: https://issues.apache.org/jira/browse/GERONIMO-5557
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>Affects Versions: 2.2.2, 3.0
>Reporter: Ivan
>Assignee: viola.lu
>
> In the latest Tomcat build, more paramter could be configured on the context 
> level
> A request thread in user-geronimo mail list : 
> http://osdir.com/ml/user-geronimo-apache/2010-08/msg3.html

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



[jira] Updated: (GERONIMO-5538) Add testsuite for webbean 1.0 in Java EE 6

2010-08-27 Thread LiWenQin (JIRA)

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

LiWenQin updated GERONIMO-5538:
---

Attachment: webbean-jpa-test.patch

webbean-jpa-test.patch tests JSF+Webbean+JPA, Scope Annotation, Inject 
annotation, events, interceptors, decorators.

> Add testsuite for webbean 1.0  in Java EE 6
> ---
>
> Key: GERONIMO-5538
> URL: https://issues.apache.org/jira/browse/GERONIMO-5538
> Project: Geronimo
>  Issue Type: Task
>  Security Level: public(Regular issues) 
>  Components: testsuite
>Affects Versions: 3.0
>Reporter: Lu Jiang
>Assignee: Forrest Xia
> Attachments: webbean-jpa-test.patch, webbean-servlet-test.patch, 
> webbean_conversation_final.patch, webbean_ejb_final.patch
>
>
> Pull the samples from Apache openwebbeans project.And make testsuites for 
> them to test these features automatically.
> The testsuites may include:
> 1.webbean+JSF
> 2.Scope Annotation in webbean(especially conversation scope)
> 3.webbean+EJB
> 4.webbean+Servlet
> 5.webbean+JPA
> 6.webban+MessageDrivenBean

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



[jira] Created: (GERONIMO-5557) Add more context level configurations for Tomcat

2010-08-27 Thread Ivan (JIRA)
Add more context level configurations for Tomcat


 Key: GERONIMO-5557
 URL: https://issues.apache.org/jira/browse/GERONIMO-5557
 Project: Geronimo
  Issue Type: Bug
  Security Level: public (Regular issues)
Affects Versions: 2.2.2, 3.0
Reporter: Ivan


In the latest Tomcat build, more paramter could be configured on the context 
level
A request thread in user-geronimo mail list : 
http://osdir.com/ml/user-geronimo-apache/2010-08/msg3.html

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



[jira] Assigned: (GERONIMO-5511) context-priority-classloader is not allowed in geronimo-web.xml for backwards compatibility

2010-08-27 Thread Ivan (JIRA)

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

Ivan reassigned GERONIMO-5511:
--

Assignee: Ivan  (was: viola.lu)

> context-priority-classloader is not allowed in geronimo-web.xml for backwards 
> compatibility
> ---
>
> Key: GERONIMO-5511
> URL: https://issues.apache.org/jira/browse/GERONIMO-5511
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: web
>Affects Versions: 3.0
> Environment: Ubuntu 8.04 x86-32
> Sun java 1.6.0_20
>Reporter: Forrest Xia
>Assignee: Ivan
>Priority: Minor
> Attachments: G5511.patch
>
>
> If the geronimo-web.xml includes element "", 
> the deployment will fail at validating xml schema like this:
> 2010-08-09 13:02:06,051 ERROR [DeploymentPortlet] Deployment failed
> xml problem for web app web.war
> org.apache.geronimo.common.DeploymentException: xml problem for web app 
> web.war
>   at 
> org.apache.geronimo.tomcat.deployment.TomcatModuleBuilder.getTomcatWebApp(TomcatModuleBuilder.java:381)
>   at 
> org.apache.geronimo.tomcat.deployment.TomcatModuleBuilder.createModule(TomcatModuleBuilder.java:275)
>   at 
> org.apache.geronimo.web25.deployment.AbstractWebModuleBuilder.createModule(AbstractWebModuleBuilder.java:273)
>   at 
> org.apache.geronimo.j2ee.deployment.SwitchingModuleBuilder.createModule(SwitchingModuleBuilder.java:153)
>   at 
> org.apache.geronimo.j2ee.deployment.EARConfigBuilder.addModules(EARConfigBuilder.java:864)
>   at 
> org.apache.geronimo.j2ee.deployment.EARConfigBuilder.getEarPlan(EARConfigBuilder.java:457)
>   at 
> org.apache.geronimo.j2ee.deployment.EARConfigBuilder.getDeploymentPlan(EARConfigBuilder.java:319)
>   at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:231)
>   at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:138)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>   at java.lang.reflect.Method.invoke(Method.java:597)
>   at 
> org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34)
>   at 
> org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:131)
>   at 
> org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:872)
>   at 
> org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:245)
>   at 
> org.apache.geronimo.deployment.plugin.local.AbstractDeployCommand.doDeploy(AbstractDeployCommand.java:116)
>   at 
> org.apache.geronimo.deployment.plugin.local.DistributeCommand.run(DistributeCommand.java:61)
>   at java.lang.Thread.run(Thread.java:619)
> Caused by: org.apache.xmlbeans.XmlException: Invalid deployment descriptor: 
> errors:
> error: cvc-complex-type.3.2.1: Attribute not allowed (no wildcards allowed): 
> configId
> error: cvc-complex-type.3.2.1: Attribute not allowed (no wildcards allowed): 
> parentId
> error: cvc-complex-type.2.4a: Expected elements 
> 'environm...@http://geronimo.apache.org/xml/ns/deployment-1.2 
> context-r...@http://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 
> work-...@http://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 
> cluster...@http://geronimo.apache.org/xml/ns/j2ee/application-2.0 
> web-contai...@http://geronimo.apache.org/xml/ns/naming-1.2 
> h...@http://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 
> cross-cont...@http://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 
> disable-cook...@http://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 
> valve-ch...@http://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 
> listener-ch...@http://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 
> tomcat-re...@http://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 
> mana...@http://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 
> clus...@http://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 
> abstract-naming-en...@http://geronimo.apache.org/xml/ns/naming-1.2 
> env-en...@http://geronimo.apache.org/xml/ns/naming-1.2 
> ejb-...@http://geronimo.apache.org/xml/ns/naming-1.2 
> ejb-local-...@http://geronimo.apache.org/xml/ns/naming-1.2 
> service-...@http://geronimo.apache.org/xml/ns/naming-1.2 
> resource-...@http://geronimo.apache.org/xml/ns/naming-1.2 
> resource-env-...@http://geronimo.apache.org/xml/ns/naming-1.2 
> message-destinat...@http://geronimo.apache.org/xml/ns/naming-1.2 
> security-realm-n...@http://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 
> serv...@http://geronimo.apache.org/xml/ns/deployment-1.2' instead of