Hi,
I'm not 100% sure of this, however I think the name in the mbean tag is
part of the mbean object name for the mbean whereas the poolname attribute
ends up being the jndi binding name for the (datasource) object users can
look up. There is no particular reason I can see to force these to be the
same.
david jencks
On 2001.06.18 12:46:39 -0400 "Ferguson, Doug" wrote:
> I didn't get any answers on the user list.
>
> Maybe this is a dev issue.
> Could we re-write the mbean to only require one place for the name?
>
> d.
>
> -----Original Message-----
> From: Ferguson, Doug [mailto:[EMAIL PROTECTED]]
> Sent: Saturday, June 16, 2001 5:28 PM
> To: JBoss User (E-mail)
> Subject: [JBoss-user] Why the redundancy in DataSource mbean tag?
>
>
>
> Why are there two different locations for the name of the DS?
> Thanks.
>
> .................. See the name Falcon ......................
>
> <mbean code="org.jboss.jdbc.XADataSourceLoader"
> name="DefaultDomain:service=XADataSource,name=Falcon">
> <attribute name="PoolName">Falcon</attribute>
> ...
> </mbean>
>
> _______________________________________________
> JBoss-user mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/jboss-user
>
> _______________________________________________
> Jboss-development mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/jboss-development
>
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
