Aaron Mulder wrote:
>
> Call it a personal weakness, but I tend to override all my JNDI
> names with a "Home" on the end so the code looks like
>
> FooHome home = (FooHome)ctx.lookup("FooHome");
> Foo foo = home.create();
>
> instead of
>
> FooHome home = (FooHome)ctx.lookup("Foo");
> Foo foo = home.create();
That's ok. Simply set the EJB name of the bean to "FooHome" then. Or do
you want to call the bean "Foo"? If so, can you please tell me
1) why suffix with Home? (Add same info everywhere=no valuable info)
2) why would it be bad to use "FooHome" in both places?
> But I suppose the JNDI name overriding wouldn't be portable across
> servers, so perhaps it's better in the long run if jBoss doesn't allow it.
Oh, wll, that's not the issue really. This is deployment information, so
either way would *work*. It's just that in one case you would simply
prefix all bean names with "myapp" (i.e. full name=prefix + EJB-name),
whereas in the more "flexible" way you would have to give full names for
every bean, which is more work to be done, and more places to mess
things up.
I would prefer the "prefix with app name" way of doing things.
/Rickard
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
