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. I would offer a "hardcoded" naming thing for
some services (say containerFactory/node/ ) and a symlink for jboss.conf
names.
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...
marc
|-----Original Message-----
|From: [EMAIL PROTECTED]
|[mailto:[EMAIL PROTECTED]]On Behalf Of Rickard �berg
|Sent: Friday, November 03, 2000 2:51 PM
|To: jBoss Developer
|Subject: [jBoss-Dev] JNDI names
|
|
|Hi!
|
|I am in the process of converting JNDI names to use "java:/" prefix
|where appropriate (almost everywhere!).
|
|Is this ok for everyone?
|
|I am also running into a little problem. Some services use the JNDI name
|in
|their JMX ObjectName. With the ":" in the name this breaks. As discussed
|before it might be better to change most services to *not* choose their
|own ObjectName, but instead configure that in jboss.conf. Does anyone
|have any feelings on that? That would make it easier to do FileLogging
|names as well which is(/was?) also a problem for the same reasons.
|
|regards,
| Rickard
|
|--
|Rickard �berg
|
|Email: [EMAIL PROTECTED]
|http://www.telkel.com
|http://www.jboss.org
|http://www.dreambean.com
|
|
|
