ManagedConnectionFactoryName exception in RAs for JBoss 3.2.

[sanepid]

Hello
I have a problem deploying my resource adapters in JBoss 3.2.0 . They used to work fine for all RC releases, but now I'm geting the following exception :
10:13:03,507 INFO [ServiceConfigurator] Problem configuring service jboss.jca:service=XATxCM,name=OpenSRS
org.jboss.deployment.DeploymentException: Exception setting attribute javax.management.Attribute: name=ManagedConnectionFactoryName value=jboss.jca:service=XATxOpenSRS,name=OpenSRS on mbean jboss.jca:service=XATxCM,name=OpenSRS; - nested throwable: (javax.management.AttributeNotFoundException: Writable attribute 'ManagedConnectionFactoryName' not found)
at org.jboss.system.ServiceConfigurator.setAttribute(ServiceConfigurator.java:472)
at org.jboss.system.ServiceConfigurator.configure(ServiceConfigurator.java:357)
at org.jboss.system.ServiceConfigurator.internalInstall(ServiceConfigurator.java:176)
at org.jboss.system.ServiceConfigurator.install(ServiceConfigurator.java:118)
at org.jboss.system.ServiceController.install(ServiceController.java:225)
at sun.reflect.GeneratedMethodAccessor20.invoke(Unknown Source)
...............



Here is my resource adapter -service.xml file:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE server>


<!--new configuration for new ConnectionManager-->


OpenSRS

<depends optional-attribute-name="TransactionManagerService">jboss:service=TransactionManager
<depends optional-attribute-name="ManagedConnectionFactoryName">

<!--hack till better deployment system-->
<depends optional-attribute-name="OldRarDeployment">jboss.jca:service=RARDeployment,name=OpenSRS



<config-property>
<config-property-name>HostName</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value>horizon.opensrs.net</config-property-value>
</config-property>

<config-property>
<config-property-name>PortNumber</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value>55000</config-property-value>
</config-property>







<depends optional-attribute-name="ManagedConnectionPool">

0
2000
5000
15
<!--criteria indicates if Subject (from security domain) or app supplied
parameters (such as from getConnection(user, pw)) are used to distinguish
connections in the pool. Choices are
ByContainerAndApplication (use both),
ByContainer (use Subject),
ByApplication (use app supplied params only),
ByNothing (all connections are equivalent, usually if adapter supports
reauthentication)-->
ByApplication


<depends optional-attribute-name="CachedConnectionManager">jboss.jca:service=CachedConnectionManager




Any idea of what may be wrong, please?
Thanks

[davidjencks]

I recommend using *-ds.xml files since they are simpler and more likely to insulate your configs from changes I may make.

However, if you wish to keep using a *-service.xml file, move the depends ManagedConnectionFactoryName embedded mbean to inside the pool mbean config.