No. There is still just one name attribute that either defines the symbolic
name or the true object name. Backward compatible with the current config.

Changing the name is an admin function that may be done because you don't
like the fact that JBoss is using several domain names. Its not just the
domain
portion that needs to be changed. The last change was to change the
attribute
of the security manager to "name=xxx" to "service=xxx" to be consistent with
the other services.

xxxxxxxxxxxxxxxxxxxxxxxx
Scott Stark
Chief Technology Officer
JBoss Group, LLC
xxxxxxxxxxxxxxxxxxxxxxxx
----- Original Message -----
From: "David Jencks" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, July 31, 2002 7:42 AM
Subject: Re: [JBoss-dev] Fw: [JBoss-user] MBean interfaces to EJBs


> As I understand the proposal at the moment, it is to allow mbeans to
> declare multiple object names that they can be looked up under (at least
in
> the dependency management part of ServiceController), some of them of the
> form
>
>
alias:symbolic-name=SomethingYouMightRememberButThenAgainYouMightNotService
>
> and to include these in the *-service.xml in the mbean config, along with
> the "real" object name.
>
> Sorry, but I don't see the point over naming the mbean well in the first
> place.  How often are we going to want to change the
> SomethingYouMightRememberButThenAgainYouMightNotService part compared to
> the "real" object name?  What is the use case for changing the domain part
> of a bunch of object names?
>
> david jencks
>
>
> On 2002.07.31 10:24:11 -0400 Scott M Stark wrote:
> > Don't allow that. Names have would have to be indicated as aliases
> > using an object name form "alias:symbolic-name". You can detect
> > duplicate aliases just as you can detect an attempt to reuse object
> > names.




-------------------------------------------------------
This sf.net email is sponsored by: Dice - The leading online job board
for high-tech professionals. Search and apply for tech jobs today!
http://seeker.dice.com/seeker.epl?rel_code=31
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to