Bug 759097 - JCA XML tags
Summary: JCA XML tags
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: Messaging_Programming_Reference
Version: 2.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: 2.1.2
: ---
Assignee: Cheryn Tan
QA Contact: Frantisek Reznicek
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-12-01 12:07 UTC by ppecka
Modified: 2015-11-16 01:13 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-05-02 05:31:39 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description ppecka 2011-12-01 12:07:30 UTC
Description of problem:
Jiri Pechanec asked for new introduced tags being documented. Here is small sample taken from original post:
https://bugzilla.redhat.com/show_bug.cgi?id=729131#c14

<attribute name="Properties">
destinationAddress=jms_ee_mdb_mdb_sndQ_MDB_QUEUE;{create:always,node:{type:queue}}
destinationType=queue
</attribute>

Comment 1 Cheryn Tan 2012-01-03 07:37:44 UTC
http://documentation-stage.bne.redhat.com/docs/en-US/Red_Hat_Enterprise_MRG/2/html/Qpid_JCA_Adapter_User_Guide/sect-Qpid_JCA_Adapter_User_Guide-Configuration_JBoss-Administered_Object.html

Under JMS Queue, I've changed the destinationAddress syntax:
<attribute name="Properties">
destinationAddress=jms_ee_mdb_mdb_sndQ_MDB_QUEUE;{create:always,node:{type:queue}}
destinationType=queue
</attribute>

I've also mirrored the changes for JMS Topic, is this accurate?

<attribute name="Properties">
destinationAddress=jms_ee_mdb_mdb_sndQ_MDB_TOPIC;{create:always,node:{type:topic}}
destinationType=topic
</attribute>

Comment 3 Jiri Pechanec 2012-01-19 11:54:45 UTC
I am ok with the text

Comment 4 Frantisek Reznicek 2012-03-13 14:58:16 UTC
Above added properties were documented.

-> VERIFIED

Comment 5 Cheryn Tan 2012-05-02 05:31:39 UTC
Documents have been published on http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_MRG/index.html as part of the MRG-M 2.1.2 update.


Note You need to log in before you can comment on or make changes to this bug.