- 
        1. Re: Migrating EJB3 Code from 4.2 to 5.0 and encountering [Jjriley Jan 20, 2009 5:08 PM (in response to jriley)Opps ... with two different interfaces it is working 
- 
        2. Re: Migrating EJB3 Code from 4.2 to 5.0 and encountering [Jalrubinger Jan 20, 2009 7:56 PM (in response to jriley)Looks like the forum software chopped off the JIRA issue from your topic. 
 What was the error? There's nothing wrong with that construct assuming:
 * There's no @Local or @Remote annotation on EchoService
 * EchoServiceRemote does not also extend from EJBObject
 * EchoServiceLocal does not also extend from EJBLocalObject
 S,
 ALR
- 
        3. Re: Migrating EJB3 Code from 4.2 to 5.0 and encountering [Jjriley Jan 21, 2009 10:31 AM (in response to jriley)I actually found the problem. It was caused by my ejb-jar.xml entries 
 My entries were something like this:<?xml version="1.0" encoding="UTF-8"?> <ejb-jar version="3.0"> <enterprise-beans> <session> <ejb-name>PropertyService</ejb-name> <remote>com.emageon.properties.service.PropertyService</remote> <ejb-class> com.emageon.properties.service.ejb.PropertyServiceBean </ejb-class> <session-type>Stateless</session-type> <transaction-type>Container</transaction-type> </session> </enterprise-beans> </ejb-jar> 
 The tags need to be changed to <business-remote>. Here is the corrected content.<?xml version="1.0" encoding="UTF-8"?> <ejb-jar version="3.0"> <enterprise-beans> <session> <ejb-name>PropertyService</ejb-name> <business-remote>com.emageon.properties.service.PropertyService</business-remote> <ejb-class> com.emageon.properties.service.ejb.PropertyServiceBean </ejb-class> <session-type>Stateless</session-type> <transaction-type>Container</transaction-type> </session> </enterprise-beans> </ejb-jar> 
- 
        4. Re: Migrating EJB3 Code from 4.2 to 5.0 and encountering [Jjriley Jan 21, 2009 10:40 AM (in response to jriley)Sorry. This post has ended up a little confusing. 
 [JBMETA-130] Was the error I got when trying to get EJB3 Session beans migrated from 4.2.x to 5.0.0 GA. In my case I was NOT trying to be EJB2.x compliant.
 If you have this problem, check these items:
 1. Make sure @Local and @Remote use a different interface.
 2. Make sure any beans referenced in ebj-jar.xml file use the <business-remote> tag instead of the and use <business-local> instead of
- 
        5. Re: Migrating EJB3 Code from 4.2 to 5.0 and encountering [Jalrubinger Jan 21, 2009 12:36 PM (in response to jriley)Yep. 
 * @Remote references a business interface (EJB 3.x View)
 * is a Remote Component interface (extends EJBObject, an EJB 2.x View)
 * <business-remote> is the XML equivalent to @Remote
 * There is no annotation for , we read it in via the return types of @Home create methods.
 S,
 ALR
 
    