[
https://issues.jboss.org/browse/JBTM-1561?page=com.atlassian.jira.plugin....
]
Tom Jenkinson commented on JBTM-1561:
-------------------------------------
Hi Cris,
1. I agree that the blacktie-admin-services ear needs all the servers and services
defining in it, this is by design. However, as you say the problem is that those are not
embedded within a domain element (servers is a top level element) so it would not work at
the moment. It would be possible to modify the code to embed the servers element under
domain so we can advertise queues with a specific domain prefix/suffix.
2. I agree, the domain concept has not been fully designed yet. The question is how to
approach domain. We could:
i. back out the concept of domain entirely, as you say this has the negative that you
can't define different servers which have the same service id in them
ii. allow multiple domains to communicate within a single blacktie stompconnect. Client
code would have to send to queues with a domain qualified name if not sending to the
default domain.
iii. Modify our approach so that the domain is the set of separate servers that connect
via a single blacktie stompconnect service. We probably would not need the
<DOMAIN>fooapp</DOMAIN> config in each _servers_ btconfig.xml as the domain is
implicity by the connection to the stomp admin service server socket (<MQ
HOST="${JBOSSAS_IP_ADDR}" PORT="61613" USER="guest"
PASSWORD="password1@" RECEIVE_TIMEOUT="10"
TIME_TO_LIVE="40"/>). Different servers should connect to different domains
via <MQ> configuration. It would be useful for each blacktie stompconnect _service_
to have access to <DOMAIN> config in order to add a message header identifying the
domain it was created within on the JMS messages it creates and then the blacktie
stompconnect receiver to apply this as a filter on the queue when receiving messages. As
you say there would be no way to call cross domain at the moment and as such btadmin would
at least need changing so that it can talk to multiple <MQ> elements for the
different domains.
iv. Remove domain support altogether. This is like option 3 but without even embeding the
domain identifier as a message property in the stompconnect service.
What do you prefer? I am erring on the side of stripping out domains altogether.
Tom
Cannot create a user defined XATMI service
------------------------------------------
Key: JBTM-1561
URL:
https://issues.jboss.org/browse/JBTM-1561
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: BlackTie, Documentation
Affects Versions: 5.0.0.M1
Reporter: Michael Musgrove
Assignee: Amos Feng
Fix For: 6.0.0.Final
The administrative interface, btadmin, does not support the definition of user defined
services. Perhaps this functionality was present in the old RHQ interface and was not
ported to btadmin when RHQ support was dropped.
The documentation set does not describe how to configure user defined services.
--
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