[jboss-jira] [JBoss JIRA] Updated: (JBESB-380) Custom composer for GatewayListeners not working
Mark Little (JIRA)
jira-events at jboss.com
Wed Jan 17 05:19:52 EST 2007
[ http://jira.jboss.com/jira/browse/JBESB-380?page=all ]
Mark Little updated JBESB-380:
------------------------------
Component/s: Configuration
Rosetta
Fix Version/s: 4.0
Affects Version/s: 4.0 CR2
Assignee: Kurt Stam (was: Mark Little)
Priority: Critical (was: Major)
> Custom composer for GatewayListeners not working
> ------------------------------------------------
>
> Key: JBESB-380
> URL: http://jira.jboss.com/jira/browse/JBESB-380
> Project: JBoss ESB
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Rosetta, Configuration
> Affects Versions: 4.0 CR2
> Reporter: Bernard Tison
> Assigned To: Kurt Stam
> Priority: Critical
> Fix For: 4.0
>
>
> The GatewayListeners (FileGatewayListener, JmsGatewayListener, ..) allow for a custom message composer instead of the default one, by attaching an action element to the gateway service definition in jbossesb.xml. But this action element is not picked up by the GatewayGenerator and is not copied into the jbossesb-gateway.xml file. The GatewayListener doesn't find the action definition in its config tree and falls back to the default composer.
--
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 jboss-jira
mailing list