> is this documented anywhere? kinda threw me for a loop.
[Schlienger, Marc] I saw this documented somewhere, I believe it
was in the workbook (downloadable from www.titan-books.com) associated with
the Enterprise JavaBeans book from Richard Monson-Haefel.
> btw, what does COMP_NAME stand for?
[Schlienger, Marc] it stands for default JNDI environment naming
context. This default context is located in the namespace called
"java:comp/env" and in its childs directories. All EJBs are mapped to
java:comp/env/ejb.
This allows for a standard and portable deployment of the beans.
The problem is that JBoss does not currently support this, that's
why we use JNDI_NAME.
> i understand JNDI_NAME (physical), but
> is COMP_NAME (logical) used for in-vm (local) calls?
>
> also, 1) is there a place to specify this preference to use the physical,
> JNDI_NAME in ejbdoclet's utilobject subtask,
[Schlienger, Marc] I don't know, if you find it, please let me
know.
> or 2) have ejbdoclet
> automatically determine if the jboss subtask is included, and if so, have
> the template generate:
>
> java.lang.Object objRef =
> initialContext.lookup(NameHome.JNDI_NAME);
>
> ^^^^^^^^^^^^^
> instead of
>
> java.lang.Object objRef =
> initialContext.lookup(NameHome.COMP_NAME);
>
>
> inside the getHome() methods in the xxxUtil class?
[Schlienger, Marc] would be nice, but restricted to the current
JBoss implementation that does not support COMP_NAME.
Regards,
Marc
-------------------------------------------------------
This SF.net email is sponsored by: Get the new Palm Tungsten T
handheld. Power & Color in a compact size!
http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0002en
_______________________________________________
Xdoclet-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-user
