Have a few bean naming problems with ejb3 rc5

[ops]

Hi everyone,

has somebody answers to this questions? I use jboss 4.0.3sp1 and installed the ejb3rc5 package as documented in the readme. Then i started testing some ejb3 session beans. When I deployed my examples I faced some probs:
1) Usually a beans jndi-name should be automatically stored as package.BeanRemoteInterface. Jboss 3.0.1sp1 does so, but after the update to ejb3rc5 they have simply the name of the implementing bean class. I know about the @stateless(name) property, but I would like to use that automatic naming. What am I doing wrong?
2) If I use the @stateless(name) property, I still have to distinguish the interface type while doing my Client-Lookup:

ctx.lookup ( BeanInterface.class.getName() + "/remote" );

Even, if there is no local interface at all. And if I do a lookup without adding the "/remote"-String I do not always get the Local interface, only in serveral cases. Sometimes I have to add a "/local" to get my stub. Quite confusing!

Thanks for your help,

Oliver

[bill.burke]

look at the tutorial eamples. EJBNAME/remote

[ops]

Hi Bill,

It is clear to me, that I have to add the type of view ("remote" / "local"), but I don´t know the reason why. Most of the ejb 3 examples on the net do their lookup simply by

ctx.lookup ( BeanInterface.class.getName() );

and, as I said, this worked on the older versions of jboss. So is this a bug? Is it a jboss-only pattern to use? Will that change in the future?

Thanks for your help,

Oliver

[ejb3workshop]

Hi there,

It is not a bug. It is a feature added to allow to give the remote and local interfaces different names.
I had a brief look at the specification (PFD), but didn't find anything explicitly referring to the change. Maybe I must have another look. If anybody has more information where the specification specified /remote and /local I would be grateful for a pointer.

Tx
Alex
ejb3workshop.com

[cspada]

look at the tutorial eamples. EJBNAME/remote

Seems that with the new jboss4.0.4RC1 the lookup need to be
EAR File name withour .ear extension/BEAN NAME/remote

Why do all the binding start with the EAR name ??