RE: Please try out the upgrade jar
Hi David, The dependency tags for the the module ID of the server wide datasource in the Geronimo-web.xml were not required for 1.0, so it is unnatural for user to know they are required for 1.1. If the upgrader tool doesnt indicate that, user will just have to go figure that out by luck. One a second thought, I dont quite understand why we need to have the datasource as the dependency in 1.1 while we dont need it as the dependency in 1.0. The Geronimo-web.xml already has the ref-name and resource-link information within the resource-ref tags. Thanks, Lin -Original Message- From: David Jencks [mailto:[EMAIL PROTECTED] Sent: Friday, June 02, 2006 12:01 AM To: dev@geronimo.apache.org Subject: Re: Please try out the upgrade jar On Jun 1, 2006, at 7:56 PM, Song Scorpio wrote: I just tried the new upgrade.jar within server runtime, context-priority-classloader element is gone. But there's still no datasource dependency, which will cause failure of application deployment.. Do you think the upgrade tool should insert comments into every plan about likely problems such as this one about datasources? Since it's possible to resolve a resource-ref without a plan entry if the resource-ref uses the same name as the datasource plan, we'd have to look at the j2ee deployment descriptors to be sure whether or not a jndi ref was present. Looking into dds is beyond what I think the upgrade tool should be doing. However, adding comments always would be pretty easy to do, I didn't think to do it however. thanks david jencks 2006/6/2, Donald Woods [EMAIL PROTECTED]: How old is the upgrade.jar you are using? Noticed that your generated plan still has the old context-priority-classloader element in it. -Donald Zhang Song wrote: For an application which is using datasource, we should manually add dependency to deployment plan upgraded by the tool. The plan upgraded by the tool is following: - # web-app xmlns =* http://geronimo.apache.org/xml/ns/j2ee/web-1.0*; xmlns:naming =*http://geronimo.apache.org/xml/ns/naming-1.1*; xmlns:sec= * http://geronimo.apache.org/xml/ns/security-1.1*; xmlns:sys= *http://geronimo.apache.org/xml/ns/deployment-1.1* - # sys:environment - # sys:moduleId sys:groupIdSample/ sys:groupId sys:artifactIdEMPdemo/ sys:artifactId sys:version1.1/ sys:version sys:typecar/ sys:type /sys:moduleId sys:dependencies / sys:hidden-classes / sys:non-overridable-classes / /sys:environment context-root/EMPdemo/ context-root context-priority-classloaderfalse /context-priority-classloader - # naming:resource-ref naming:ref-namejdbc/DataSource /naming:ref-name naming:resource-linkSystemDatasource /naming:resource-link /naming:resource-ref /web-app But this upgraded plan will cause following error during deployment: -- Error: Unable to distribute EMPdemo-1.0.war: Unable to resolve resource reference 'jdbc/DataSource' (Could not find resource 'jdbc/EmployeeDatasource'. Perhaps it has not yet been configured, or your application does not have a dependency declared for that resource module?) -- After I add datasource's module reference to the upgraded plan, that application can be deployed successfully. -- - # sys:environment - # sys:moduleId sys:groupIdSample/ sys:groupId sys:artifactIdEMPdemo/ sys:artifactId sys:version1.1/ sys:version sys:typecar/ sys:type /sys:moduleId - # sys:dependencies - # sys:dependency sys:groupIdSample/ sys:groupId sys:artifactIdEmployeeDatasource /sys:artifactId sys:version1.1/ sys:version sys:typecar/ sys:type /sys:dependency /sys:dependencies sys:hidden-classes / sys:non-overridable-classes / /sys:environment context-root/EMPdemo/ context-root context-priority-classloaderfalse /context-priority-classloader - # naming:resource-ref naming:ref-namejdbc/DataSource /naming:ref-name naming:resource-linkjdbc/EmployeeDatasource /naming:resource-link /naming:resource-ref /web-app -- Could the upgrade tool add some comments to plan or give a warning to user when processing with datasource?
Re: Please try out the upgrade jar
For an application which is using datasource, we should manually add dependency to deployment plan upgraded by the tool.The plan upgraded by the tool is following: - web-app xmlns =http://geronimo.apache.org/xml/ns/j2ee/web-1.0 xmlns:naming =http://geronimo.apache.org/xml/ns/naming-1.1 xmlns:sec= http://geronimo.apache.org/xml/ns/security-1.1 xmlns:sys= http://geronimo.apache.org/xml/ns/deployment-1.1 - sys:environment - sys:moduleId sys:groupIdSample/ sys:groupId sys:artifactIdEMPdemo/ sys:artifactId sys:version1.1/ sys:version sys:typecar/ sys:type /sys:moduleId sys:dependencies / sys:hidden-classes / sys:non-overridable-classes / /sys:environment context-root/EMPdemo/ context-root context-priority-classloaderfalse /context-priority-classloader - naming:resource-ref naming:ref-namejdbc/DataSource /naming:ref-name naming:resource-linkSystemDatasource /naming:resource-link /naming:resource-ref /web-appBut this upgraded plan will cause following error during deployment:-- Error: Unable to distribute EMPdemo-1.0.war: Unable to resolve resource reference 'jdbc/DataSource' (Could not find resource 'jdbc/EmployeeDatasource'. Perhaps it has not yet been configured, or your application does not have a dependency declared for that resource module?)--After I add datasource's module reference to the upgraded plan, that application can be deployed successfully.-- - sys:environment - sys:moduleId sys:groupIdSample/ sys:groupId sys:artifactIdEMPdemo/ sys:artifactId sys:version1.1/ sys:version sys:typecar/ sys:type /sys:moduleId - sys:dependencies - sys:dependency sys:groupIdSample/ sys:groupId sys:artifactIdEmployeeDatasource /sys:artifactId sys:version1.1/ sys:version sys:typecar/ sys:type /sys:dependency /sys:dependencies sys:hidden-classes / sys:non-overridable-classes / /sys:environment context-root/EMPdemo/ context-root context-priority-classloaderfalse /context-priority-classloader - naming:resource-ref naming:ref-namejdbc/DataSource /naming:ref-name naming:resource-linkjdbc/EmployeeDatasource /naming:resource-link /naming:resource-ref /web-app--Could the upgrade tool add some comments to plan or give a warning to user when processing with datasource?
Re: Please try out the upgrade jar
How old is the upgrade.jar you are using? Noticed that your generated plan still has the old context-priority-classloader element in it. -Donald Zhang Song wrote: For an application which is using datasource, we should manually add dependency to deployment plan upgraded by the tool. The plan upgraded by the tool is following: - # web-app xmlns =*http://geronimo.apache.org/xml/ns/j2ee/web-1.0*; xmlns:naming =*http://geronimo.apache.org/xml/ns/naming-1.1*; xmlns:sec= *http://geronimo.apache.org/xml/ns/security-1.1*; xmlns:sys= *http://geronimo.apache.org/xml/ns/deployment-1.1*; - # sys:environment - # sys:moduleId sys:groupIdSample/ sys:groupId sys:artifactIdEMPdemo/ sys:artifactId sys:version1.1/ sys:version sys:typecar/ sys:type /sys:moduleId sys:dependencies / sys:hidden-classes / sys:non-overridable-classes / /sys:environment context-root/EMPdemo/ context-root context-priority-classloaderfalse /context-priority-classloader - # naming:resource-ref naming:ref-namejdbc/DataSource /naming:ref-name naming:resource-linkSystemDatasource /naming:resource-link /naming:resource-ref /web-app But this upgraded plan will cause following error during deployment: -- Error: Unable to distribute EMPdemo-1.0.war: Unable to resolve resource reference 'jdbc/DataSource' (Could not find resource 'jdbc/EmployeeDatasource'. Perhaps it has not yet been configured, or your application does not have a dependency declared for that resource module?) -- After I add datasource's module reference to the upgraded plan, that application can be deployed successfully. -- - # sys:environment - # sys:moduleId sys:groupIdSample/ sys:groupId sys:artifactIdEMPdemo/ sys:artifactId sys:version1.1/ sys:version sys:typecar/ sys:type /sys:moduleId - # sys:dependencies - # sys:dependency sys:groupIdSample/ sys:groupId sys:artifactIdEmployeeDatasource /sys:artifactId sys:version1.1/ sys:version sys:typecar/ sys:type /sys:dependency /sys:dependencies sys:hidden-classes / sys:non-overridable-classes / /sys:environment context-root/EMPdemo/ context-root context-priority-classloaderfalse /context-priority-classloader - # naming:resource-ref naming:ref-namejdbc/DataSource /naming:ref-name naming:resource-linkjdbc/EmployeeDatasource /naming:resource-link /naming:resource-ref /web-app -- Could the upgrade tool add some comments to plan or give a warning to user when processing with datasource? smime.p7s Description: S/MIME Cryptographic Signature
Re: Please try out the upgrade jar
I just tried the new upgrade.jar within server runtime, context-priority-classloader element is gone. But there's still no datasource dependency, which will cause failure of application deployment.. 2006/6/2, Donald Woods [EMAIL PROTECTED]: How old is the upgrade.jar you are using?Noticed that your generated plan still has the oldcontext-priority-classloader element in it.-DonaldZhang Song wrote: For an application which is using datasource, we should manually add dependency to deployment plan upgraded by the tool. The plan upgraded by the tool is following: - # web-app xmlns =* http://geronimo.apache.org/xml/ns/j2ee/web-1.0* xmlns:naming =*http://geronimo.apache.org/xml/ns/naming-1.1* xmlns:sec= * http://geronimo.apache.org/xml/ns/security-1.1* xmlns:sys= *http://geronimo.apache.org/xml/ns/deployment-1.1* - # sys:environment - # sys:moduleId sys:groupIdSample/ sys:groupId sys:artifactIdEMPdemo/ sys:artifactId sys:version1.1/ sys:version sys:typecar/ sys:type /sys:moduleId sys:dependencies / sys:hidden-classes / sys:non-overridable-classes / /sys:environment context-root/EMPdemo/ context-root context-priority-classloaderfalse /context-priority-classloader - # naming:resource-ref naming:ref-namejdbc/DataSource /naming:ref-name naming:resource-linkSystemDatasource /naming:resource-link /naming:resource-ref /web-app But this upgraded plan will cause following error during deployment: --Error: Unable to distribute EMPdemo-1.0.war: Unable to resolve resource reference 'jdbc/DataSource' (Could not find resource'jdbc/EmployeeDatasource'.Perhaps it has not yet been configured,or your application does not have a dependency declared for that resource module?) -- After I add datasource's module reference to the upgraded plan, that application can be deployed successfully. -- - # sys:environment - # sys:moduleId sys:groupIdSample/ sys:groupId sys:artifactIdEMPdemo/ sys:artifactId sys:version1.1/ sys:version sys:typecar/ sys:type /sys:moduleId - # sys:dependencies - # sys:dependency sys:groupIdSample/ sys:groupId sys:artifactIdEmployeeDatasource /sys:artifactId sys:version1.1/ sys:version sys:typecar/ sys:type /sys:dependency /sys:dependencies sys:hidden-classes / sys:non-overridable-classes / /sys:environment context-root/EMPdemo/ context-root context-priority-classloaderfalse /context-priority-classloader - # naming:resource-ref naming:ref-namejdbc/DataSource /naming:ref-name naming:resource-linkjdbc/EmployeeDatasource /naming:resource-link /naming:resource-ref /web-app -- Could the upgrade tool add some comments to plan or give a warning to user when processing with datasource?
Re: Please try out the upgrade jar
On Jun 1, 2006, at 7:56 PM, Song Scorpio wrote:I just tried the new upgrade.jar within server runtime, context-priority-classloader element is gone. But there's still no datasource dependency, which will cause failure of application deployment..Do you think the upgrade tool should insert comments into every plan about likely problems such as this one about datasources? Since it's possible to resolve a resource-ref without a plan entry if the resource-ref uses the same name as the datasource plan, we'd have to look at the j2ee deployment descriptors to be sure whether or not a jndi ref was present. Looking into dds is beyond what I think the upgrade tool should be doing. However, adding comments always would be pretty easy to do, I didn't think to do it however.thanksdavid jencks 2006/6/2, Donald Woods [EMAIL PROTECTED]: How old is the upgrade.jar you are using?Noticed that your generated plan still has the oldcontext-priority-classloader element in it.-DonaldZhang Song wrote: For an application which is using datasource, we should manually add dependency to deployment plan upgraded by the tool. The plan upgraded by the tool is following: - # web-app xmlns ="* http://geronimo.apache.org/xml/ns/j2ee/web-1.0*" xmlns:naming ="*http://geronimo.apache.org/xml/ns/naming-1.1*" xmlns:sec=" * http://geronimo.apache.org/xml/ns/security-1.1*" xmlns:sys=" *http://geronimo.apache.org/xml/ns/deployment-1.1* " - # sys:environment - # sys:moduleId sys:groupIdSample/ sys:groupId sys:artifactIdEMPdemo/ sys:artifactId sys:version1.1/ sys:version sys:typecar/ sys:type /sys:moduleId sys:dependencies / sys:hidden-classes / sys:non-overridable-classes / /sys:environment context-root/EMPdemo/ context-root context-priority-classloaderfalse /context-priority-classloader - # naming:resource-ref naming:ref-namejdbc/DataSource /naming:ref-name naming:resource-linkSystemDatasource /naming:resource-link /naming:resource-ref /web-app But this upgraded plan will cause following error during deployment: --Error: Unable to distribute EMPdemo-1.0.war: Unable to resolve resource reference 'jdbc/DataSource' (Could not find resource'jdbc/EmployeeDatasource'. Perhaps it has not yet been configured,or your application does not have a dependency declared for that resource module?) -- After I add datasource's module reference to the upgraded plan, that application can be deployed successfully. -- - # sys:environment - # sys:moduleId sys:groupIdSample/ sys:groupId sys:artifactIdEMPdemo/ sys:artifactId sys:version1.1/ sys:version sys:typecar/ sys:type /sys:moduleId - # sys:dependencies - # sys:dependency sys:groupIdSample/ sys:groupId sys:artifactIdEmployeeDatasource /sys:artifactId sys:version1.1/ sys:version sys:typecar/ sys:type /sys:dependency /sys:dependencies sys:hidden-classes / sys:non-overridable-classes / /sys:environment context-root/EMPdemo/ context-root context-priority-classloaderfalse /context-priority-classloader - # naming:resource-ref naming:ref-namejdbc/DataSource /naming:ref-name naming:resource-linkjdbc/EmployeeDatasource /naming:resource-link /naming:resource-ref /web-app -- Could the upgrade tool add some comments to plan or give a warning to user when processing with datasource?
RE: Please try out the upgrade jar
Hi David, How are we supposed to run the latest upgrade tool now that it is a module inside of Geronimo? I am able to see the upgraded plan from admin console, but I haven't been able to get the latest upgrade tool by itself running. What I did was: E:\geronimo-1.1-SNAPSHOT\binjava -jar client.jar geronimo/upgrade-cli/1.1-SNAPSHOT java.lang.IllegalArgumentException: Invalid id: geronimo/upgrade-cli/1.1-SNAPSHOT at org.apache.geronimo.kernel.repository.Artifact.create(Artifact.java:4 9) at org.apache.geronimo.system.main.ClientCommandLine.main(ClientCommandL ine.java:46) I also tried to execute deploy.bat start geronimo/upgrade/1.1-SNAPSHOT/car before it, but it didn't make any difference. Thanks, Lin -Original Message- From: David Jencks [mailto:[EMAIL PROTECTED] Sent: Monday, May 29, 2006 1:36 PM To: dev@geronimo.apache.org Subject: Re: Please try out the upgrade jar Toby, Thanks for pointing this out. I've fixed it in 1.1, will port to trunk soon. See http://issues.apache.org/jira/browse/GERONIMO-2068 thanks david jencks On May 26, 2006, at 3:29 PM, toby cabot wrote: David, Thanks for providing this tool, it's a big help. I had some problems on a test geronimo-application.xml file that includes some gbean references (for hooking up to security gbeans). The file looks like: = ?xml version=1.0 ? application xmlns=http://geronimo.apache.org/xml/ns/j2ee/ application configId=hello parentId=geronimo/j2ee-security/1.0.1-SNAPSHOT/car gbean name=hello-realm class=org.apache.geronimo.security.realm.GenericSecurityRealm attribute name=realmNamehello-realm/attribute reference name=LoginModuleConfiguration namehello-login-chain/name /reference reference name=ServerInfo gbean- namegeronimo.server:J2EEApplication=null,J2EEModule=geronimo/j2ee- system/1.0.1-SNAPSHOT/ car,J2EEServer=geronimo,j2eeType=GBean,name=ServerInfo/gbean-name /reference reference name=LoginService gbean- namegeronimo.server:J2EEApplication=null,J2EEModule=geronimo/j2ee- security/1.0.1-SNAPSHOT/ car,J2EEServer=geronimo,j2eeType=JaasLoginService,name=JaasLoginServic e/gbean-name /reference /gbean gbean name=hello-login-chain class=org.apache.geronimo.security.jaas.JaasLoginModuleUse attribute name=controlFlagREQUIRED/attribute reference name=LoginModule namehello-login/name /reference /gbean gbean name=hello-login class=org.apache.geronimo.security.jaas.LoginModuleGBean attribute name=loginModuleClassreva.common.auth.TrivialLoginModule/ attribute attribute name=serverSidetrue/attribute attribute name=options usersURI=var/security/demo_users.properties groupsURI=var/security/demo_groups.properties /attribute attribute name=loginDomainNamehello-realm/attribute /gbean /application = The problem seems to be the application/gbean/reference/gbean-name elements, as the error I get at offline deploy time looks like: Deployer operation failed: org.apache.xmlbeans.XmlException: Invalid deployment descriptor: [error: cvc-complex-type.2.4a: Expected elements '[EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ deployment-1.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ deployment-1.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ deployment-1.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ deployment-1.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ deployment-1.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ deployment-1.1' instead of '[EMAIL PROTECTED]://geronimo.apache.org/ xml/ns/deployment-1.1' here in element [EMAIL PROTECTED]:// geronimo.apache.org/xml/ns/deployment-1.1, error: cvc-complex-type. 2.4a: Expected elements '[EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ deployment-1.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ deployment-1.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ deployment-1.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ deployment-1.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ deployment-1.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ deployment-1.1' instead of '[EMAIL PROTECTED]://geronimo.apache.org/ xml/ns/deployment-1.1' here in element [EMAIL PROTECTED]:// geronimo.apache.org/xml/ns/deployment-1.1] Descriptor: xml-fragment xmlns:dep=http://geronimo.apache.org/xml/ ns/deployment-1.1 dep:environment dep:moduleId dep:groupIddefault/dep:groupId dep:artifactIdhello/dep:artifactId dep:version1-default/dep:version dep:typecar/dep:type /dep:moduleId dep:dependencies dep:dependency dep:groupIdgeronimo/dep:groupId dep:artifactIdj2ee-security/dep:artifactId
Re: Please try out the upgrade jar
E:\geronimo-1.1-SNAPSHOT\binjava -jar upgrade.jar Parameter usage: inputPlan outputPlan or inputPlan in which case the output will be in the same location as inputPlan with '.upgraded' appended Lin Sun wrote: Hi David, How are we supposed to run the latest upgrade tool now that it is a module inside of Geronimo? I am able to see the upgraded plan from admin console, but I haven't been able to get the latest upgrade tool by itself running. What I did was: E:\geronimo-1.1-SNAPSHOT\binjava -jar client.jar geronimo/upgrade-cli/1.1-SNAPSHOT java.lang.IllegalArgumentException: Invalid id: geronimo/upgrade-cli/1.1-SNAPSHOT at org.apache.geronimo.kernel.repository.Artifact.create(Artifact.java:4 9) at org.apache.geronimo.system.main.ClientCommandLine.main(ClientCommandL ine.java:46) I also tried to execute deploy.bat start geronimo/upgrade/1.1-SNAPSHOT/car before it, but it didn't make any difference. Thanks, Lin -Original Message- From: David Jencks [mailto:[EMAIL PROTECTED] Sent: Monday, May 29, 2006 1:36 PM To: dev@geronimo.apache.org Subject: Re: Please try out the upgrade jar Toby, Thanks for pointing this out. I've fixed it in 1.1, will port to trunk soon. See http://issues.apache.org/jira/browse/GERONIMO-2068 thanks david jencks On May 26, 2006, at 3:29 PM, toby cabot wrote: David, Thanks for providing this tool, it's a big help. I had some problems on a test geronimo-application.xml file that includes some gbean references (for hooking up to security gbeans). The file looks like: = ?xml version=1.0 ? application xmlns=http://geronimo.apache.org/xml/ns/j2ee/ application configId=hello parentId=geronimo/j2ee-security/1.0.1-SNAPSHOT/car gbean name=hello-realm class=org.apache.geronimo.security.realm.GenericSecurityRealm attribute name=realmNamehello-realm/attribute reference name=LoginModuleConfiguration namehello-login-chain/name /reference reference name=ServerInfo gbean- namegeronimo.server:J2EEApplication=null,J2EEModule=geronimo/j2ee- system/1.0.1-SNAPSHOT/ car,J2EEServer=geronimo,j2eeType=GBean,name=ServerInfo/gbean-name /reference reference name=LoginService gbean- namegeronimo.server:J2EEApplication=null,J2EEModule=geronimo/j2ee- security/1.0.1-SNAPSHOT/ car,J2EEServer=geronimo,j2eeType=JaasLoginService,name=JaasLoginServic e/gbean-name /reference /gbean gbean name=hello-login-chain class=org.apache.geronimo.security.jaas.JaasLoginModuleUse attribute name=controlFlagREQUIRED/attribute reference name=LoginModule namehello-login/name /reference /gbean gbean name=hello-login class=org.apache.geronimo.security.jaas.LoginModuleGBean attribute name=loginModuleClassreva.common.auth.TrivialLoginModule/ attribute attribute name=serverSidetrue/attribute attribute name=options usersURI=var/security/demo_users.properties groupsURI=var/security/demo_groups.properties /attribute attribute name=loginDomainNamehello-realm/attribute /gbean /application = The problem seems to be the application/gbean/reference/gbean-name elements, as the error I get at offline deploy time looks like: Deployer operation failed: org.apache.xmlbeans.XmlException: Invalid deployment descriptor: [error: cvc-complex-type.2.4a: Expected elements '[EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ deployment-1.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ deployment-1.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ deployment-1.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ deployment-1.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ deployment-1.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ deployment-1.1' instead of '[EMAIL PROTECTED]://geronimo.apache.org/ xml/ns/deployment-1.1' here in element [EMAIL PROTECTED]:// geronimo.apache.org/xml/ns/deployment-1.1, error: cvc-complex-type. 2.4a: Expected elements '[EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ deployment-1.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ deployment-1.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ deployment-1.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ deployment-1.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ deployment-1.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ deployment-1.1' instead of '[EMAIL PROTECTED]://geronimo.apache.org/ xml/ns/deployment-1.1' here in element [EMAIL PROTECTED]:// geronimo.apache.org/xml/ns/deployment-1.1] Descriptor: xml-fragment xmlns:dep=http://geronimo.apache.org/xml/ ns/deployment-1.1 dep:environment dep:moduleId dep:groupIddefault/dep:groupId dep:artifactIdhello/dep:artifactId dep:version1-default/dep:version dep:typecar/dep:type /dep:moduleId dep:dependencies
RE: Please try out the upgrade jar
Thanks, that worked very well! -Original Message- From: Donald Woods [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 31, 2006 4:48 PM To: dev@geronimo.apache.org Subject: Re: Please try out the upgrade jar E:\geronimo-1.1-SNAPSHOT\binjava -jar upgrade.jar Parameter usage: inputPlan outputPlan or inputPlan in which case the output will be in the same location as inputPlan with '.upgraded' appended Lin Sun wrote: Hi David, How are we supposed to run the latest upgrade tool now that it is a module inside of Geronimo? I am able to see the upgraded plan from admin console, but I haven't been able to get the latest upgrade tool by itself running. What I did was: E:\geronimo-1.1-SNAPSHOT\binjava -jar client.jar geronimo/upgrade-cli/1.1-SNAPSHOT java.lang.IllegalArgumentException: Invalid id: geronimo/upgrade-cli/1.1-SNAPSHOT at org.apache.geronimo.kernel.repository.Artifact.create(Artifact.java:4 9) at org.apache.geronimo.system.main.ClientCommandLine.main(ClientCommandL ine.java:46) I also tried to execute deploy.bat start geronimo/upgrade/1.1-SNAPSHOT/car before it, but it didn't make any difference. Thanks, Lin -Original Message- From: David Jencks [mailto:[EMAIL PROTECTED] Sent: Monday, May 29, 2006 1:36 PM To: dev@geronimo.apache.org Subject: Re: Please try out the upgrade jar Toby, Thanks for pointing this out. I've fixed it in 1.1, will port to trunk soon. See http://issues.apache.org/jira/browse/GERONIMO-2068 thanks david jencks On May 26, 2006, at 3:29 PM, toby cabot wrote: David, Thanks for providing this tool, it's a big help. I had some problems on a test geronimo-application.xml file that includes some gbean references (for hooking up to security gbeans). The file looks like: = ?xml version=1.0 ? application xmlns=http://geronimo.apache.org/xml/ns/j2ee/ application configId=hello parentId=geronimo/j2ee-security/1.0.1-SNAPSHOT/car gbean name=hello-realm class=org.apache.geronimo.security.realm.GenericSecurityRealm attribute name=realmNamehello-realm/attribute reference name=LoginModuleConfiguration namehello-login-chain/name /reference reference name=ServerInfo gbean- namegeronimo.server:J2EEApplication=null,J2EEModule=geronimo/j2ee- system/1.0.1-SNAPSHOT/ car,J2EEServer=geronimo,j2eeType=GBean,name=ServerInfo/gbean-name /reference reference name=LoginService gbean- namegeronimo.server:J2EEApplication=null,J2EEModule=geronimo/j2ee- security/1.0.1-SNAPSHOT/ car,J2EEServer=geronimo,j2eeType=JaasLoginService,name=JaasLoginServic e/gbean-name /reference /gbean gbean name=hello-login-chain class=org.apache.geronimo.security.jaas.JaasLoginModuleUse attribute name=controlFlagREQUIRED/attribute reference name=LoginModule namehello-login/name /reference /gbean gbean name=hello-login class=org.apache.geronimo.security.jaas.LoginModuleGBean attribute name=loginModuleClassreva.common.auth.TrivialLoginModule/ attribute attribute name=serverSidetrue/attribute attribute name=options usersURI=var/security/demo_users.properties groupsURI=var/security/demo_groups.properties /attribute attribute name=loginDomainNamehello-realm/attribute /gbean /application = The problem seems to be the application/gbean/reference/gbean-name elements, as the error I get at offline deploy time looks like: Deployer operation failed: org.apache.xmlbeans.XmlException: Invalid deployment descriptor: [error: cvc-complex-type.2.4a: Expected elements '[EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ deployment-1.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ deployment-1.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ deployment-1.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ deployment-1.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ deployment-1.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ deployment-1.1' instead of '[EMAIL PROTECTED]://geronimo.apache.org/ xml/ns/deployment-1.1' here in element [EMAIL PROTECTED]:// geronimo.apache.org/xml/ns/deployment-1.1, error: cvc-complex-type. 2.4a: Expected elements '[EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ deployment-1.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ deployment-1.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ deployment-1.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ deployment-1.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ deployment-1.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ deployment-1.1' instead of '[EMAIL PROTECTED]://geronimo.apache.org/ xml/ns/deployment-1.1' here in element [EMAIL PROTECTED]:// geronimo.apache.org/xml/ns/deployment-1.1] Descriptor: xml-fragment
Re: Please try out the upgrade jar
Toby, Thanks for pointing this out. I've fixed it in 1.1, will port to trunk soon. See http://issues.apache.org/jira/browse/GERONIMO-2068 thanks david jencks On May 26, 2006, at 3:29 PM, toby cabot wrote: David, Thanks for providing this tool, it's a big help. I had some problems on a test geronimo-application.xml file that includes some gbean references (for hooking up to security gbeans). The file looks like: = ?xml version=1.0 ? application xmlns=http://geronimo.apache.org/xml/ns/j2ee/ application configId=hello parentId=geronimo/j2ee-security/1.0.1-SNAPSHOT/car gbean name=hello-realm class=org.apache.geronimo.security.realm.GenericSecurityRealm attribute name=realmNamehello-realm/attribute reference name=LoginModuleConfiguration namehello-login-chain/name /reference reference name=ServerInfo gbean- namegeronimo.server:J2EEApplication=null,J2EEModule=geronimo/j2ee- system/1.0.1-SNAPSHOT/ car,J2EEServer=geronimo,j2eeType=GBean,name=ServerInfo/gbean-name /reference reference name=LoginService gbean- namegeronimo.server:J2EEApplication=null,J2EEModule=geronimo/j2ee- security/1.0.1-SNAPSHOT/ car,J2EEServer=geronimo,j2eeType=JaasLoginService,name=JaasLoginServic e/gbean-name /reference /gbean gbean name=hello-login-chain class=org.apache.geronimo.security.jaas.JaasLoginModuleUse attribute name=controlFlagREQUIRED/attribute reference name=LoginModule namehello-login/name /reference /gbean gbean name=hello-login class=org.apache.geronimo.security.jaas.LoginModuleGBean attribute name=loginModuleClassreva.common.auth.TrivialLoginModule/ attribute attribute name=serverSidetrue/attribute attribute name=options usersURI=var/security/demo_users.properties groupsURI=var/security/demo_groups.properties /attribute attribute name=loginDomainNamehello-realm/attribute /gbean /application = The problem seems to be the application/gbean/reference/gbean-name elements, as the error I get at offline deploy time looks like: Deployer operation failed: org.apache.xmlbeans.XmlException: Invalid deployment descriptor: [error: cvc-complex-type.2.4a: Expected elements '[EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ deployment-1.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ deployment-1.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ deployment-1.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ deployment-1.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ deployment-1.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ deployment-1.1' instead of '[EMAIL PROTECTED]://geronimo.apache.org/ xml/ns/deployment-1.1' here in element [EMAIL PROTECTED]:// geronimo.apache.org/xml/ns/deployment-1.1, error: cvc-complex-type. 2.4a: Expected elements '[EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ deployment-1.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ deployment-1.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ deployment-1.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ deployment-1.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ deployment-1.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ deployment-1.1' instead of '[EMAIL PROTECTED]://geronimo.apache.org/ xml/ns/deployment-1.1' here in element [EMAIL PROTECTED]:// geronimo.apache.org/xml/ns/deployment-1.1] Descriptor: xml-fragment xmlns:dep=http://geronimo.apache.org/xml/ ns/deployment-1.1 dep:environment dep:moduleId dep:groupIddefault/dep:groupId dep:artifactIdhello/dep:artifactId dep:version1-default/dep:version dep:typecar/dep:type /dep:moduleId dep:dependencies dep:dependency dep:groupIdgeronimo/dep:groupId dep:artifactIdj2ee-security/dep:artifactId dep:version1.0.1-SNAPSHOT/dep:version dep:typecar/dep:type /dep:dependency /dep:dependencies dep:hidden-classes/ dep:non-overridable-classes/ /dep:environment dep:gbean name=hello-realm class=org.apache.geronimo.security.realm.GenericSecurityRealm dep:attribute name=realmNamehello-realm/dep:attribute dep:reference name=LoginModuleConfiguration dep:namehello-login-chain/dep:name /dep:reference dep:reference name=ServerInfo dep:gbean- namegeronimo.server:J2EEApplication=null,J2EEModule=geronimo/j2ee- system/1.0.1-SNAPSHOT/ car,J2EEServer=geronimo,j2eeType=GBean,name=ServerInfo/dep:gbean- name /dep:reference dep:reference name=LoginService dep:gbean- namegeronimo.server:J2EEApplication=null,J2EEModule=geronimo/j2ee- security/1.0.1-SNAPSHOT/ car,J2EEServer=geronimo,j2eeType=JaasLoginService,name=JaasLoginServic e/dep:gbean-name /dep:reference /dep:gbean dep:gbean name=hello-login-chain
Re: Please try out the upgrade jar
David, Thanks for providing this tool, it's a big help. I had some problems on a test geronimo-application.xml file that includes some gbean references (for hooking up to security gbeans). The file looks like: = ?xml version=1.0 ? application xmlns=http://geronimo.apache.org/xml/ns/j2ee/application; configId=hello parentId=geronimo/j2ee-security/1.0.1-SNAPSHOT/car gbean name=hello-realm class=org.apache.geronimo.security.realm.GenericSecurityRealm attribute name=realmNamehello-realm/attribute reference name=LoginModuleConfiguration namehello-login-chain/name /reference reference name=ServerInfo gbean-namegeronimo.server:J2EEApplication=null,J2EEModule=geronimo/j2ee-system/1.0.1-SNAPSHOT/car,J2EEServer=geronimo,j2eeType=GBean,name=ServerInfo/gbean-name /reference reference name=LoginService gbean-namegeronimo.server:J2EEApplication=null,J2EEModule=geronimo/j2ee-security/1.0.1-SNAPSHOT/car,J2EEServer=geronimo,j2eeType=JaasLoginService,name=JaasLoginService/gbean-name /reference /gbean gbean name=hello-login-chain class=org.apache.geronimo.security.jaas.JaasLoginModuleUse attribute name=controlFlagREQUIRED/attribute reference name=LoginModule namehello-login/name /reference /gbean gbean name=hello-login class=org.apache.geronimo.security.jaas.LoginModuleGBean attribute name=loginModuleClassreva.common.auth.TrivialLoginModule/attribute attribute name=serverSidetrue/attribute attribute name=options usersURI=var/security/demo_users.properties groupsURI=var/security/demo_groups.properties /attribute attribute name=loginDomainNamehello-realm/attribute /gbean /application = The problem seems to be the application/gbean/reference/gbean-name elements, as the error I get at offline deploy time looks like: Deployer operation failed: org.apache.xmlbeans.XmlException: Invalid deployment descriptor: [error: cvc-complex-type.2.4a: Expected elements '[EMAIL PROTECTED]://geronimo.apache.org/xml/ns/deployment-1.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/deployment-1.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/deployment-1.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/deployment-1.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/deployment-1.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/deployment-1.1' instead of '[EMAIL PROTECTED]://geronimo.apache.org/xml/ns/deployment-1.1' here in element [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/deployment-1.1, error: cvc-complex-type.2.4a: Expected elements '[EMAIL PROTECTED]://geronimo.apache.org/xml/ns/deployment-1.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/deployment-1.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/deployment-1.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/deployment-1.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/deployment-1.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/deployment-1.1' instead of '[EMAIL PROTECTED]://geronimo.apache.org/xml/ns/deployment-1.1' here in element [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/deployment-1.1] Descriptor: xml-fragment xmlns:dep=http://geronimo.apache.org/xml/ns/deployment-1.1; dep:environment dep:moduleId dep:groupIddefault/dep:groupId dep:artifactIdhello/dep:artifactId dep:version1-default/dep:version dep:typecar/dep:type /dep:moduleId dep:dependencies dep:dependency dep:groupIdgeronimo/dep:groupId dep:artifactIdj2ee-security/dep:artifactId dep:version1.0.1-SNAPSHOT/dep:version dep:typecar/dep:type /dep:dependency /dep:dependencies dep:hidden-classes/ dep:non-overridable-classes/ /dep:environment dep:gbean name=hello-realm class=org.apache.geronimo.security.realm.GenericSecurityRealm dep:attribute name=realmNamehello-realm/dep:attribute dep:reference name=LoginModuleConfiguration dep:namehello-login-chain/dep:name /dep:reference dep:reference name=ServerInfo dep:gbean-namegeronimo.server:J2EEApplication=null,J2EEModule=geronimo/j2ee-system/1.0.1-SNAPSHOT/car,J2EEServer=geronimo,j2eeType=GBean,name=ServerInfo/dep:gbean-name /dep:reference dep:reference name=LoginService dep:gbean-namegeronimo.server:J2EEApplication=null,J2EEModule=geronimo/j2ee-security/1.0.1-SNAPSHOT/car,J2EEServer=geronimo,j2eeType=JaasLoginService,name=JaasLoginService/dep:gbean-name /dep:reference /dep:gbean dep:gbean name=hello-login-chain class=org.apache.geronimo.security.jaas.JaasLoginModuleUse dep:attribute name=controlFlagREQUIRED/dep:attribute dep:reference name=LoginModule dep:namehello-login/dep:name /dep:reference /dep:gbean dep:gbean name=hello-login
Re: Please try out the upgrade jar
On 5/12/06, Paul McMahan [EMAIL PROTECTED] wrote: Also, I think you (or someone) mentioned earlier that it might be useful to make this utility available from the admin console. Seems like one reasonable approach would be to enable the current application deployment portlet to detect when a backlevel plan is provided (assuming that's always possible) and invoke your utility to provide a head start on creating a new plan. If there's consensus around that idea then I can help with the UI. I attached a patch to GERONIMO-2006 that implements this idea. When a deployment fails the console looks for a configId attribute in the plan and if found provides the user with a new plan generated by the upgrader. They can edit the upgraded plan in place and save it locally. In some cases (welcome app, jmx-debug, and others) the upgraded plan needs no further editing so the user can save the plan and then immediately deploy again from the same portlet. In some cases (daytrader) manual editing is required but the upgraded plan at least provides a starting place. Best wishes, Paul Paul On 5/12/06, David Jencks [EMAIL PROTECTED] wrote: I put the upgrade jar at http://people.apache.org/~djencks/geronimo-upgrade-1.1-SNAPSHOT.jar It would be very helpful to find out to what extent this works in real life. It's supposed to include all the classes it needs (that's why its so big) usage: java -jar geronimo-upgrade-1.1-SNAPSHOT.jar path to source plan [path to target plan] if you leave out the target, you'll get output in the same directory as the source. thanks david jencks
Re: Please try out the upgrade jar
I've also noticed another difference between the 1.0 and 1.1 deployment plans. Concerning the following xml: security-realm-namegeronimo-properties-realm/security-realm-name security default-principal principal name=anonymous class=org.apache.geronimo.security.realm.providers.GeronimoUserPrincipal/ /default-principal role-mappings role role-name=tomcat principal name=admin class=org.apache.geronimo.security.realm.providers.GeronimoGroupPrincipal/ /role /role-mappings /security IIRC, for *G1.0*, certain applications required this xml in order to deploy/start properly on Jetty. It was *not* required for Tomcat. For *G1.1*, it seems that these security settings are required for both Jetty and Tomcat. The point is that Jetty applications will migrate fine though Tomcat applications may now require these few additional lines of xml. Perhaps the Upgrade tool should account for this case.. Thanks -Dave- David Jencks wrote: Thanks for trying it out. I changed how it starts quite a bit today -- I hope it hasn't become too slow. I also think I fixed the schema issue Dave Colasurdo found. thanks david jencks On May 14, 2006, at 3:57 PM, Chris Cardona wrote: Hi David J., This is very helpful! So far it worked for the simple ejb, war, ear that I've tested. I'll let you know if I ran into problems deploying other modules. Dave Colasurdo, FYI, I tried upgrading my geronimo-web.xml and it was converted from: web-app xmlns=http://geronimo.apache.org/xml/ns/web; ... To: web-app xmlns=http://geronimo.apache.org/xml/ns/j2ee/web-1.1; ... Maybe the upgrade tool is not expecting: web-app xmlns=http://geronimo.apache.org/xml/ns/j2ee/web/tomcat-1.0; ... Not sure if this is a bug or that's the expected behavior. Chris --- Dave Colasurdo [EMAIL PROTECTED] wrote: Thanks David! It seems to run fine on the simple plans that I have tried though I do have a few quick comments and observations.. 1) Should the version in the schema name be updated (from 1.0 - 1.1) for both jetty and tomcat plans? For example, the following line is unchanged when the tool is run.. web-app xmlns=http://geronimo.apache.org/xml/ns/j2ee/web/tomcat-1.0; 2) When using a unicode file as input (on windows platform) the output file isn't created in unicode format. 3) On windows platform, it seems that CR (x'0D') is inserted on the end of every line.. This appears as a musical note in my editor :) -Dave- David Jencks wrote: I put the upgrade jar at http://people.apache.org/~djencks/geronimo-upgrade-1.1-SNAPSHOT.jar It would be very helpful to find out to what extent this works in real life. It's supposed to include all the classes it needs (that's why its so big) usage: java -jar geronimo-upgrade-1.1-SNAPSHOT.jar path to source plan [path to target plan] if you leave out the target, you'll get output in the same directory as the source. thanks david jencks __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Re: Please try out the upgrade jar
Hi David J., This is very helpful! So far it worked for the simple ejb, war, ear that I've tested. I'll let you know if I ran into problems deploying other modules. Dave Colasurdo, FYI, I tried upgrading my geronimo-web.xml and it was converted from: web-app xmlns=http://geronimo.apache.org/xml/ns/web; ... To: web-app xmlns=http://geronimo.apache.org/xml/ns/j2ee/web-1.1; ... Maybe the upgrade tool is not expecting: web-app xmlns=http://geronimo.apache.org/xml/ns/j2ee/web/tomcat-1.0; ... Not sure if this is a bug or that's the expected behavior. Chris --- Dave Colasurdo [EMAIL PROTECTED] wrote: Thanks David! It seems to run fine on the simple plans that I have tried though I do have a few quick comments and observations.. 1) Should the version in the schema name be updated (from 1.0 - 1.1) for both jetty and tomcat plans? For example, the following line is unchanged when the tool is run.. web-app xmlns=http://geronimo.apache.org/xml/ns/j2ee/web/tomcat-1.0; 2) When using a unicode file as input (on windows platform) the output file isn't created in unicode format. 3) On windows platform, it seems that CR (x'0D') is inserted on the end of every line.. This appears as a musical note in my editor :) -Dave- David Jencks wrote: I put the upgrade jar at http://people.apache.org/~djencks/geronimo-upgrade-1.1-SNAPSHOT.jar It would be very helpful to find out to what extent this works in real life. It's supposed to include all the classes it needs (that's why its so big) usage: java -jar geronimo-upgrade-1.1-SNAPSHOT.jar path to source plan [path to target plan] if you leave out the target, you'll get output in the same directory as the source. thanks david jencks __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Re: Please try out the upgrade jar
Thanks for trying it out. I changed how it starts quite a bit today -- I hope it hasn't become too slow. I also think I fixed the schema issue Dave Colasurdo found. thanks david jencks On May 14, 2006, at 3:57 PM, Chris Cardona wrote: Hi David J., This is very helpful! So far it worked for the simple ejb, war, ear that I've tested. I'll let you know if I ran into problems deploying other modules. Dave Colasurdo, FYI, I tried upgrading my geronimo-web.xml and it was converted from: web-app xmlns=http://geronimo.apache.org/xml/ns/web; ... To: web-app xmlns=http://geronimo.apache.org/xml/ns/j2ee/web-1.1; ... Maybe the upgrade tool is not expecting: web-app xmlns=http://geronimo.apache.org/xml/ns/j2ee/web/tomcat-1.0; ... Not sure if this is a bug or that's the expected behavior. Chris --- Dave Colasurdo [EMAIL PROTECTED] wrote: Thanks David! It seems to run fine on the simple plans that I have tried though I do have a few quick comments and observations.. 1) Should the version in the schema name be updated (from 1.0 - 1.1) for both jetty and tomcat plans? For example, the following line is unchanged when the tool is run.. web-app xmlns=http://geronimo.apache.org/xml/ns/j2ee/web/tomcat-1.0; 2) When using a unicode file as input (on windows platform) the output file isn't created in unicode format. 3) On windows platform, it seems that CR (x'0D') is inserted on the end of every line.. This appears as a musical note in my editor :) -Dave- David Jencks wrote: I put the upgrade jar at http://people.apache.org/~djencks/geronimo-upgrade-1.1-SNAPSHOT.jar It would be very helpful to find out to what extent this works in real life. It's supposed to include all the classes it needs (that's why its so big) usage: java -jar geronimo-upgrade-1.1-SNAPSHOT.jar path to source plan [path to target plan] if you leave out the target, you'll get output in the same directory as the source. thanks david jencks __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Re: Please try out the upgrade jar
Thanks David! It seems to run fine on the simple plans that I have tried though I do have a few quick comments and observations.. 1) Should the version in the schema name be updated (from 1.0 - 1.1) for both jetty and tomcat plans? For example, the following line is unchanged when the tool is run.. web-app xmlns=http://geronimo.apache.org/xml/ns/j2ee/web/tomcat-1.0; 2) When using a unicode file as input (on windows platform) the output file isn't created in unicode format. 3) On windows platform, it seems that CR (x'0D') is inserted on the end of every line.. This appears as a musical note in my editor :) -Dave- David Jencks wrote: I put the upgrade jar at http://people.apache.org/~djencks/geronimo-upgrade-1.1-SNAPSHOT.jar It would be very helpful to find out to what extent this works in real life. It's supposed to include all the classes it needs (that's why its so big) usage: java -jar geronimo-upgrade-1.1-SNAPSHOT.jar path to source plan [path to target plan] if you leave out the target, you'll get output in the same directory as the source. thanks david jencks
