[jira] [Commented] (SLING-4429) Support JNDI lookup in JDBC DataSource Provider for App Servers

["Carsten Ziegeler (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SLING-4429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14348340#comment-14348340 ] 

Carsten Ziegeler commented on SLING-4429:
-----------------------------------------

What about doing this in the init() method of the Sling Servlet - avoiding the registration of yet another listener?
In that case we should prefix the init parameters for the servlet with something like "jndi" to distinguish them from parameters for Sling itself - and only do the jndi stuff if such a parameter is available

> Support JNDI lookup in JDBC DataSource Provider for App Servers
> ---------------------------------------------------------------
>
>                 Key: SLING-4429
>                 URL: https://issues.apache.org/jira/browse/SLING-4429
>             Project: Sling
>          Issue Type: Improvement
>          Components: Extensions, Launchpad
>            Reporter: Ankit Aggarwal
>            Assignee: Chetan Mehrotra
>         Attachments: SLING-4429.patch, SLING-4429_Latest.patch
>
>
> JNDI lookup fails in case of WebSphere as mentioned in JIRA SLING-3735.
> (Where we are trying the JNDI access from a thread that is not managed by the J2EE.).
> In this case, We will create a Listener in sling launchpad webapp and then register the JNDI DataSource in DummyContext which would then be available in OSGI environment.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)