[esb-issues] [JBoss JIRA] Commented: (JBESB-701) JMS Queue Notifier does not have configured message properties attached

Daniel Bevenius (JIRA) jira-events at lists.jboss.org
Mon Aug 27 03:11:18 EDT 2007


    [ http://jira.jboss.com/jira/browse/JBESB-701?page=comments#action_12373936 ] 
            
Daniel Bevenius commented on JBESB-701:
---------------------------------------

I've been trying to reproduce this by writing additional junit tests but without success. 
I've also run a manual test where I used a jms client that posts a JMS Message to the ESB. The ESB was configurerd with a static router which simply passed the message back to the jms client.

This is what the ESB configuration looks like:
<action name="route-to-response" class="org.jboss.soa.esb.actions.Notifier">
	<property name="okMethod" value="notifyOK" />
	<property name="notification-details">
	    <NotificationList type="OK">
		    <target class="NotifyQueues">
			<messageProp name="BEVETESTKEY" value="BEVETESTVALUE" />
			<queue jndiName="queue/ValidationResponse"/>
		    </target>
	    </NotificationList>
         </property>
</action>
My jms client logs the value of the string property like this:
log.debug("JMSMessage StringProperty: " + msg.getStringProperty( "BEVETESTKEY"));

The correct value is displayed. I can't see that there is anything wrong here. 
Jiri, could you let me know if I have not understood the problem?

Thanks,

Daniel 

> JMS Queue Notifier does not have configured message properties attached
> -----------------------------------------------------------------------
>
>                 Key: JBESB-701
>                 URL: http://jira.jboss.com/jira/browse/JBESB-701
>             Project: JBoss ESB
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Rosetta
>    Affects Versions: 4.2 Milestone Release 2
>            Reporter: Jiri Pechanec
>         Assigned To: Daniel Bevenius
>            Priority: Minor
>             Fix For: 4.2
>
>
> The configuration Notifier with class NotifyQueues can contain a list of elements "queue" and each of these "queue" can contain a list of "messageProp" elements that contains properties to be attached to message.
> The properties are not attached.
> The reason is:
>     Constructor NotifyQueues is populated with ConfigTree that has root at the "target" element and has correctly access to the child "queue" elements from which it initilizes but the same ConfigTree is passed to NofityJMS parent class which can't initialize properties as they are stored not on this level but on the level below under each "queue" element.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        



More information about the esb-issues mailing list