Not really sure what you are asking, but see my message from yesterday. You
can put the jnp into the jndi-name in your jboss.xml deployment descriptor.
Because it is in your jar file, it will persist. That will allow that one
EJB to be referenced from that jar.
----- Original Message -----
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, May 02, 2001 4:50 PM
Subject: [JBoss-user] persistent bind to jnp possible?
>
> Hi,
>
> Is it possible to bind something to jnp and then shut down/restart jboss,
> and can still lookup the bounded info?
> e.g., bind some app configuration info into jnp and get it later, even
> after restart jboss.
>
> If it not possible, any work around? Do I need to use "External JNDI
> Configuration and JNDI Viewing"?
> -- if I need to do it within an ejbean and want to keep the initialContext
> not hardcoded? if doing bind/lookup
> only from ordinary clients, seems that we can simply use a directory for
> app config info.
>
> Can we change jnp to make it only read-only, but wirte also? How difficult
> it is? How desirable?
>
>
> thanks
>
>
> Kai
>
>
> _______________________________________________
> JBoss-user mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/jboss-user
>
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user