DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=4315>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=4315 EJB Access with weblogic.jar included: Can't access new InitialContext() ------- Additional Comments From [EMAIL PROTECTED] 2001-10-21 15:52 ------- I read the tomcat-user problem also before wrote the bug report! I want show that we must change the server.xml <ejb> semantic's, to address Servlet API conform ejb access. At my source code I don't directly reference the EJB JNDI names from Weblogic or JBoss. I want not used absolute jndi names. The local names as java:/comp/env/ejb/Customer are better for portable code. BEA address this feature with the weblogic.xml mapping and I thing we can do more with the <ejb> tag. <Ejb name="ejb/Echo" type="Session" home="echo.EchoHome" remote="echo.Echo" remote-jndi="echo.EchoHome" factory="weblogic.jndi.WLInitialContextFactory" factoryLocation="t3://127.0.0.1:7001" principal="system" credentials="weblogic" /> or for grouping <ejb-context> <factory>weblogic.jndi.WLInitialContextFactory</factory> <location>t3://127.0.0.1:7001<location> <param> <param-name>principal<param-name> <param-value>system<param-value> </param> <param> <param-name>credentials<param-name> <param-value>weblogic<param-value> </param> <ejb name="ejb/Echo" type="Session" home="echo.EchoHome" remote="echo.Echo" remote-jndi-name="echo.EchoHome" /> <ejb-context> I hope know is the bug or missing feature report clear. Peter
