JNDI Values not accessible on Gemini blueprint Spring Configuration running on Tomcat [message #1854189] |
Fri, 05 August 2022 09:21 |
Christian Meister Messages: 3 Registered: November 2015 |
Junior Member |
|
|
I am trying to access JNDI values from SpringConfiguration class invoked by Gemini Blueprint.
This application runs on Apache Tomcat with Equinox OSGI.
It is old Application that uses Gemini Blueprint 1.0.2.
I can define my JDNI Values in server.xml link them in context.xml and use them in my web.xml.
In my launch.ini i use the parent classloader fwk so the JNDI configuration is passed to the OSGI-Container.
My Application-Bundles can read those values for example in Bundle-Activator:
String xxx= InitialContext.doLookup("java:comp/env/xxx"); or
String xxx= new InitialContext().lookup("java:comp/env/xxx");
Invoked from Gemini in BlueprintExtenderThread i can't access those values.
<jee:jndi-lookup id="xxx" jndi-name="java:comp/env/xxx" />
fails.
The classloaders are different in Bundle-Activator and BlueprintExtenderThread.
How can i access my JNDI configuration with gemini blueprint?
[Updated on: Fri, 05 August 2022 10:47] Report message to a moderator
|
|
|
|
Powered by
FUDForum. Page generated in 0.03327 seconds