[
https://issues.apache.org/jira/browse/VELOCITY-837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claude Brisson closed VELOCITY-837.
-----------------------------------
Resolution: Won't Fix
Assignee: Claude Brisson
InvalidReferenceEventHandler.invalidMethod is called whenever the object is
null or the method does not exist. As such, arguments are even not evaluated in
this case.
While I understand that there may be very specific use-cases where this is
needed, I really don't think it's worth it.
Please re-open and describe your use case if you think it's not that exotic.
> Arguments to InvalidReferenceEventHandler.invalidMethod are falsely ignored
> ---------------------------------------------------------------------------
>
> Key: VELOCITY-837
> URL: https://issues.apache.org/jira/browse/VELOCITY-837
> Project: Velocity
> Issue Type: Bug
> Components: Engine
> Affects Versions: 1.7
> Reporter: Peter-Paul Kruijsen
> Assignee: Claude Brisson
> Attachments: VELOCITY-837.patch
>
>
> The arguments to a method that is handled by
> InvalidReferenceEventHandler.invalidMethod are ignored.
> Example: $someObject.myOwnMethod("with", "some", "arguments")
> The arguments are ignored, as per ASTReference.java#306-308 [current HEAD
> revision]:
> String methodName = ((ASTMethod)
> jjtGetChild(failedChild)).getMethodName();
> result = EventHandlerUtil.invalidMethod(rsvc, context, name.toString(),
> previousResult, methodName, uberInfo);
> This method fails to include the arguments of the current ASTMethod.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org
For additional commands, e-mail: dev-h...@velocity.apache.org
