Hello Linda,
>> other example: name has to start with java:app/jdbc, to avoid access to
>> other JNDI names outside the application
>>
>
>Our expectation here is that access to the JNDI name space will scoped per
>tenant.
>Which example are you referring to?
you are right. It is clearly stated in the document, that the namespace is tenant scoped. I overlooked that when I read the document the first time.
"java:global: global namespace for all applications in the application server instance"
I assume this means "visible to all applications from the same tenant"?
Do we need a "java:global:global" scope? How should the platform provide default resources to tenants? Or is it expected to provide a mapping from platform java:global to tenant java:global. Something like "provide this resource to all tenants"? I'm not sure it this makes sense, but I'm thinking of a private cloud offering and some read-only resource, e.g. user-db, call kind of other master data.
>We agree with you. We don't expect passwords to be used in this manner
>in production systems. However, they may be useful in development mode
>and in testing locally, etc.
Do you have an example how passwords are provided in production?
Regards
Christian
--
NEU: FreePhone - 0ct/min Handyspartarif mit Geld-zurück-Garantie!
Jetzt informieren: http://www.gmx.net/de/go/freephone