[jira] Updated: (OPENEJB-1374) Compatibility between Jboss and OpenEJB JNDI names and CMP configurations

["Yuri Makhno (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/OPENEJB-1374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Yuri Makhno updated OPENEJB-1374:
---------------------------------

    Attachment: openejb-jboss.zip

> Compatibility between Jboss and OpenEJB JNDI names and CMP configurations
> -------------------------------------------------------------------------
>
>                 Key: OPENEJB-1374
>                 URL: https://issues.apache.org/jira/browse/OPENEJB-1374
>             Project: OpenEJB
>          Issue Type: Improvement
>          Components: deployment
>            Reporter: Yuri Makhno
>         Attachments: openejb-jboss.zip
>
>
> Our company uses Jboss in production and OpenEjb for unit testing. When we started adaptation of OpenEJb in our environment we had two main problems:
>  * OpenEjb and Jboss use different JNDI names for beans
>  * Jboss cmp beans can't be deployed with OpenEjb 
> After some investigation we decided to write JbossCompatibleInitialContextFactory which extends LocalInitialContextFactory and:
>  * supports @LocalBinding, @RemoteBinding, @RemoteBindings jboss ejb3 annotations
>  * translates jbosscmp-jdbc.xml to OpenEjb cmp beans format in runtime
>  * parses jboss.xml to find JNDI names for beans
>  * adds compatibility with Jboss JNDI names for datasources (like: "java:/PostgresDS", "java:jcr/local")
> I'm attaching implementation of JbossCompatibleInitialContextFactory as well as tests of the factory for ejb2 and ejb3 beans.
> We would be pleasure if our work will be helpful for you.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.