[JBoss JIRA] Created: (JBESB-1984) XSD validation in AbstractProcessingPipeline can fail in legacy environments
3:38 a.m.
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
Priority: Critical
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
8:02 a.m.
New subject: [JBoss JIRA] Updated: (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 updated JBESB-1984:
--------------------------------
Fix Version/s: 4.4 CP1
Assignee: Kevin Conner
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
9:12 a.m.
New subject: [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
4:53 a.m.
New subject: [JBoss JIRA] Work started: (JBESB-1984) XSD validation in AbstractProcessingPipeline can fail in legacy environments
[
https://jira.jboss.org/jira/browse/JBESB-1984?page=com.atlassian.jira.plu...
]
Work on JBESB-1984 started by Kevin Conner.
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
3:54 a.m.
New subject: [JBoss JIRA] Closed: (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 closed JBESB-1984.
-------------------------------
Resolution: Done
I have added support for requestLocation and responseLocation attributes into the
configuration of the actions.
If these are specified then any validation/webservice will use those values for
request/responses.
I have also added deployable unit tests into the qa/junit area to test validation and
location options.
Committed in revision 23548.
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
1:01 p.m.
New subject: [JBoss JIRA] Reopened: (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 reopened JBESB-1984:
---------------------------------
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 CP2
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
1:01 p.m.
New subject: [JBoss JIRA] Closed: (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 closed JBESB-1984.
-------------------------------
Fix Version/s: 4.4 CP2
(was: 4.4 CP1)
Resolution: Done
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 CP2
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
8:29 a.m.
New subject: [JBoss JIRA] Reopened: (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 reopened JBESB-1984:
---------------------------------
This issue is being pulled from the 4.4CP2 release, need to undo the changes.
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 CP2
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
1:39 p.m.
New subject: [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:
-------------------------------------
Changes reverted in revision 24835.
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 CP2
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
1:41 p.m.
New subject: [JBoss JIRA] Updated: (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 updated JBESB-1984:
--------------------------------
Fix Version/s: 4.4 CP3
(was: 4.4 CP2)
Moving to 4.4CP3
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 CP3
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
4:16 a.m.
New subject: [JBoss JIRA] Updated: (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 updated JBESB-1984:
--------------------------------
Fix Version/s: 4.5
(was: 4.4 CP3)
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.5
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
9:31 a.m.
New subject: [JBoss JIRA] Closed: (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 closed JBESB-1984.
-------------------------------
Resolution: Done
Added to trunk in revision 25073.
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.5
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
5779
days inactive
5931
days old
11 comments
2 participants
participants (2)
-
Jiri Pechanec (JIRA) -
Kevin Conner (JIRA)