[jira] Closed: (GERONIMO-3609) JNDI lookup problem on fowarded calls in Jetty

["David Jencks (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/GERONIMO-3609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Jencks closed GERONIMO-3609.
----------------------------------

    Resolution: Fixed

The patch seems to work and ith the other new uses of LifecycleMethod I don't think the code can be simplified more so I committed it in rev 601149.

> JNDI lookup problem on fowarded calls in Jetty
> ----------------------------------------------
>
>                 Key: GERONIMO-3609
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-3609
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: Jetty
>    Affects Versions: 2.0.x, 2.1
>            Reporter: Jarek Gawor
>            Assignee: David Jencks
>             Fix For: 2.1
>
>         Attachments: GERONIMO-3609-2.patch, GERONIMO-3609.patch
>
>
> I am having trouble looking up a DataSource from an EAR containing a
> WAR (which is where the lookup takes place) using JNDI. I find it to
> be really weird, because I can look up the DataSource fine if I do it
> through a JSP page or a servlet. However, when I try to look it up in
> portlet code, the jndi name does not seem to be visible, although it
> is visible in the JNDI viewer. Additionally, I have successfully
> looked it up through jsp and servlets.
> This is only a problem in Jetty, because the same code works fine for Tomcat.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.