RE: Geronimo 1.1 to 2.1/ J2EE to JEE(5)
Feel free to! I'll test the information further per my other post on this thread. Original Message Subject: Re: Geronimo 1.1 to 2.1/ J2EE to JEE(5) From: Jason Warner [EMAIL PROTECTED] Date: Tue, February 26, 2008 8:49 pm To: user@geronimo.apache.org, [EMAIL PROTECTED] Mark, I've been working on putting together some migration documentation for 2.1. This seems like great information for these documents. Would you mind if I included it? On Tue, Feb 26, 2008 at 6:02 PM, Jacek Laskowski [EMAIL PROTECTED] wrote: On Tue, Feb 26, 2008 at 12:00 PM, Mark Aufdencamp [EMAIL PROTECTED] wrote: To port a J2EE Enterprise Application from Geronimo 1.1 to a JEE(5) Enterprise Application on Geronimo 2.0/2.1 Does it mean that without these changes one would not be able to migrate an ear from Geronimo 1.1 to Geronimo 2.1? What will happen when you don't apply the changes to the dds? Jacek -- Jacek Laskowski http://www.JacekLaskowski.pl -- ~Jason Warner
RE: Geronimo 1.1 to 2.1/ J2EE to JEE(5)
I developed on a Windows XP workstation in Eclipse 3.2 with Geronimo 1.1.1. I deployed a clean Eclipse Europa 3.3 and Geronimo-Tomcat6- 2.0.1 environment on an Ubuntu workstation. I then checked out my EAR Project, EJB Project, and WEB Projects from my subversion repository. The initial attempt to deploy tossed a deployment exception with some versioning messages. I'll try it again with 2.1 before the beginning of next week and follow up to the list. I'll report the results straight out of subversion and with my proposed deployment descriptor modifications. I'm fairly confident that the Tomcat component will be backward compatible. (Large user base) My greatest potential concern is with changes to the EJB project. Can anyone say for certain that they've deployed and tested an EJB 2.1 project on Geronimo 2.0/2.1 ? What kind of regression tests exists for backward compatibility in the code base? I guess I should check out the source and start looking at the code instead of being a binary user:) (BIG Thank You to those that compile the binaries for the rest of us users!) Does the JEE TCK include the J2EE TCK as a subset to test backward compatibility? Just curious and not pressed to get on Geronimo 2.1. I would like to start playing with an EJB 3.0 model branch moving forward with my applications back end code. Has anyone developed/deployed an EAR with a EJB 2.1 Project and a EJB 3.0 Project component? Thanks to all for the 411 Original Message Subject: Geronimo 1.1 to 2.1/ J2EE to JEE(5) From: Mark Aufdencamp [EMAIL PROTECTED] Date: Tue, February 26, 2008 3:00 pm To: user@geronimo.apache.org As I a haven't seen this specifically identified, I thought I'd outline my thoughts and have them confirmed. Everyones comments are appreciated I'm presuming no required changes to the codebase. The only requirement to port a J2EE Geronimo 1.1 Enterprise Application to run as a JEE Geronimo 2.0/2.1 Enterprise Application are changes to the Application Server specific deployment descriptors. I don't for see problems with the EAR or WAR's, but have my concerns about the EJB's. My understanding is that EJB 2.1 is required to function as a part of the JEE spec. Read: You don't have to port from EJB 2.1 to EJB 3.0, although there are significant advantages to the new JPA technology. To port a J2EE Enterprise Application from Geronimo 1.1 to a JEE(5) Enterprise Application on Geronimo 2.0/2.1 EAR Project Definition application.xml xmlns=http://java.sun.com/xml/ns/j2ee; No Changes Required geronimo-application.xml xmlns=http://geronimo.apache.org/xml/ns/j2ee/application-1.1; becomes xmlns=http://geronimo.apache.org/xml/ns/j2ee/application-2.0; EJB Project Definition ejb-jar.xml No Changes Required openejb-jar.xml xmlns=http://www.openejb.org/xml/ns/openejb-jar-2.1; xmlns:nam=http://geronimo.apache.org/xml/ns/naming-1.1; xmlns:pkgen=http://www.openejb.org/xml/ns/pkgen-2.0; xmlns:sec=http://geronimo.apache.org/xml/ns/security-1.1; xmlns:sys=http://geronimo.apache.org/xml/ns/deployment-1.1; becomes xmlns=http://www.openejb.org/xml/ns/openejb-jar-2.1; xmlns:nam=http://geronimo.apache.org/xml/ns/naming-1.2; xmlns:pkgen=http://www.openejb.org/xml/ns/pkgen-2.0; xmlns:sec=http://geronimo.apache.org/xml/ns/security-2.0; xmlns:sys=http://geronimo.apache.org/xml/ns/deployment-1.2; WebApp Project Definition web.xml No Change Required geronimo-web.xml xmlns=http://geronimo.apache.org/xml/ns/j2ee/web-1.1; becomes xmlns=http://geronimo.apache.org/xml/ns/j2ee/web-2.0; Hope this helps others! TIA, Mark Aufdencamp [EMAIL PROTECTED]
Re: Geronimo 1.1 to 2.1/ J2EE to JEE(5)
Mark, I went ahead and added that wiki page. It can be found here : http://cwiki.apache.org/confluence/display/GMOxDOC21/Deployment+descriptor+changes+for+going+from+G+1.1+to+G+2.1 Please let me know if you see anything that you'd like changed or added. One thing I should note is that Geronimo 2.1 actually requires a general web application xmlns of http://geronimo.apache.org/xml/ns/j2ee/web-2.0.1 rather than web-2.0 which is required for 2.0. On Wed, Feb 27, 2008 at 9:30 AM, Mark Aufdencamp [EMAIL PROTECTED] wrote: I developed on a Windows XP workstation in Eclipse 3.2 with Geronimo 1.1.1. I deployed a clean Eclipse Europa 3.3 and Geronimo-Tomcat6- 2.0.1 environment on an Ubuntu workstation. I then checked out my EAR Project, EJB Project, and WEB Projects from my subversion repository. The initial attempt to deploy tossed a deployment exception with some versioning messages. I'll try it again with 2.1 before the beginning of next week and follow up to the list. I'll report the results straight out of subversion and with my proposed deployment descriptor modifications. I'm fairly confident that the Tomcat component will be backward compatible. (Large user base) My greatest potential concern is with changes to the EJB project. Can anyone say for certain that they've deployed and tested an EJB 2.1 project on Geronimo 2.0/2.1 ? What kind of regression tests exists for backward compatibility in the code base? I guess I should check out the source and start looking at the code instead of being a binary user:) (BIG Thank You to those that compile the binaries for the rest of us users!) Does the JEE TCK include the J2EE TCK as a subset to test backward compatibility? Just curious and not pressed to get on Geronimo 2.1. I would like to start playing with an EJB 3.0 model branch moving forward with my applications back end code. Has anyone developed/deployed an EAR with a EJB 2.1 Project and a EJB 3.0 Project component? Thanks to all for the 411 Original Message Subject: Geronimo 1.1 to 2.1/ J2EE to JEE(5) From: Mark Aufdencamp [EMAIL PROTECTED] Date: Tue, February 26, 2008 3:00 pm To: user@geronimo.apache.org As I a haven't seen this specifically identified, I thought I'd outline my thoughts and have them confirmed. Everyones comments are appreciated I'm presuming no required changes to the codebase. The only requirement to port a J2EE Geronimo 1.1 Enterprise Application to run as a JEE Geronimo 2.0/2.1 Enterprise Application are changes to the Application Server specific deployment descriptors. I don't for see problems with the EAR or WAR's, but have my concerns about the EJB's. My understanding is that EJB 2.1 is required to function as a part of the JEE spec. Read: You don't have to port from EJB 2.1 to EJB 3.0, although there are significant advantages to the new JPA technology. To port a J2EE Enterprise Application from Geronimo 1.1 to a JEE(5) Enterprise Application on Geronimo 2.0/2.1 EAR Project Definition application.xml xmlns=http://java.sun.com/xml/ns/j2ee; No Changes Required geronimo-application.xml xmlns=http://geronimo.apache.org/xml/ns/j2ee/application-1.1; becomes xmlns=http://geronimo.apache.org/xml/ns/j2ee/application-2.0; EJB Project Definition ejb-jar.xml No Changes Required openejb-jar.xml xmlns=http://www.openejb.org/xml/ns/openejb-jar-2.1; xmlns:nam=http://geronimo.apache.org/xml/ns/naming-1.1; xmlns:pkgen=http://www.openejb.org/xml/ns/pkgen-2.0; xmlns:sec=http://geronimo.apache.org/xml/ns/security-1.1; xmlns:sys=http://geronimo.apache.org/xml/ns/deployment-1.1; becomes xmlns=http://www.openejb.org/xml/ns/openejb-jar-2.1; xmlns:nam=http://geronimo.apache.org/xml/ns/naming-1.2; xmlns:pkgen=http://www.openejb.org/xml/ns/pkgen-2.0; xmlns:sec=http://geronimo.apache.org/xml/ns/security-2.0; xmlns:sys=http://geronimo.apache.org/xml/ns/deployment-1.2; WebApp Project Definition web.xml No Change Required geronimo-web.xml xmlns=http://geronimo.apache.org/xml/ns/j2ee/web-1.1; becomes xmlns=http://geronimo.apache.org/xml/ns/j2ee/web-2.0; Hope this helps others! TIA, Mark Aufdencamp [EMAIL PROTECTED] -- ~Jason Warner
Re: Geronimo 1.1 to 2.1/ J2EE to JEE(5)
I used the wrong link there. The proper link should be this one:
http://cwiki.apache.org/GMOxDOC21/deployment-descriptor-changes-for-going-from-g-11-to-g-21.html
On Wed, Feb 27, 2008 at 11:36 AM, Jason Warner [EMAIL PROTECTED] wrote:
Mark,
I went ahead and added that wiki page. It can be found here :
http://cwiki.apache.org/confluence/display/GMOxDOC21/Deployment+descriptor+changes+for+going+from+G+1.1+to+G+2.1
Please let me know if you see anything that you'd like changed or added.
One thing I should note is that Geronimo 2.1 actually requires a general
web application xmlns of
http://geronimo.apache.org/xml/ns/j2ee/web-2.0.1rather than
web-2.0 which is required for 2.0.
On Wed, Feb 27, 2008 at 9:30 AM, Mark Aufdencamp [EMAIL PROTECTED]
wrote:
I developed on a Windows XP workstation in Eclipse 3.2 with Geronimo
1.1.1. I deployed a clean Eclipse Europa 3.3 and Geronimo-Tomcat6-
2.0.1 environment on an Ubuntu workstation. I then checked out my EAR
Project, EJB Project, and WEB Projects from my subversion repository.
The initial attempt to deploy tossed a deployment exception with some
versioning messages.
I'll try it again with 2.1 before the beginning of next week and follow
up to the list. I'll report the results straight out of subversion and
with my proposed deployment descriptor modifications.
I'm fairly confident that the Tomcat component will be backward
compatible. (Large user base) My greatest potential concern is with
changes to the EJB project.
Can anyone say for certain that they've deployed and tested an EJB 2.1
project on Geronimo 2.0/2.1 ?
What kind of regression tests exists for backward compatibility in the
code base? I guess I should check out the source and start looking at
the code instead of being a binary user:) (BIG Thank You to those that
compile the binaries for the rest of us users!)
Does the JEE TCK include the J2EE TCK as a subset to test backward
compatibility?
Just curious and not pressed to get on Geronimo 2.1. I would like to
start playing with an EJB 3.0 model branch moving forward with my
applications back end code.
Has anyone developed/deployed an EAR with a EJB 2.1 Project and a EJB
3.0 Project component?
Thanks to all for the 411
Original Message
Subject: Geronimo 1.1 to 2.1/ J2EE to JEE(5)
From: Mark Aufdencamp [EMAIL PROTECTED]
Date: Tue, February 26, 2008 3:00 pm
To: user@geronimo.apache.org
As I a haven't seen this specifically identified, I thought I'd
outline
my thoughts and have them confirmed. Everyones comments are
appreciated
I'm presuming no required changes to the codebase. The only
requirement
to port a J2EE Geronimo 1.1 Enterprise Application to run as a JEE
Geronimo 2.0/2.1 Enterprise Application are changes to the Application
Server specific deployment descriptors. I don't for see problems with
the EAR or WAR's, but have my concerns about the EJB's. My
understanding is that EJB 2.1 is required to function as a part of the
JEE spec. Read: You don't have to port from EJB 2.1 to EJB 3.0,
although there are significant advantages to the new JPA technology.
To port a J2EE Enterprise Application from Geronimo 1.1 to a JEE(5)
Enterprise Application on Geronimo 2.0/2.1
EAR Project Definition
application.xml
xmlns=http://java.sun.com/xml/ns/j2ee;
No Changes Required
geronimo-application.xml
xmlns=http://geronimo.apache.org/xml/ns/j2ee/application-1.1;
becomes
xmlns=http://geronimo.apache.org/xml/ns/j2ee/application-2.0;
EJB Project Definition
ejb-jar.xml
No Changes Required
openejb-jar.xml
xmlns=http://www.openejb.org/xml/ns/openejb-jar-2.1;
xmlns:nam=http://geronimo.apache.org/xml/ns/naming-1.1;
xmlns:pkgen=http://www.openejb.org/xml/ns/pkgen-2.0;
xmlns:sec=http://geronimo.apache.org/xml/ns/security-1.1;
xmlns:sys=http://geronimo.apache.org/xml/ns/deployment-1.1;
becomes
xmlns=http://www.openejb.org/xml/ns/openejb-jar-2.1;
xmlns:nam=http://geronimo.apache.org/xml/ns/naming-1.2;
xmlns:pkgen=http://www.openejb.org/xml/ns/pkgen-2.0;
xmlns:sec=http://geronimo.apache.org/xml/ns/security-2.0;
xmlns:sys=http://geronimo.apache.org/xml/ns/deployment-1.2;
WebApp Project Definition
web.xml
No Change Required
geronimo-web.xml
xmlns=http://geronimo.apache.org/xml/ns/j2ee/web-1.1;
becomes
xmlns=http://geronimo.apache.org/xml/ns/j2ee/web-2.0;
Hope this helps others!
TIA,
Mark Aufdencamp
[EMAIL PROTECTED]
--
~Jason Warner
--
~Jason Warner
Geronimo 1.1 to 2.1/ J2EE to JEE(5)
As I a haven't seen this specifically identified, I thought I'd outline my thoughts and have them confirmed. Everyones comments are appreciated I'm presuming no required changes to the codebase. The only requirement to port a J2EE Geronimo 1.1 Enterprise Application to run as a JEE Geronimo 2.0/2.1 Enterprise Application are changes to the Application Server specific deployment descriptors. I don't for see problems with the EAR or WAR's, but have my concerns about the EJB's. My understanding is that EJB 2.1 is required to function as a part of the JEE spec. Read: You don't have to port from EJB 2.1 to EJB 3.0, although there are significant advantages to the new JPA technology. To port a J2EE Enterprise Application from Geronimo 1.1 to a JEE(5) Enterprise Application on Geronimo 2.0/2.1 EAR Project Definition application.xml xmlns=http://java.sun.com/xml/ns/j2ee; No Changes Required geronimo-application.xml xmlns=http://geronimo.apache.org/xml/ns/j2ee/application-1.1; becomes xmlns=http://geronimo.apache.org/xml/ns/j2ee/application-2.0; EJB Project Definition ejb-jar.xml No Changes Required openejb-jar.xml xmlns=http://www.openejb.org/xml/ns/openejb-jar-2.1; xmlns:nam=http://geronimo.apache.org/xml/ns/naming-1.1; xmlns:pkgen=http://www.openejb.org/xml/ns/pkgen-2.0; xmlns:sec=http://geronimo.apache.org/xml/ns/security-1.1; xmlns:sys=http://geronimo.apache.org/xml/ns/deployment-1.1; becomes xmlns=http://www.openejb.org/xml/ns/openejb-jar-2.1; xmlns:nam=http://geronimo.apache.org/xml/ns/naming-1.2; xmlns:pkgen=http://www.openejb.org/xml/ns/pkgen-2.0; xmlns:sec=http://geronimo.apache.org/xml/ns/security-2.0; xmlns:sys=http://geronimo.apache.org/xml/ns/deployment-1.2; WebApp Project Definition web.xml No Change Required geronimo-web.xml xmlns=http://geronimo.apache.org/xml/ns/j2ee/web-1.1; becomes xmlns=http://geronimo.apache.org/xml/ns/j2ee/web-2.0; Hope this helps others! TIA, Mark Aufdencamp [EMAIL PROTECTED]
Re: Geronimo 1.1 to 2.1/ J2EE to JEE(5)
Great collection Mark, we'll make sure to add it to the 2.1 doc Thanks a bunch Cheers! Hernan Mark Aufdencamp wrote: As I a haven't seen this specifically identified, I thought I'd outline my thoughts and have them confirmed. Everyones comments are appreciated I'm presuming no required changes to the codebase. The only requirement to port a J2EE Geronimo 1.1 Enterprise Application to run as a JEE Geronimo 2.0/2.1 Enterprise Application are changes to the Application Server specific deployment descriptors. I don't for see problems with the EAR or WAR's, but have my concerns about the EJB's. My understanding is that EJB 2.1 is required to function as a part of the JEE spec. Read: You don't have to port from EJB 2.1 to EJB 3.0, although there are significant advantages to the new JPA technology. To port a J2EE Enterprise Application from Geronimo 1.1 to a JEE(5) Enterprise Application on Geronimo 2.0/2.1 EAR Project Definition application.xml xmlns=http://java.sun.com/xml/ns/j2ee; No Changes Required geronimo-application.xml xmlns=http://geronimo.apache.org/xml/ns/j2ee/application-1.1; becomes xmlns=http://geronimo.apache.org/xml/ns/j2ee/application-2.0; EJB Project Definition ejb-jar.xml No Changes Required openejb-jar.xml xmlns=http://www.openejb.org/xml/ns/openejb-jar-2.1; xmlns:nam=http://geronimo.apache.org/xml/ns/naming-1.1; xmlns:pkgen=http://www.openejb.org/xml/ns/pkgen-2.0; xmlns:sec=http://geronimo.apache.org/xml/ns/security-1.1; xmlns:sys=http://geronimo.apache.org/xml/ns/deployment-1.1; becomes xmlns=http://www.openejb.org/xml/ns/openejb-jar-2.1; xmlns:nam=http://geronimo.apache.org/xml/ns/naming-1.2; xmlns:pkgen=http://www.openejb.org/xml/ns/pkgen-2.0; xmlns:sec=http://geronimo.apache.org/xml/ns/security-2.0; xmlns:sys=http://geronimo.apache.org/xml/ns/deployment-1.2; WebApp Project Definition web.xml No Change Required geronimo-web.xml xmlns=http://geronimo.apache.org/xml/ns/j2ee/web-1.1; becomes xmlns=http://geronimo.apache.org/xml/ns/j2ee/web-2.0; Hope this helps others! TIA, Mark Aufdencamp [EMAIL PROTECTED]
Re: Geronimo 1.1 to 2.1/ J2EE to JEE(5)
On Tue, Feb 26, 2008 at 12:00 PM, Mark Aufdencamp [EMAIL PROTECTED] wrote: To port a J2EE Enterprise Application from Geronimo 1.1 to a JEE(5) Enterprise Application on Geronimo 2.0/2.1 Does it mean that without these changes one would not be able to migrate an ear from Geronimo 1.1 to Geronimo 2.1? What will happen when you don't apply the changes to the dds? Jacek -- Jacek Laskowski http://www.JacekLaskowski.pl
Re: Geronimo 1.1 to 2.1/ J2EE to JEE(5)
Mark, I've been working on putting together some migration documentation for 2.1. This seems like great information for these documents. Would you mind if I included it? On Tue, Feb 26, 2008 at 6:02 PM, Jacek Laskowski [EMAIL PROTECTED] wrote: On Tue, Feb 26, 2008 at 12:00 PM, Mark Aufdencamp [EMAIL PROTECTED] wrote: To port a J2EE Enterprise Application from Geronimo 1.1 to a JEE(5) Enterprise Application on Geronimo 2.0/2.1 Does it mean that without these changes one would not be able to migrate an ear from Geronimo 1.1 to Geronimo 2.1? What will happen when you don't apply the changes to the dds? Jacek -- Jacek Laskowski http://www.JacekLaskowski.pl -- ~Jason Warner
