OpenEJB tries to parse sun-ejb-jar.xml

• Key: GERONIMO-4573
• Type: Bug
• Status: Closed
• Resolution: Fixed
• Priority: Major
• Assignee: Unassigned
• Reporter: Fredrik Jonson
• Component/s: OpenEJB
• Affects Version/s: 2.1.3
• Fix Version/s: 2.1.4

Description

I'm trying to create an application with a inbound rar connector implementation, and have the ear deploy properly on both Geronimo and Glassfish 2.1. To solve that I declare my resource adapter reference both in a openejb-jar.xml for the geronimo specific configuration and a sun-ejb-jar.xml for the glassfish specific configuration.

This solution works on glassfish, it ignores openejb-jar.xml as intended. In geronimo, openejb seems to pick up and try to parse the sun-ejb-jar.xml even though the ejb module also contains both a ejb-jar.xml and openejb-jar.xml.

Since sun-ejb-jar.xml is application server specific for Sun/Glassfish I expect Geronimo to stay away from it entirely.

This issue has been raised before, but I could not find anything relevant in jira. Check the following mail note:
http://marc.info/?l=geronimo-dev&m=118857105323864

Comments

[Fredrik Jonson]

I've created a simplistic patch for openejb 3.0.x, and tested it successfully on geronimo 2.1.3, by replacing the openejb-core jar with a patched one. The patch is attached to OPENEJB-1006.

[Fredrik Jonson]

I can confirm that the solution in OPENEJB-1006 has resolved this issue too. When I replace the openejb-core snapshot jar with the latest release candidate in the repository of a geronimo 2.1.4-SNAPSHOT, and use the following environment setting:

JAVA_OPTS=-Dopenejb.vendor.config=GERONIMO

I no longer see the deployment failure caused by the existence of a sun-ejb-jar.xml in my ejb module.