[ https://issues.jboss.org/browse/JBTM-1561?page=com.atlassian.jira.plugin.... ] Crispin Boylan commented on JBTM-1561: -------------------------------------- I've looked into this and there are a number of issues: 1. The btconfig.xml inside blacktie-admin-services.ear is used to determine the list of available servers. This means that if I have two applications running under the same wildfly instance I would have to define all the servers in the ear file btconfig.xml, or it wouldnt be able to tell me which servers are running. 2. The domain value of btconfig.xml doesnt really seem to be used, so I cant say have two applications with different domain values and then both advertise a service called fooapp, it would clash as we dont use the domain value when defining the queues. I guess to solve this we would need to: 1. add the domain to the name of the queue, so BTR_fooapp would become BTR_fooapp_foodomain, the only trouble here would be calling from one domain to another becomes impossible as there's no way to specify what domain you want to call (as far as I know, and even if there was, how do you specify a different domain from the default). Perhaps in this case it's easiest just to assume that apps running in the same wildfly can't define the same service? 2. Avoid using the btconfig.xml for servers and queues and send the btconfig.xml (or just the list of queues/servers) with every call to the admin services which requires us to know the full list of servers and queues for the domain. thoughts? is there a secret reason for having a defined domain value? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira