[
https://issues.apache.org/jira/browse/SLING-4429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14325800#comment-14325800
]
Carsten Ziegeler commented on SLING-4429:
-----------------------------------------
[~chetanm] Can we generalize the JNDI solution ? We could store the app server
context in a static variable in the ServletContextListener and then somehow do
some magic, that code running within OSGi gets our context that is simply a
wrapper around the app server context
> 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)
