History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: OGNL-133
Type: Task Task
Status: Resolved Resolved
Resolution: Fixed
Priority: Minor Minor
Assignee: Jesse Kuhnert
Reporter: Jesse Kuhnert
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
OGNL

bring back old OgnlContext.callMethod parameter

Created: 26/Nov/07 08:46 AM   Updated: 18/Jan/08 01:28 PM
Component/s: Core Runtime
Affects Version/s: 2.7.1
Fix Version/s: 2.7.2

Environment: any


 Description  « Hide
From forum post:


Just notice that callMethod in OgnlRuntime has changed from

public static Object callMethod(OgnlContext context, Object target,
                                    String methodName, String propertyName, Object[] args) throws OgnlException



to

public static Object callMethod(OgnlContext context, Object target,
                                    String methodName, Object[] args)
            throws OgnlException



Is there a reason for this change?

This might break compatibility if we migrate to the next version. Is it possible to still keep the old method signature? or maybe mark it as deprecated first.


 All   Comments   Change History      Sort Order:
Jesse Kuhnert - [18/Jan/08 01:28 PM ]
 Brought back old OgnlRuntime.callMethod method and added deprecated info for it.