Re: JNDI not available from ServletContextListener
On 30/07/2010 04:58, Steve Mitchell wrote: I guess the maintainers know what they're doing, because my original DataSource problem turns out to be a configuration problem. I still don't know why the Eclipse project fails for me, but I'm assuming it's some kind of deployment problem. Do you mind explaining what the problem was, in case we come across it again? p Thanks, case closed, --Steve From: Steve Mitchell Sent: Thursday, July 29, 2010 5:49 PM To: 'users@tomcat.apache.org' Subject: JNDI not available from ServletContextListener Can anybody reproduce the bug I'm getting in Tomcat 6.0.29, or is it just me? I'm trying to access a DataSource via JNDI from a ServletContextListener. I find that my InitialContext has no bindings at all in the ServletContextListener.contextInitialized() method. It makes no difference whether I declare the DataSource in META-INF/context.xml or in conf/server.xml (with a ResourceLink in META-INF/context.xml). A Bugzilla bug was filed for this behavior under Tomcat 7, and the bug was patched. https://issues.apache.org/bugzilla/show_bug.cgi?id=49132 That bug report includes a bare-bones Eclipse project that exhibited the error under Tomcat 7. When I deploy that project on Tomcat 6.0.29, I get the same behavior that was reported under Tomcat 7, consistent with my original DataSource problem. I reported my experience in Bugzilla but it was rejected. https://issues.apache.org/bugzilla/show_bug.cgi?id=49673 Perhaps I've configured something wrong - does anybody else get the same behavior with the Eclipse project tomcat7-web-test under Tomcat 6.0.29? Or is there something wrong with the posted project? --Steve signature.asc Description: OpenPGP digital signature
RE: JNDI not available from ServletContextListener
Hi Steve TC useNaming needs to be set true to enable JNDI access.. http://tomcat.apache.org/tomcat-5.5-doc/config/context.html eclipse has JNDI configurations for the oc4j,jboss and jonas eclipse-plugins you may want to ask eclipse support folk if they can recommend a tomcat plugin that is JNDI configurable i did'nt see any mention of JNDI in sysdeo plugin should'nt be too difficult to refactor the plugin to accept JNDI communication http://www.eclipsetotale.com/tomcatPlugin.html hth Martin Gainty __ Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni. From: mitch...@intertrust.com To: users@tomcat.apache.org Date: Thu, 29 Jul 2010 20:58:52 -0700 Subject: RE: JNDI not available from ServletContextListener I guess the maintainers know what they're doing, because my original DataSource problem turns out to be a configuration problem. I still don't know why the Eclipse project fails for me, but I'm assuming it's some kind of deployment problem. Thanks, case closed, --Steve From: Steve Mitchell Sent: Thursday, July 29, 2010 5:49 PM To: 'users@tomcat.apache.org' Subject: JNDI not available from ServletContextListener Can anybody reproduce the bug I'm getting in Tomcat 6.0.29, or is it just me? I'm trying to access a DataSource via JNDI from a ServletContextListener. I find that my InitialContext has no bindings at all in the ServletContextListener.contextInitialized() method. It makes no difference whether I declare the DataSource in META-INF/context.xml or in conf/server.xml (with a ResourceLink in META-INF/context.xml). A Bugzilla bug was filed for this behavior under Tomcat 7, and the bug was patched. https://issues.apache.org/bugzilla/show_bug.cgi?id=49132 That bug report includes a bare-bones Eclipse project that exhibited the error under Tomcat 7. When I deploy that project on Tomcat 6.0.29, I get the same behavior that was reported under Tomcat 7, consistent with my original DataSource problem. I reported my experience in Bugzilla but it was rejected. https://issues.apache.org/bugzilla/show_bug.cgi?id=49673 Perhaps I've configured something wrong - does anybody else get the same behavior with the Eclipse project tomcat7-web-test under Tomcat 6.0.29? Or is there something wrong with the posted project? --Steve
RE: JNDI not available from ServletContextListener
I guess the maintainers know what they're doing, because my original DataSource problem turns out to be a configuration problem. I still don't know why the Eclipse project fails for me, but I'm assuming it's some kind of deployment problem. Thanks, case closed, --Steve From: Steve Mitchell Sent: Thursday, July 29, 2010 5:49 PM To: 'users@tomcat.apache.org' Subject: JNDI not available from ServletContextListener Can anybody reproduce the bug I'm getting in Tomcat 6.0.29, or is it just me? I'm trying to access a DataSource via JNDI from a ServletContextListener. I find that my InitialContext has no bindings at all in the ServletContextListener.contextInitialized() method. It makes no difference whether I declare the DataSource in META-INF/context.xml or in conf/server.xml (with a ResourceLink in META-INF/context.xml). A Bugzilla bug was filed for this behavior under Tomcat 7, and the bug was patched. https://issues.apache.org/bugzilla/show_bug.cgi?id=49132 That bug report includes a bare-bones Eclipse project that exhibited the error under Tomcat 7. When I deploy that project on Tomcat 6.0.29, I get the same behavior that was reported under Tomcat 7, consistent with my original DataSource problem. I reported my experience in Bugzilla but it was rejected. https://issues.apache.org/bugzilla/show_bug.cgi?id=49673 Perhaps I've configured something wrong - does anybody else get the same behavior with the Eclipse project tomcat7-web-test under Tomcat 6.0.29? Or is there something wrong with the posted project? --Steve
