Hi Anil,
I have tested jbossxacml-2.0.3.CR4.jar against our policies. Now our issue with
HigherOrderFunction is solved!
Thanks a lot for your very fast reaction.
Best regards, Joerg
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4221324#4221324
Reply to the
Please pick the March 24th snapshot from the location above.
The CR4 release tomorrow will contain it.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4220718#4220718
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4220718
Thanks for the policy. I can reproduce the issue. I will upload a snapshot
later in the day with the fix and the CR4 release will be tomorrow.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4220669#4220669
Reply to the post :
http://www.jboss.org/index.html?m
Hi Anil,
The issue can be reproduced using "anyURI-regexp-match" inside an "any-of"
function. In that case the following fix in HigherOrderFunction of the original
sunxacml implementation is needed:
http://sunxacml.svn.sourceforge.net/viewvc/sunxacml/trunk/sunxacml/com/sun/xacml/cond/HigherOrde
Hi Karin,
I cannot reproduce the issue with a policy that I mashed up.
http://anonsvn.jboss.org/repos/jbossas/projects/security/security-xacml/trunk/jboss-sunxacml/src/test/resources/policies/function-match/function-match-policy-01.xml
I have been fixing bugs since 2.0.3.CR3. Not sure if that h
