I could always count on you to have a lively conversation early at
night. People are going to hate us when they get their e-mails first
thing on the morning :)
Anyway, the JNDI specs are not the best in the world, but here's what I
gathered. A federated namespace spans multiple namespaces using compund
names. For example:
ldap://host/uid=arkin,ou=people
consists of a DNS and DN. A flat namespace is one that spans a single
namespace using composite names. For example:
file:/usr/bin
The ENC falls under the second category.
By definition all contexts should support Names, a lookup on "" always
returns the same context. Sub-contexts need not be creatable or
destructable (e.g. read-only), but they must be retrievable with lookup(
"ctx" ).
I know the specs are consistent in using "java:comp/env" and
"file:/usr/bin" and "ldap://host", but aside from this consistency, I
could not find anything in the specs or API that indicates the contrary
to the above.
arkin
> That is not the definition of "flat". You're describing "federated"
> namespaces. Flat is where there are no subcontexts, or possibilities to
> create/destroy subcontexts. "java:comp/env/myvar" is still a valid name,
> but the name would have the single component "comp/env/myvar".
>
> /Rickard
>
> --
> Rickard Öberg
>
> @home: +46 13 177937
> Email: [EMAIL PROTECTED]
> http://www.dreambean.com
> Question reality
>
> ===========================================================================
> To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
> of the message "signoff EJB-INTEREST". For general help, send email to
> [EMAIL PROTECTED] and include in the body of the message "help".
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
