Return-Path: Delivered-To: apmail-geronimo-user-archive@www.apache.org Received: (qmail 939 invoked from network); 27 Feb 2008 19:03:48 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 27 Feb 2008 19:03:48 -0000 Received: (qmail 86600 invoked by uid 500); 27 Feb 2008 19:03:21 -0000 Delivered-To: apmail-geronimo-user-archive@geronimo.apache.org Received: (qmail 86562 invoked by uid 500); 27 Feb 2008 19:03:21 -0000 Mailing-List: contact user-help@geronimo.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: user@geronimo.apache.org List-Id: Delivered-To: mailing list user@geronimo.apache.org Received: (qmail 86537 invoked by uid 99); 27 Feb 2008 19:03:21 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 27 Feb 2008 11:03:21 -0800 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of jaw981@gmail.com designates 209.85.142.189 as permitted sender) Received: from [209.85.142.189] (HELO ti-out-0910.google.com) (209.85.142.189) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 27 Feb 2008 19:02:45 +0000 Received: by ti-out-0910.google.com with SMTP id b8so2268513tic.1 for ; Wed, 27 Feb 2008 11:02:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; bh=pDxzEUuA1lTsqf1T35arUQJCagNpKvri5PrN1PGjplo=; b=MpbIVt8D5m2i6RpoZxbRzk0NjhQYdyBs7VKRpWhnoJPGbPDyvqylxEGviVfBvKKxgsUQyMJeJprBbO936WE0AkcZzEEuRlmt5KyXAov/BdETFdkXWQgkkFAahCUdTSrX/6+AYDUAkxvjg2OjtiDfUCEDdnhcD3Y5RIncmTk1Yo4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=wGd0jQJJ9RMLUTg7OJsGrf3z3mlVetb1tnGrxi2M+R4fDF8BrzOW3q94HnwWYy1Y4hP1/dOsOjXAlvu8INHNbEJojqaIaXYtI06WC2RHSTZGw1ZQ1D/VIWcBvTAH2ErTI8OnMmy8UiE0ReX6YBT0OhpcVF4Lpp0UnCLyxKfIRj8= Received: by 10.150.95.20 with SMTP id s20mr2447311ybb.58.1204138970895; Wed, 27 Feb 2008 11:02:50 -0800 (PST) Received: by 10.150.138.3 with HTTP; Wed, 27 Feb 2008 11:02:50 -0800 (PST) Message-ID: <73a75e430802271102o35b5564crec3bae3ad033f145@mail.gmail.com> Date: Wed, 27 Feb 2008 14:02:50 -0500 From: "Jason Warner" To: user@geronimo.apache.org Subject: Re: Geronimo 1.1 to 2.1/ J2EE to JEE(5) In-Reply-To: <73a75e430802270836w3129b162w17e4ae749d2f8318@mail.gmail.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_5280_30189815.1204138970882" References: <20080227073039.181451e9c2a7ebbcd6ae28cea81146c8.99341e6b11.wbe@email.secureserver.net> <73a75e430802270836w3129b162w17e4ae749d2f8318@mail.gmail.com> X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_5280_30189815.1204138970882 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline 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 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 > 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 > > > 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 > > > Mark@Aufdencamp.com > > > > > > > -- > ~Jason Warner -- ~Jason Warner ------=_Part_5280_30189815.1204138970882 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline 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 <jaw981@gmail.com> 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.1 rather than web-2.0 which is required for 2.0. 

On Wed, Feb 27, 2008 at 9:30 AM, Mark Aufdencamp <mark@aufdencamp.com> 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 <mark@aufdencamp.com>
> 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
> Mark@Aufdencamp.com




--
~Jason Warner



--
~Jason Warner ------=_Part_5280_30189815.1204138970882--