Hi,
I finally managed to fix the trunk of openejb to be able to do the
lookup of a trivial EJB3 stateless bean (I can't invoke methods
though... I receive the exception attached at the end of this email...
still investigating on it)
Now I notice that openejb uses different types of JndiNameStrategy to
assign names to deployed ejbs, so that my ejb, whose remote interface
is org.acme.Calculator, becomes CalculatorBusinessRemote bean on JNDI.
Is this behaviour correct?
With Glassfish, the ejb takes the simple name of its business
interface, but I didn't find a clear statement in the specification
about the correct naming of ejb...
--
Filippo (ejb3 invokation exception follows)
The bean instance null threw a system
exception:org.apache.xbean.recipe.MissingAccessorException: Unable to
create bean null attribute null: Unable to find a valid setter method:
public void
org.acme.CalculatorImpl.setSessionContext(org.apache.openejb.core.stateless.StatelessContext)
org.apache.xbean.recipe.MissingAccessorException: Unable to create
bean null attribute null: Unable to find a valid setter method: public
void
org.acme.CalculatorImpl.setSessionContext(org.apache.openejb.core.stateless.StatelessContext)
at org.apache.xbean.recipe.ObjectRecipe.findSetter(ObjectRecipe.java:599)
at org.apache.xbean.recipe.ObjectRecipe.create(ObjectRecipe.java:210)
at org.apache.xbean.recipe.ObjectRecipe.create(ObjectRecipe.java:154)
at
org.apache.openejb.core.stateless.StatelessInstanceManager.getInstance(StatelessInstanceManager.java:94)
at
org.apache.openejb.core.stateless.StatelessContainer.invoke(StatelessContainer.java:113)
