[
http://jira.jboss.com/jira/browse/JBESB-1282?page=comments#action_12385312 ]
Kevin Conner commented on JBESB-1282:
-------------------------------------
The generic problem with this issue is that each service is forced to deserialise the
object when the message is deserialised. It is not just the DLQ which will be affected by
this, all other services will be.
It should be possible to modify the message implementation so that this deserialising is
done on a Just In Time basis, this would solve the generic problem.
This will not happen for the GA though, it will have to make it into the release (CP and
trunk) at a later date.
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