The definitive source for the datasource mbean names is the 
ConnectionFactoryTemplate.xsl used by the deployer which processes the *-ds.xml 
deployemnts.


  |   <xsl:template match="local-tx-datasource">
  |     <mbean code="org.jboss.resource.connectionmanager.TxConnectionManager" 
  |            name="jboss.jca:service=LocalTxCM,name={jndi-name}" 
  |            display-name="ConnectionManager for DataSource {jndi-name}">
  | ...
  | 
  |   <xsl:template match="no-tx-datasource">
  |     <mbean 
code="org.jboss.resource.connectionmanager.NoTxConnectionManager" 
  |            name="jboss.jca:service=NoTxCM,name={jndi-name}"
  |            display-name="ConnectionManager for DataSource {jndi-name}">
  | ...
  | 
  |   <xsl:template match="xa-datasource">
  |     <mbean code="org.jboss.resource.connectionmanager.TxConnectionManager" 
  |            name="jboss.jca:service=XATxCM,name={jndi-name}"
  |            display-name="ConnectionManager for DataSource {jndi-name}">
  | 
  | ...
  | 
  | 

However, the same base pattern is also used for the generic connection factory 
mappings:

  |   <!-- template for generic resource adapters supporting transactions -->
  |   <xsl:template match="tx-connection-factory">
  |     <mbean code="org.jboss.resource.connectionmanager.TxConnectionManager" 
  |            name="jboss.jca:service=TxCM,name={jndi-name}" 
  |            display-name="ConnectionManager for ConnectionFactory 
{jndi-name}">
  | ...
  | 
  |   <xsl:template match="no-tx-connection-factory">
  |     <mbean 
code="org.jboss.resource.connectionmanager.NoTxConnectionManager" 
  |            name="jboss.jca:service=NoTxCM,name={jndi-name}" 
  |            display-name="ConnectionManager for ConnectionFactory 
{jndi-name}">
  | ...
  | 
  | 

You can't distinguish between a no-tx-connection-factory deployment and a 
no-tx-datasource deployment by looking at the mbean name alone. There are 
attributes that can be used to differentiate one from the other though. In 
4.0.x a datasource has a JMXInvokerName attribute while a connection factory 
does not. This diff does not exist in 3.2. It would probably be better to 
explicitly tag the datasource as such with an additional jcaType=DataSource 
attribute in the name.


View the original post : 
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3864927#3864927

Reply to the post : 
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3864927


-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
JBoss-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to