[esb-issues] [JBoss JIRA] Commented: (JBESB-1282) How does a service work when message payload types are out of scope of the service?
[ http://jira.jboss.com/jira/browse/JBESB-1282?page=comments#action_12385330 ]
Tom Fennelly commented on JBESB-1282:
-------------------------------------
Kurt and I had a chat about this and came to the conclusion that there 2 issues... the
generic issue as described by Kev above (i.e that the message payload is not opaque) and
that there's potentially a general "patterns" type issue re whether or not
messages being sent to the DLQ (or other orthogonal type services) should themselves be
wrapped as payloads to a new message that is itself governed by its own set of contracts
(i.e. between the ServiceInvoker and the DLQ).
How does a service work when message payload types are out of scope
of the service?
-----------------------------------------------------------------------------------
Key: JBESB-1282
URL: http://jira.jboss.com/jira/browse/JBESB-1282
Project: JBoss ESB
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Rosetta, Process flow
Affects Versions: 4.2.1 IR2
Reporter: Tom Fennelly
Assigned To: Kurt Stam
Fix For: 4.2.1 triage
Attachments: stack.txt
Just wondering e.g. the DLQ is running as a centralized service... it's forwarded a
failed message that contains payload types that it knows nothing about... what should
happen?
I'm seeing an exception related to this on th aggregator quickstart. The DLQ service
is running on the AS, while the individual serives are all running standalone. The DLQ
Service has no visibility on the payload types bound to them failed messages that get
delivered to it.
--
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