views:

1040

answers:

2

The EJB3 spec indicates that EJB2 and EJB3 can co-exist in a single application.

I wish to migrate my EJB2 stateless session beans to EJB3 stateless session beans.
This question does not relate to JPA at all (that is a separate piece of work to be carried out in the future)

I'm running on websphere 6.1 with the EJB3 feature pack installed and patched and the profile is augmented (an ejb3 sample app confirms that it works)

What changes do I need to make to my code, web.xml, application.xml, ejb-jar.xml and other websphere specific bindings to convert a SINGLE ejb from 2 to 3?

A: 

You need to put JEE xml namespaces in the three xml files you mentioned to start with. Then I think you remove your WAS binding files and use a different jndi lookup

That seems to get me some of the way, however now my ejb clients are being denied due to not having adequate roles. From the error message I can see it's picking up the correct username, but not mapping to the roles.It's using the FileRegistrySample that comes with websphere in my dev environment, and the same configuration worked fine with the old ejb2 setup.Have they done something different with authentication?
Travis Dixon
A: 
Travis Dixon