[
https://issues.apache.org/jira/browse/SYNAPSE-102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
indika priyantha kumara reassigned SYNAPSE-102:
-----------------------------------------------
Assignee: indika priyantha kumara
> Dynamic registry not working after second file change
> -----------------------------------------------------
>
> Key: SYNAPSE-102
> URL: https://issues.apache.org/jira/browse/SYNAPSE-102
> Project: Synapse
> Issue Type: Bug
> Components: Core
> Affects Versions: Incubating-M2
> Environment: Windows XP Professional
> Reporter: Tijs Rademakers
> Assigned To: indika priyantha kumara
>
> I use a dynamic registry to implement a validation schema:
> <registry provider="org.apache.synapse.registry.url.SimpleURLRegistry">
> <parameter name="root">file:./repository/conf</parameter>
> <parameter name="cachableDuration">15000</parameter>
> </registry>
> The validation is implemented with the following configuration:
> <validate>
> <schema key="orderxsd.xml" source="//jug:order"
> xmlns:jug="http://atosorigin.com/nljug"/>
> <on-fail>
> <makefault>
> <code value="tns:Receiver"
>
> xmlns:tns="http://www.w3.org/2003/05/soap-envelope"/>
> <reason value="Invalid order request"/>
> </makefault>
> <property name="RESPONSE" value="true"/>
> <header name="To" expression="get-property('ReplyTo')"/>
> </on-fail>
> <send/>
> </validate>
> When I startup Synapse with this configuration it works fine. Then I change
> the orderxsd.xml and after 15 seconds the changes are used by Synapse. So
> here also it is just working fine. But when I change the orderxsd.xml another
> time, the changes are not picked up. It just keeps using the older
> orderxsd.xml version. It seems that after the second file change the registry
> is not processing the changes.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
