[
https://issues.apache.org/jira/browse/SLING-4429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14325962#comment-14325962
]
Carsten Ziegeler commented on SLING-4429:
-----------------------------------------
Ok, thanks - I was under the impression that the lookup of the context is the
problematic part, but once you have the context it can be used to lookup in
unmanaged threads; but if that information is wrong, then yes, we need to do it
this way.
Getting the sling properties might be a little bit tricky as the listener is
invoked before Sling is instatiated. I'm wondering if we need to use a
listener, the Sling servlet is triggered and either on init or the first
request, Sling is instantiated. The thread should be a managed thread so maybe
we can do this while Sling is setting up itself; in that case the sling
properties would be 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
>
>
> 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)
