[ http://wso2.org/jira/browse/ESBJAVA-397?page=all ]
Evanthika Amarasiri closed ESBJAVA-397.
---------------------------------------
Assignee: (was: indika kumara)
Fixed in build 1.6-QA-B1. When a new Validate mediator is added to for the
second time, the schema key of the first validate mediator does not get loaded.
The issue will be closed
> If a second validate mediator is added into a sequence, the schema key
> selected for the first validate mediator is loaded automatically
> ---------------------------------------------------------------------------------------------------------------------------------------
>
> Key: ESBJAVA-397
> URL: http://wso2.org/jira/browse/ESBJAVA-397
> Project: WSO2 ESB
> Issue Type: Bug
> Components: Sequences Management
> Affects Versions: NIGHTLY
> Environment: Ubuntu7.04, JDK1.5.0_12, Firefox 2.0.0.9
> Reporter: Evanthika Amarasiri
> Priority: Minor
> Fix For: NIGHTLY
>
>
> Steps to reproduce
> Go to "Sequences" and add a In mediator and then a Validate mediator under
> the In mediator. Next specify a schema key for the Validate mediator. Now add
> an Out mediator and add a Validate mediator for the Out mediator. When the
> Validate mediator is selected, the schema key selected for the In mediator is
> automatically loaded.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://wso2.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
Esb-java-dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/esb-java-dev
