Hi,

I'm trying to deploy jms services in JBoss 3.2.7... I know it's an older version, but the only version our software currently supports. I'm getting a Deployment exception trying to deploy the JMSProvider using a deployment file as follows:

<connection-factories>

 <mbean code="org.jboss.jms.jndi.JMSProviderLoader" name="jboss.mq:service=JMSProviderLoader,name=JMSProvider">
 <attribute name="ProviderName">DefaultJMSProvider</attribute>
 <attribute name="ProviderAdapterClass">org.jboss.jms.jndi.JNDIProviderAdapter</attribute>
 <attribute name="FactoryRef">java:/ConnectionFactory</attribute>
 <attribute name="QueueFactoryRef">java:/ConnectionFactory</attribute>
 <attribute name="TopicFactoryRef">java:/ConnectionFactory</attribute>
 </mbean>

 <mbean code="org.jboss.jms.asf.ServerSessionPoolLoader" name="jboss.mq:service=ServerSessionPoolMBean,name=StdJMSPool">
 <depends optional-attribute-name="XidFactory">jboss:service=XidFactory</depends>
 <attribute name="PoolName">StdJMSPool</attribute>
 <attribute name="PoolFactoryClass">org.jboss.jms.asf.StdServerSessionPoolFactory</attribute>
 </mbean>

 <tx-connection-factory>
 <jndi-name>JmsXA</jndi-name>
 <xa-transaction/>
 <rar-name>jms-ra.rar</rar-name>
 <connection-definition>org.jboss.resource.adapter.jms.JmsConnectionFactory</connection-definition>
 <config-property name="SessionDefaultType" type="java.lang.String">javax.jms.Topic</config-property>
 <config-property name="JmsProviderAdapterJNDI" type="java.lang.String">java:/DefaultJMSProvider</config-property>
 <max-pool-size>20</max-pool-size>
 <security-domain-and-application>JmsXARealm</security-domain-and-application>
 </tx-connection-factory>

</connection-factories>

The error message is as follows:

13:13:46,100 INFO [ServiceConfigurator] Problem configuring service jboss.mq:service=JMSProviderLoader,name=JMSProvider

org.jboss.deployment.DeploymentException: No Attribute found with name: FactoryRef


As one can see by my deployment descriptor I am specifying an attribute named "FactoryRef"

Has anyone seen a similar message? Does anyone know how to fix this problem? Also, does anyone have a set of deployment descriptors specifying file based persistence that will get JMS working, including MDBs, in JBoss 3.2.7?

Thanks in advance for any help,

Steve...