thanks Yura,
this is not jost about jndi prefix. take a look at this list :
JBOSS :: {jar file name}/{bean name}/{local or remote}
GLASSFISH :: ejb/{bean name}
WEBLOGIC :: {jar file name}_{bean name}_{remote or local interface name}
..
I solved this problem with one xml file for each app server
Hi Mohammad,
I have one suggestion to fix JNDI naming conventions on different servers.
In general if in your code you have:
InitialContext iniCtx = new InitialContext(props);
Context envCtx = (Context) iniCtx.lookup("java:comp/env");
I suggest you to expose constant "java:/comp/e
No, it doesn't about Tapestry.
its about my problems during migration from lightweight containers to the
Java EE standard world.
On Sat, Apr 12, 2008 at 11:27 AM, adasal <[EMAIL PROTECTED]> wrote:
> Your blog doesn't seem to be about Tapestry.
> I believe there are standards, but the standards
Your blog doesn't seem to be about Tapestry.
I believe there are standards, but the standards have boarders which may be
redefined as the standard evolves. What is inside the boarder will be
interoperable, What is outside is left to the implementer.
It is very possible to misunderstand the standard
