JCA resources model names and service names should be deterministic ------------------------------------------------------------------- Key: WFLY-1656 URL: https://issues.jboss.org/browse/WFLY-1656 Project: WildFly Issue Type: Bug Components: JCA Affects Versions: 8.0.0.Alpha2 Reporter: Bartosz Baranowski Assignee: Stefano Maestri Fix For: 8.0.0.Beta1 This is an offspring of: https://issues.jboss.org/browse/WFLY-1492 . Example RA definition: {noformat} <resource-adapters> <resource-adapter id="XXX"> <archive>test</archive> <transaction-support>NoTransaction</transaction-support> </resource-adapter> </resource-adapters> {noformat} The *id* attribute is optional. This leads to a bit undeterministic model expansion. There are two bits that dont add up or make this a bad apple. 1. RA service names are not unique, despite their model paths, the service name boils down to *archive name* ( and possibly *id* if its present). This seems odd, since in model we can point exact, unique path(profile, subsystem,.. and so on). 2. Second thing is the *id* piece. Its optional. If its not present, AS injects counter suffix( either due to #1 or because there is doubled definition of RA in the same profile). In the end RA paths look like: {noformat} /xxx/xxx/xxx/${archive-name}/${archive-name} /xxx/xxx/xxx/${archive-name}/${archive-name}->1 /xxx/xxx/xxx/${archive-name}/${archive-name}->2 /xxx/xxx/xxx/${archive-name}/${archive-name}->3 {noformat} With *id* present: /xxx/xxx/xxx/${archive-name}/${id} Im not sure ATM, but its even possible to double with *id* {noformat} /xxx/xxx/xxx/${archive-name}/${id}->1 {noformat}