Doesn't help me on 4.0.3SP1. What we should *really* do is create those
JNDI dependencies we were arguing about before.
Adrian Brock wrote:
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>
On Wed, 2006-02-01 at 12:52, Adrian Brock wrote:
On Wed, 2006-02-01 at 12:05, Bill Burke wrote:
Can I use:
"jboss.jca:service=ManagedConnectionFactory,name=DefaultDS"?
It is the DataSourceBinding or ConnectionFactoryBinding
that you want to depend upon.
This is what populates JNDI.
Bill Burke wrote:
In EJB3 I'm trying to guess the datasource MBean name so that I can
create a dependency on it. I do this based on the JNDI name passed into
persistence.xml. So, if the datsource is "java:/DefaultDS" I assume
that there is a:
"jboss.jca:service=DataSource,name=DefaultDS" mbean available.
Is this a valid assumption?
Thanks,
Bill
--
Bill Burke
Chief Architect
JBoss Inc.
-------------------------------------------------------
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&kid=103432&bid=230486&dat=121642
_______________________________________________
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
