[ http://wso2.org/jira/browse/WSAS-664?page=all ]
Afkham Azeez resolved WSAS-664.
-------------------------------
Fix Version/s: 2.2
Resolution: Not a bug
The principle is: Database configuration overrides XML config files. If this
change was done before the module information was written to DB, the policy
would have shown up on the UI. If you wish to change the module.xml, you have
to first delete the module from the WSAS repository (Using Delete Module
function), and then add it again as a new module
> The changes done in a policy of the module.xml is not reflected in 'module
> policy' page in the management console
> -----------------------------------------------------------------------------------------------------------------
>
> Key: WSAS-664
> URL: http://wso2.org/jira/browse/WSAS-664
> Project: WSO2 WSAS
> Issue Type: Bug
> Components: core
> Environment: winxp, jdk15, WSAS-2.2-qabuild2
> Reporter: Charitha Kankanamge
> Assigned To: Saminda Wishwajith Abeyruwan
> Priority: Critical
> Fix For: 2.2
>
>
> Steps to reproduce:
> ================
> 1. Stop WSAS
> 2. Open module.xml in wso2throttle-SNAPSHOT.mar
> 3. Uncomment the existing policy and add the following.
> <wsp:Policy xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy";
>
> xmlns:throttle="http://www.wso2.org/products/wso2commons/throttle";>
> <throttle:ThrottleAssertion>
> <wsp:All>
> <throttle:ID throttle:type="IP">Other</throttle:ID>
> <wsp:ExactlyOne>
> <wsp:All>
> <throttle:MaximumCount>4</throttle:MaximumCount>
> <throttle:UnitTime>800000</throttle:UnitTime>
> <throttle:ProhibitTimePeriod
> wsp:Optional="true">10000</throttle:ProhibitTimePeriod>
> </wsp:All>
> <throttle:IsAllow>true</throttle:IsAllow>
> </wsp:ExactlyOne>
> </wsp:All>
> <wsp:All>
> <throttle:ID
> throttle:type="IP">192.168.8.200-192.168.8.222</throttle:ID>
> <wsp:ExactlyOne>
> <wsp:All>
> <throttle:MaximumCount>8</throttle:MaximumCount>
> <throttle:UnitTime>800000</throttle:UnitTime>
> <throttle:ProhibitTimePeriod
> wsp:Optional="true">10</throttle:ProhibitTimePeriod>
> </wsp:All>
> <throttle:IsAllow>true</throttle:IsAllow>
> </wsp:ExactlyOne>
> </wsp:All>
> <wsp:All>
> <throttle:ID throttle:type="IP">192.168.8.201</throttle:ID>
> <wsp:ExactlyOne>
> <wsp:All>
> <throttle:MaximumCount>200</throttle:MaximumCount>
> <throttle:UnitTime>600000</throttle:UnitTime>
> <throttle:ProhibitTimePeriod
> wsp:Optional="true"></throttle:ProhibitTimePeriod>
> </wsp:All>
> <throttle:IsAllow>true</throttle:IsAllow>
> </wsp:ExactlyOne>
> </wsp:All>
> <wsp:All>
> <throttle:ID throttle:type="IP">192.168.8.198</throttle:ID>
> <wsp:ExactlyOne>
> <wsp:All>
> <throttle:MaximumCount>50</throttle:MaximumCount>
> <throttle:UnitTime>500000</throttle:UnitTime>
> <throttle:ProhibitTimePeriod
> wsp:Optional="true"></throttle:ProhibitTimePeriod>
> </wsp:All>
> <throttle:IsAllow>true</throttle:IsAllow>
> </wsp:ExactlyOne>
> </wsp:All>
> </throttle:ThrottleAssertion>
> </wsp:Policy>
> 4. Save the file and restart WSAS
> 5. Go to Modules > wso2throttle > Module Policy page
> 6. Check the policy. It will not show the updated policy.
--
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
_______________________________________________
Wsas-java-dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/wsas-java-dev
