Hi!
Just some minor corrections.
marc fleury wrote:
> Yes and no,
>
> Yes: a service provider for naming could perfectly take the reference we
> pass to it and persist them (if able). Here I am talking about the "global"
> directory, i.e. your naming file system (I like to think of it as a
> distributed filesystem) can expose the global references, this is
> transparent to jboss and j2ee "en general", i.e. orthogonal, should work.
Correct.
> However: j2ee defines the "java:" namespace which in the case of beans is a
> projection of the global namespace (or filesystem) to a given bean. Think
> of it as a Unix filesystem where you only see the files you have r access
> to, you don't see the rest. In other words unlike Unix you won't even *see*
> in the sense of ls -al the files or objects in the namespace because java:
> is scoped for a particular bean.
Correct.
> Bottom line: jboss needs to keep the java: association in the container and
> does calls to the naming provider (in our case jnp) to set the scoped and
> projected view of the namespace to the bean. That requires acces to the
> root setting and we don't do that with LDAP. If there is a way to access
> the equivalent of "setRoot(beanNamingRoot)" on the LDAP provider then we
> could code it (trivial) but it needs to be done. If there are takers of
> that, i will gladly kick a sub project on it.
Correct. So, the JNDI settings could use another global JNDI provider,
as !long as the "java:" implementation is the current one!.
/Rickard
--
Rickard �berg
Email: [EMAIL PROTECTED]
http://www.telkel.com
http://www.jboss.org
http://www.dreambean.com
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
