|Makes sense. Have you discussed the global vs local namespace issue
|(i.e. "/" vs "java:/")?
NDA kid NDA :)
|> 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.
|
Ok the specifics of the JMX impl of the naming is not the question, so if
you want to provide an overriding name there that is fine imho. (any
strategy you implement is fine). For the JNDI names we will need a
standardization but it is not there yet... so just go ahead...
go to sleep
marc
|/Rickard
|
|--
|Rickard �berg
|
|Email: [EMAIL PROTECTED]
|http://www.telkel.com
|http://www.jboss.org
|http://www.dreambean.com
|
|
|
