How do I migrate ejb2 stateless session beans to ejb3 piecemeal?

I'm going to have a crack at answering my own question as I go along Here's how I got through it.

I'm going to have a crack at answering my own question as I go along. Here's how I got through it The following xml files used to have doctypes, but must now have namespaces: myApp. Ear/META-INF/application.

Xml myApp. Ear/web. War/WEB-INF/web.

Xml myApp. Ear/ejb. Jar/META-INF/ejb-jar.

Xml The following changes have been made to web. Xml taglib elements are now under a jsp-config element the display-name element has been removed from filter elements and servlet elements Remove myApp. Ear/ejb.

Jar/META-INF/ibm-ejb-jar-bnd. Xmi JNDI lookups change all your local ejb jndi lookups to use ejblocal:classname I also removed my jdbc resource ref from ejb-jar. Xml mappings and am using a global lookup instead The security problem I was having was because I removed ibm-application-bnd.

Xmi where it binds users and groups to roles.

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 Jun 16 '09 at 2:14.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.