[jboss-user] [EJB 3.0] New message: "Why EJB 2.0 TO EJB 3.0 migration?"

pravu Mi do-not-reply at jboss.com
Thu Jan 21 04:54:54 EST 2010


User development,

A new message was posted in the thread "Why EJB 2.0 TO EJB 3.0 migration?":

http://community.jboss.org/message/521301#521301

Author  : pravu Mi
Profile : http://community.jboss.org/people/pravumishra

Message:
--------------------------------------------------------------
Hi There,
 
The latest JBoss supports both EJB 2.0 and EJB 3.0. Guess existance of both the type of beans in a single EAR problem does not create any problem and it it works.
 
I have many modules those are developed by using EJB 2.0 and many new modules developed by using ejb 3.0. Instead of modifying( migrating) the EJB 2.0 code to ejb 3.0 I wanted to integrate all the modules in a single EAR file.
 
After placing all the modules into single EAR file, I foound the Screens those uses EJB 3.0 works fine and for EJB 2.0 it says  javax.naming.NameNotFoundException: Bean not bound
 
>From the defined 2.0 JNDI name it is not able to get the object. Is the declaration of JNDI names and bean mapping for 2.0 is useless in case we use both type of beans(2.0 and 3.0) in a single EAR?
 
It looks like there is some declaration missing in any of the configuration file.

Can any body let me know how to make it work.

Thanks and Regards,
Pravu Mishra.

--------------------------------------------------------------

To reply to this message visit the message page: http://community.jboss.org/message/521301#521301




More information about the jboss-user mailing list