[jboss-jira] [JBoss JIRA] Closed: (JBESB-380) Custom composer for GatewayListeners not working

[Kurt Stam (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBESB-380?page=all ]

Kurt Stam closed JBESB-380.
---------------------------

    Resolution: Done

Moved the definition of the gateway composer class from the action element in an an attribute of the gateway.

Now you can specify the custom composer class and method using properties on the listener, so do  something like:

 <jms-listener name="JMS-Gateway"
                    busidref="quickstartGwChannel"
                    maxThreads="1"
                    is-gateway="true"
                    >
                    <property name="composer-class" value="org.jboss.soa.esb.listeners.gateway.JmsGatewayListener"/>
                    <property name="composer-process" value="process"/>
                </jms-listener>

> 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: Configuration, Rosetta
>    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