I still think we need a jmx object name alias registry to wean off of
the objectnames to simple, purpose oriented names. This would have to be
integrated as an aspect on top of the mbeanserver/registry.

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Adrian Brock
Sent: Wednesday, February 01, 2006 12:59 PM
To: jboss-development@lists.sourceforge.net
Cc: Bill Burke
Subject: Re: [JBoss-dev] Re: Guessing datasource name

Perhaps we should just byte the bullet and fix this naming confusion?
The problem is everybody's existing config that uses it.
e.g. JMS and login-config.xml that reference these names.

You can certainly "fix" the stylesheet and change this config
in jbossjca-service.xml

  <mbean code="org.jboss.deployment.XSLSubDeployer"
name="jboss.jca:service=ConnectionFactoryDeployer">
    <attribute name="DdSuffix">-ds.xml</attribute>
    <attribute name="EnhancedSuffixes">300:-ds.xml</attribute>
    <attribute
name="XslUrl">stylesheets/ConnectionFactoryTemplate.xsl</attribute>
    <attribute name="ValidateDTDs">false</attribute>
  </mbean>




-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642
_______________________________________________
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to