[
http://jira.jboss.com/jira/browse/JBESB-1087?page=comments#action_12380872 ]
Burr Sutter commented on JBESB-1087:
------------------------------------
Further investigation shows that GroovyGateway.java uses BasicMessageComposer.java which
has:
message.getBody().add(ActionUtils.POST_ACTION_DATA, messagePayload);
It is my thinking that this should be
message.getBody().add(messagePayload);
so that it is in the "default location" just like the File, FTP and JMS
gateways. Note this is not an action but the gateway/composer. All gateways should try
to use the "default location" so the the action developer knows where to look
inside the message object for the "default data".
org.jboss.soa.esb.listeners.message.BasicMessageComposer.java
in product\rosetta\src\org\jboss\soa\esb\listeners\message
groovy gateway & data injection
-------------------------------
Key: JBESB-1087
URL:
http://jira.jboss.com/jira/browse/JBESB-1087
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Transports
Affects Versions: 4.2
Reporter: Burr Sutter
Assigned To: Mark Little
Priority: Minor
The groovy gateway:
<groovy-listener name="groovy-client"
script="MessageInjectionConsole" is-gateway="true" />
drops its message content into the "after" location therefore you must use:
String content = (String) ActionUtils.getTaskObject(message);
to fetch it out in your custom action. This is inconsistent with the rest of the
gateways which are moving to using:
content = (String) message.getBody().get();
--
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