check the JBoss log to see under what name your TestBMPEntity was bound at deployment, normally it will be something like
"test/TestBMPEntity" instead of "ejb/test/TestBMPEntity"
but you will find it in the server log
And then change your lookup accordingly.
Thanks, but I tried fiddling with the InitialContext lookup, and the only one that works is
That's the installed jndi name.
The returned object's findByPrimaryKey method works fine.
There's some so far undiscovered lookup in the JBoss 3 TestBMPEntity example's code that the server needs that is not being addressed by the XDoclet automatically generated deployment descriptors.
If anyone can get the sample TestBMPEntity's create method to work from a client app, I'd be happy to hear from them.
I fixed the problem. Thanks for the suggestion.
As suggested, it was a lookup problem. I changed the sample TestBMPEntityBean's generateUniqueId() lookup from "java:comp/env/ejb/test/SequenceGenerator" (not there) to "ejb/test/SequenceGenerator" (which has a JNDI name).