You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sling.apache.org by "Chetan Mehrotra (JIRA)" <ji...@apache.org> on 2015/02/18 12:52:12 UTC

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

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

Chetan Mehrotra reassigned SLING-4429:
--------------------------------------

    Assignee: Chetan Mehrotra

> 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: Bug
>          Components: Extensions, Launchpad
>            Reporter: Ankit Aggarwal
>            Assignee: Chetan Mehrotra
>            Priority: Critical
>         Attachments: SLING-4429.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)