[
https://issues.apache.org/jira/browse/SLING-4429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14325915#comment-14325915
]
Neerav commented on SLING-4429:
-------------------------------
InitialContext in itself is just a collection of properties. The validity of
properties and the check whether the request is from application server managed
thread is done at the time of lookup. So as [~chetanm] mentioned, we need to
perform lookup from app server managed thread, store it and then use it from
un-managed threads.
> 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
>
>
> 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)
