marc fleury wrote:
> I have no significant problem (yet).
>
> The main problem i see is that the JSR77 will want to find objects from JNDI
> at some point (hook to management somehow) and for that we need a
> standardized naming structure.
Makes sense. Have you discussed the global vs local namespace issue
(i.e. "/" vs "java:/")?
> I would offer a "hardcoded" naming thing for
> some services (say containerFactory/node/ ) and a symlink for jboss.conf
> names.
Not quite sure what you're referring to (it's getting late over here, so
maybe I'm just too tired to see). Can you expand on this?
> Once we standardize on naming of parts of the server we can provide these
> "hardcoded" but I wouldn't *just* offer the jboss.conf one...
Note that there are two kinds of names we are discussing: JNDI names and
JMX ObjectNames. Currently all JNDI names are hardcoded and linked to
"/" namespace, and all ObjectNames are hardcoded in the respective
services. I am changing some of the services so that they only use a
hardcoded ObjectName if one is not provided in jboss.conf! That allows
one to override *only if necessary*; defaults are always available.
/Rickard
--
Rickard �berg
Email: [EMAIL PROTECTED]
http://www.telkel.com
http://www.jboss.org
http://www.dreambean.com
