Starting with the EJB3 feature pack, WAS has a new deployment option labeled 'Allow EJB reference targets to resolve automatically'. This allows EJB references to be automatically determined by the container, and the JNDI binding names don't have to be specified up front.

When MyEclipse Blue deploys an application with an EJB, this deployment property isn't set. As a result, I can't include a reference to an EJB3 bean. As it works now, the ejbdeploy script on WAS throws an error when you make a reference to an EJB3 bean and don't have that deployment option set. (I am trying to use this with JBoss Seam, see http://blog.hibernate.org/Bloggers/WebSphereRunningSeamsJEE5BookingExample for more info on this).

My only workaround at this point is to remove all of the EJB refs from web.xml during deployment, and then add them back manually after ejbdeploy runs. Can you add an option to set the 'Allow EJB reference targets to resolve automatically' during a deployment to WAS?

jx2dad,
Thanks for the heads up, I'll kick this back to the Blue team for evaluation.