[esb-issues] [JBoss JIRA] Commented: (JBESB-1984) XSD validation in AbstractProcessingPipeline can fail in legacy environments
[
https://jira.jboss.org/jira/browse/JBESB-1984?page=com.atlassian.jira.plu...
]
Kevin Conner commented on JBESB-1984:
-------------------------------------
Using the payload proxy would only be effective if we had a mechanism to specify the
legacy locations for the pipeline and, as there is no easy way to determine these values
from the pipeline, this would require further parameters.
I'll take a quick look into this.
XSD validation in AbstractProcessingPipeline can fail in legacy
environments
----------------------------------------------------------------------------
Key: JBESB-1984
URL: https://jira.jboss.org/jira/browse/JBESB-1984
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Rosetta
Affects Versions: 4.4
Reporter: Jiri Pechanec
Assignee: Kevin Conner
Priority: Critical
Fix For: 4.4 CP1
In AbstractProcessingPipeline the message payload is accessed by direct call of
message.get() for purpose of XSD validations. I thing the access should be via
MessagePayloadProxy class as in other parts of the codebase to work correctly in legacy
environment.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira