On Jun 26, 2006, at 9:32 PM, Alan D. Cabrera wrote:
Can you explain in more detail the rearchitecture that was done in
this update? If this from openejb3 does that mean that we can
deprecate openejb3?
No, you misunderstand. Just about December/January/February OpenEJB
1 trunk and 2 trunk were realigned (2 more than 1), then both were
used as the basis for the openejb3 code which will deprecate all
prior openejb versions (finally!). The trick is Geronimo decided to
ditch it's trunk (1.2) around April and OpenEJB 2 and 3 are still
using it. In short this "patch" unscrews us :) It merges the old G
1.2 features back into new G 1.2 so we can restore OpenEJB 2.2 and
3.x will compile again.
-David
Regards,
Alan
Dain Sundstrom wrote:
I have finished the work to update the openejb dead-2.2 branch to
run with Geronimo 1.2. The dead-2.2 branch contains a major
rearchitecture of the OpenEJB container system which split the
deployment units from reusable container and this rearchitecture
has already been adopted in OpenEJB 3. This work was done in the
https://svn.apache.org/repos/asf/geronimo/branches/dain/
openejb-2.2-merge branch, and is largely composed of merges from
the Geronimo dead-1.2 branch.
A patch for this change can be found in GERONIMO-12345, but the
attached patch is not expected work perfectly. Any mismatches or
problems will be worked out during the final merge with trunk.
The best way to test this change is to checkout and build the
branch directly. The maven m:co goal should work to check out the
https://svn.codehaus.org/openejb/branches/dain-2.2-merge/merged
branch from openejb. For those with tck access, there is a dain-
openejb-2.2-merge branch available for testing the tck.
Please, review this quickly so the branch doesn't drift too much.
Thanks in advance,
-dain
A quick history of this branch follows:
417321 Fixed openejb version number in project.properties
---------------------------------------------------------------------
---
416533 Applied GERONIMO-1960 which verifies GBean references when
the final configuration data is created in a deployment context
416483 Fixed deployment plans to match newest openejb changes
---------------------------------------------------------------------
---
416428 Fixed more plans
---------------------------------------------------------------------
---
415721 Biggest change which updates the j2ee deployment context to
contain the transactionManager name amongst some smaller changes
---------------------------------------------------------------------
---
415720 Update maven.xml to use new openejb module names
---------------------------------------------------------------------
---
415225 Set svn:ignore on new interceptor module
---------------------------------------------------------------------
---
415224 svn merge -r 378403:378404 https://svn.apache.org/repos/asf/
geronimo/[EMAIL PROTECTED]
---------------------------------------------------------------------
---
415222 svn merge -r 378358:378359 https://svn.apache.org/repos/asf/
geronimo/[EMAIL PROTECTED]
---------------------------------------------------------------------
---
415220 svn merge -r 378346:378347 https://svn.apache.org/repos/asf/
geronimo/[EMAIL PROTECTED]
---------------------------------------------------------------------
---
415218 svn merge -r 378182:378183 https://svn.apache.org/repos/asf/
geronimo/[EMAIL PROTECTED]
---------------------------------------------------------------------
---
415217 svn merge -r 378161:378162 https://svn.apache.org/repos/asf/
geronimo/[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
