Hey Reza, I would prefer a single patch file IF eclipse behaved as expected. I always end up having some trouble applying patch files via eclipse and I end up manually adding the changes at times. Seperate patch files therefore turn out to be easier. Thanks Neeraj ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ "The light at the end of the tunnel...may be you"
Neeraj Joshi WebSphere XD - Compute Grid AIM, IBM Apache Imperius - http://incubator.apache.org/imperius ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ "Reza Asadollahi (JIRA)" <[EMAIL PROTECTED]> 09/17/2008 02:01 PM Please respond to imperius-dev@incubator.apache.org To imperius-dev@incubator.apache.org cc Subject [jira] Commented: (IMPERIUS-18) Failure to find the proper method of the anchor object during policy execution [ https://issues.apache.org/jira/browse/IMPERIUS-18?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12631862#action_12631862 ] Reza Asadollahi commented on IMPERIUS-18: ----------------------------------------- Hey Neeraj, Thanks for applying the patch. Regarding the change in AnchorMethodInvokeAction.execute method signature to throw SPLException, I actually changed the ActionBlock.execute method signature and all classes that implement it. Is it ok if I create one patch file for all files changed? Or you'd like to have one patch file for each individual file. Thanks, > Failure to find the proper method of the anchor object during policy execution > ------------------------------------------------------------------------------ > > Key: IMPERIUS-18 > URL: https://issues.apache.org/jira/browse/IMPERIUS-18 > Project: Imperius > Issue Type: Bug > Reporter: Reza Asadollahi > Assignee: Bill Stoddard > Priority: Critical > Attachments: AnchorMethodInvokeAction_patch.txt, Equal_patch.txt, Greater_patch.txt, GreaterOrEqual_patch.txt, JavaActuatorImpl_Patch.txt, Less_patch.txt, LessOrEqual_patch.txt, LogicalAnd_patch.txt, PolicyEvaluatorImpl_patch.txt, SPLException_patch.txt > > > An anchor object has a method named foo with the following signature: > public void foo(Object o) > if this method is used in a SPL policy as foo("test"), the policy will fail to execute with the following exception since it looks for method foo(java.lang.String) and can not find it. > org.apache.imperius.spl.parser.exceptions.SPLException: org.starmx.MyClass.foo(java.lang.String) > at org.apache.imperius.javaspl.JavaActuatorImpl.invokeMethod(JavaActuatorImpl.java:115) > at org.apache.imperius.spl.parser.statements.actions.impl.AnchorMethodInvokeAction.invokeClassMethod(AnchorMethodInvokeAction.java:362) > at org.apache.imperius.spl.parser.compiler.IdentPrimaryTuple.evaluate(IdentPrimaryTuple.java:152) > at org.apache.imperius.spl.parser.statements.actions.impl.AnchorMethodInvokeAction.execute(AnchorMethodInvokeAction.java:170) > at org.apache.imperius.spl.parser.statements.impl.PolicyDefinition.evaluate(PolicyDefinition.java:224) > at org.apache.imperius.spl.parser.statements.impl.SPLPolicy._evaluatePolicies(SPLPolicy.java:151) > at org.apache.imperius.spl.parser.statements.impl.SPLPolicy.evaluate(SPLPolicy.java:362) > at org.apache.imperius.spl.evaluator.impl.PolicyEvaluatorImpl.evaluatePolicy(PolicyEvaluatorImpl.java:118) > at org.apache.imperius.spl.manager.impl.PolicyManagerImpl.evaluatePolicy(PolicyManagerImpl.java:209) > at org.apache.imperius.javaspl.Java_SPLPolicyRuleProvider.executePolicy(Java_SPLPolicyRuleProvider.java:134) > This is a serious problem since it doesn't allow to call any method that has the super class of the real parameter in its signature. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
