]
Koen Aers resolved JBIDE-5594.
------------------------------
Resolution: Done
I have changed reply-to-originator into replyToOriginator. If somebody could test this
integration that would be great. (revision: 16175)
Wrong xml tag name for replyToOriginator for EsbNotifier
--------------------------------------------------------
Key: JBIDE-5594
URL:
https://jira.jboss.org/jira/browse/JBIDE-5594
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: esb, jbpm
Affects Versions: 3.1.0.M4
Environment: JBDS 3.0 M4 and SOA-P 5.0 Beta1 (probably applies to JBDS 2.x and
SOA-P 4.3 as well)
Reporter: Aaron Pestel
Assignee: Koen Aers
Priority: Blocker
Fix For: 3.1.0.CR2
Attachments: jbpm_esbNotifier_replyToOriginator.png
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
When creating an EsbNotifier for an event in a node-enter (or other locations), when
setting the Reply/Fault option (see screenshot), it adds this XML to the process
definition:
<reply-to-originator>
reply
</reply-to-originator>
Instead, it should be:
<replyToOriginator>
reply
</replyToOriginator>
From the code I've looked at, it seems it should be the reply-to-originator, but that
doesn't work. Only replyToOriginator works. I must be missing something or looking
at wrong source version, but at any rate I think we want to change it to replyToOriginator
in what JBDS puts in the process definition xml.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: