[JBoss JIRA] Created: (JBESB-1087) groovy gateway & data injection
by Burr Sutter (JIRA)
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
17 years, 1 month
[JBoss JIRA] Created: (JBESB-1085) transformation reloading doesn't work
by Jaroslaw Kijanowski (JIRA)
transformation reloading doesn't work
-------------------------------------
Key: JBESB-1085
URL: http://jira.jboss.com/jira/browse/JBESB-1085
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Transformation Service
Affects Versions: 4.2
Reporter: Jaroslaw Kijanowski
Assigned To: Tom Fennelly
I'm trying to reload a SmooksTransformer's config resource. I'm using the transform_XML2XML_simple QS + one class (UpdateNotifier) for notification (QS is attched).
How to reproduce:
and deploy
ant runtest -> the message is transformed properly
ant updateTopic
ESB console:
21:24:23,035 INFO [SmooksInstanceManager] Transformation configuration update notification received for configuration source 'transform'. Resetting SmooksTransformer in order to force a configuration re-read.
ant runtest -> the message isn't transformed
--
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
17 years, 1 month
[JBoss JIRA] Created: (JBESB-1017) error in fun_cbr QS
by Jaroslaw Kijanowski (JIRA)
error in fun_cbr QS
-------------------
Key: JBESB-1017
URL: http://jira.jboss.com/jira/browse/JBESB-1017
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Examples
Affects Versions: 4.2
Reporter: Jaroslaw Kijanowski
Assigned To: Mark Little
When I try to extend the QS as described in readme.txt (add three actions to the green service) I get:
18:04:15,413 INFO [STDOUT] Green Team
18:04:15,488 ERROR [SmooksDOMFilter] Failed to apply processing unit [org.milyn.javabean.BeanPopulator] to [org:milyn:smooks:unknowndoc:/Order].
org.milyn.cdr.SmooksConfigurationException: Bean [orderHeader] configuration invalid. Bean setter method [setOrderDate(java.util.GregorianCalendar)] not found on type [org.jboss.soa.esb.dvdstore.OrderHeader]. You may need to set a 'decoder' on the binding config.
It works fine with the dvdstore from transform_XML2POJO/src/org/jboss/soa/esb/dvdstore.
--
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
17 years, 1 month
[JBoss JIRA] Created: (JBESB-646) NON_PERSISTENT JMS messaging.
by Daniel Bevenius (JIRA)
NON_PERSISTENT JMS messaging.
-----------------------------
Key: JBESB-646
URL: http://jira.jboss.com/jira/browse/JBESB-646
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Rosetta
Reporter: Daniel Bevenius
Assigned To: Mark Little
Priority: Minor
The current classes that deal with sending JMS messages, like JMSCourier, do not specify a delivery mode when sending messages. The default is then that the messages are sent with a delivery mode of persistent.
The request (see forum reference) is to be able have the delivery mode configurable so one can avoid the persisting to stable storage.
--
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
17 years, 1 month
[JBoss JIRA] Created: (JBESB-1091) WARN messages when deploying helloworld_ftp_action QS
by Jaroslaw Kijanowski (JIRA)
WARN messages when deploying helloworld_ftp_action QS
-----------------------------------------------------
Key: JBESB-1091
URL: http://jira.jboss.com/jira/browse/JBESB-1091
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Documentation, Examples
Affects Versions: 4.2, 4.2.1 IR1
Reporter: Jaroslaw Kijanowski
Assigned To: Mark Little
When deploying the helloworld_ftp_action QS I get follwoing WARN messages:
16:11:15,426 WARN [ScheduleMapper] Property 'pollLatencySeconds' is DEPRECATED. Please change your configuration to use 'schedule-frequency'.
16:11:15,485 WARN [AbstractFileGateway] No value specified for: max-millis-for-response - This will be an 'inbound-only' gateway
Also the Programmers Guide doesn't mention, that schedule-frequency should be used for a FTP listener.
--
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
17 years, 1 month