Dain and David...
Took a swag at deploying Daytrader on Geronimo 2.0-M2... During deployment, it complained about the openejb-jar.xml file missing from the EJB module. I added the one you provided earlier in this chain, but for some reason it is still complaining that the openejb-jar.xml file is missing from the EJB module. I think Matt is probably running into the same issue...
Does the or-mapping file also need to go in the ear/jar somewhere? Should this work on M2? Is there anything else that needs to go into the jar/ear?
It really seems to me like we need way too many extra xml files to deploy this thing.
I just fix that allows nested openejb plans to work correctly. This
was a big problem in the tck since all plans use the nested model.
On Feb 6, 2007, at 9:10 PM, Dain Sundstrom wrote:
> OK, I think the conversion tool should be full working now.
> There were loads of tiny bugs causing deployments to fail
> especially around cmp. I tested the converter with the OpenEJB2
> itests which use almost every feature of OpenEJB2 and the
> application now deploys with out error now. Of course there are
> things sill unimplemented or ported to 3, so if you try to use
> those features, you will get an exception at runtime.
> Let us know if you find any problems with the converter.
> On Feb 6, 2007, at 9:57 AM, Dain Sundstrom wrote:
>> On Feb 6, 2007, at 6:37 AM, David Blevins wrote:
>>> Haven't been able to get a full deploy of anything (tried
>>> daytrader and the v2 itests), but things are starting to look
>>> good with the converter. The basic conversion is happening and
>>> conversion of things like environment and abstract name queries
>>> are definitely getting ported over. Still see some hiccups in
>>> CMPs, but apps without CMPs may deploy just fine. Will look into
>>> it more when I get up.
>>> Dain, can you take a look at the persistence unit part of the
>>> rewritten EjbModuleBuilder. Seems something in the way i've
>>> reworked the code results in those not coming through so well.
>> Looking at it now.