Hi Christina,
The JNDI context is for now in-memory (using xbean-naming). It means
that jndi:name/jndi:bind are not persistent when you restart.
I plan to implement a properties persistence adapter (AFAIR, I created a
Jira assigned to me).
On the other hand, the JNDI names defined as OSGi service properties are
persistent.
Regards
JB
On 02/20/2014 09:13 AM, christina wrote:
I am creating a JNDI alias in Karaf using the jndi:alias command and have
noticed that this alias is not persistent between Karaf restarts. The same
is true when using the jndi:bind command to directly bind an OSGi service to
the JNDI context. I assume that this is because the underlying OSGi service
is un-registered and re-registered in the meantime, but I would expect to be
somehow able to bind OSGi services to the JNDI in a persistent way since
otherwise I can't really use the JNDI asmy service won't be there after
restarting Karaf. Am I perhaps missing something? Is there a way to create a
JNDI alias in a persistent way?
--
View this message in context:
http://karaf.922171.n3.nabble.com/Persistent-JNDI-names-aliases-tp4031846.html
Sent from the Karaf - User mailing list archive at Nabble.com.
--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com
