Move filter, used for service validator, from pi4soa into Overlord code base ---------------------------------------------------------------------------- Key: SOAG-82 URL: https://jira.jboss.org/jira/browse/SOAG-82 Project: SOA Governance Issue Type: Task Security Level: Public (Everyone can see) Components: Behavioural Monitoring Affects Versions: 1.0 MR2 Reporter: Gary Brown Assignee: Gary Brown Fix For: 1.0 MR2 The service validator for jbossesb was originally developed before Project Overlord was established. However the models and configuration files that the service validators use are stored in the ESB bundle: overlord-cdl-validator.esb When Overlord is installed, the ant script sets up the global filter currently using the class: org.pi4soa.jbossesb.validator.ValidatorFilter As part of a separate task, to enable the service validators to use a "hot deployment" mechanism to update the configuration being monitored, I propose to move the Overlord specific aspects of the service validator into the Overlord code base. The impact of this change will be the configuration of the global filter. This can be updated in the M2 release, so that when it is next installed, it will configure the Overlord version of the filter - however if the ant script is not used to do the upgrade to M2, it is possible that a user will experience a problem. I believe we just need to document this in the release note, to ensure deployment of M2 is done using the ant scripts. -- 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