You are viewing a plain text version of this content. The canonical link for it is here.
Posted to pluto-dev@portals.apache.org by "Benjamin Gould (JIRA)" <ji...@apache.org> on 2007/12/12 18:39:43 UTC
[jira] Created: (PLUTO-451) JSP21ExpressionEvaluatorProxy is
causing an exception in Tomcat 6.0 if compiled using JDK 5.0
JSP21ExpressionEvaluatorProxy is causing an exception in Tomcat 6.0 if compiled using JDK 5.0
---------------------------------------------------------------------------------------------
Key: PLUTO-451
URL: https://issues.apache.org/jira/browse/PLUTO-451
Project: Pluto
Issue Type: Bug
Components: portlet container taglibs
Affects Versions: 1.1.5, 1.1-286-COMPATIBILITY, 1.1-286-trunk-merge
Environment: JDK 5.0, Tomcat 6.0
Reporter: Benjamin Gould
Fix For: 1.1.5, 1.1-286-COMPATIBILITY, 1.1-286-trunk-merge
Attachments: taglib-problem.diff
JDK 5.0 changed the signature of Method.invoke() to using varargs for the second argument. The ExpressionEvaluatorProxy for JSP 2.1 passes null, which presumably gets coerced into new Object[] { null } by the compiler. This causes an exception because the runtime arguments for JspApplicationContexts.getExpressionFactory() do not match its signature. Passing an empty array Object[] {} to Method.invoke() resolves this ambiguity.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (PLUTO-451) JSP21ExpressionEvaluatorProxy is
causing an exception in Tomcat 6.0 if compiled using JDK 5.0
Posted by "Craig Doremus (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PLUTO-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12552087 ]
Craig Doremus commented on PLUTO-451:
-------------------------------------
Applied patch to trunk in SVN rev 604444.
> JSP21ExpressionEvaluatorProxy is causing an exception in Tomcat 6.0 if compiled using JDK 5.0
> ---------------------------------------------------------------------------------------------
>
> Key: PLUTO-451
> URL: https://issues.apache.org/jira/browse/PLUTO-451
> Project: Pluto
> Issue Type: Bug
> Components: portlet container taglibs
> Affects Versions: 1.1.5, 1.1-286-COMPATIBILITY, 1.1-286-trunk-merge
> Environment: JDK 5.0, Tomcat 6.0
> Reporter: Benjamin Gould
> Fix For: 1.1.5, 1.1-286-COMPATIBILITY, 1.1-286-trunk-merge
>
> Attachments: taglib-problem.diff
>
>
> JDK 5.0 changed the signature of Method.invoke() to using varargs for the second argument. The ExpressionEvaluatorProxy for JSP 2.1 passes null, which presumably gets coerced into new Object[] { null } by the compiler. This causes an exception because the runtime arguments for JspApplicationContexts.getExpressionFactory() do not match its signature. Passing an empty array Object[] {} to Method.invoke() resolves this ambiguity.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (PLUTO-451) JSP21ExpressionEvaluatorProxy is
causing an exception in Tomcat 6.0 if compiled using JDK 5.0
Posted by "Craig Doremus (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PLUTO-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12552085 ]
Craig Doremus commented on PLUTO-451:
-------------------------------------
Applied patch to 1.1-286-trunk-merge branch in SVN rev 604442. Thank you Ben!
> JSP21ExpressionEvaluatorProxy is causing an exception in Tomcat 6.0 if compiled using JDK 5.0
> ---------------------------------------------------------------------------------------------
>
> Key: PLUTO-451
> URL: https://issues.apache.org/jira/browse/PLUTO-451
> Project: Pluto
> Issue Type: Bug
> Components: portlet container taglibs
> Affects Versions: 1.1.5, 1.1-286-COMPATIBILITY, 1.1-286-trunk-merge
> Environment: JDK 5.0, Tomcat 6.0
> Reporter: Benjamin Gould
> Fix For: 1.1.5, 1.1-286-COMPATIBILITY, 1.1-286-trunk-merge
>
> Attachments: taglib-problem.diff
>
>
> JDK 5.0 changed the signature of Method.invoke() to using varargs for the second argument. The ExpressionEvaluatorProxy for JSP 2.1 passes null, which presumably gets coerced into new Object[] { null } by the compiler. This causes an exception because the runtime arguments for JspApplicationContexts.getExpressionFactory() do not match its signature. Passing an empty array Object[] {} to Method.invoke() resolves this ambiguity.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (PLUTO-451) JSP21ExpressionEvaluatorProxy is
causing an exception in Tomcat 6.0 if compiled using JDK 5.0
Posted by "Craig Doremus (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PLUTO-451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Craig Doremus updated PLUTO-451:
--------------------------------
Fix Version/s: (was: 1.1-286-COMPATIBILITY)
Affects Version/s: (was: 1.1-286-COMPATIBILITY)
JSP21ExpressionEvaluatorProxy is not part of 1.1-286-COMPATIBILITY branch.
> JSP21ExpressionEvaluatorProxy is causing an exception in Tomcat 6.0 if compiled using JDK 5.0
> ---------------------------------------------------------------------------------------------
>
> Key: PLUTO-451
> URL: https://issues.apache.org/jira/browse/PLUTO-451
> Project: Pluto
> Issue Type: Bug
> Components: portlet container taglibs
> Affects Versions: 1.1.5, 1.1-286-trunk-merge
> Environment: JDK 5.0, Tomcat 6.0
> Reporter: Benjamin Gould
> Fix For: 1.1.5, 1.1-286-trunk-merge
>
> Attachments: taglib-problem.diff
>
>
> JDK 5.0 changed the signature of Method.invoke() to using varargs for the second argument. The ExpressionEvaluatorProxy for JSP 2.1 passes null, which presumably gets coerced into new Object[] { null } by the compiler. This causes an exception because the runtime arguments for JspApplicationContexts.getExpressionFactory() do not match its signature. Passing an empty array Object[] {} to Method.invoke() resolves this ambiguity.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (PLUTO-451) JSP21ExpressionEvaluatorProxy is
causing an exception in Tomcat 6.0 if compiled using JDK 5.0
Posted by "Benjamin Gould (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PLUTO-451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Gould updated PLUTO-451:
---------------------------------
Attachment: taglib-problem.diff
> JSP21ExpressionEvaluatorProxy is causing an exception in Tomcat 6.0 if compiled using JDK 5.0
> ---------------------------------------------------------------------------------------------
>
> Key: PLUTO-451
> URL: https://issues.apache.org/jira/browse/PLUTO-451
> Project: Pluto
> Issue Type: Bug
> Components: portlet container taglibs
> Affects Versions: 1.1.5, 1.1-286-COMPATIBILITY, 1.1-286-trunk-merge
> Environment: JDK 5.0, Tomcat 6.0
> Reporter: Benjamin Gould
> Fix For: 1.1.5, 1.1-286-COMPATIBILITY, 1.1-286-trunk-merge
>
> Attachments: taglib-problem.diff
>
>
> JDK 5.0 changed the signature of Method.invoke() to using varargs for the second argument. The ExpressionEvaluatorProxy for JSP 2.1 passes null, which presumably gets coerced into new Object[] { null } by the compiler. This causes an exception because the runtime arguments for JspApplicationContexts.getExpressionFactory() do not match its signature. Passing an empty array Object[] {} to Method.invoke() resolves this ambiguity.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (PLUTO-451) JSP21ExpressionEvaluatorProxy is causing
an exception in Tomcat 6.0 if compiled using JDK 5.0
Posted by "Craig Doremus (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PLUTO-451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Craig Doremus closed PLUTO-451.
-------------------------------
Resolution: Fixed
Patch applied to both branches. Thank you Ben!
> JSP21ExpressionEvaluatorProxy is causing an exception in Tomcat 6.0 if compiled using JDK 5.0
> ---------------------------------------------------------------------------------------------
>
> Key: PLUTO-451
> URL: https://issues.apache.org/jira/browse/PLUTO-451
> Project: Pluto
> Issue Type: Bug
> Components: portlet container taglibs
> Affects Versions: 1.1.5, 1.1-286-trunk-merge
> Environment: JDK 5.0, Tomcat 6.0
> Reporter: Benjamin Gould
> Fix For: 1.1.5, 1.1-286-trunk-merge
>
> Attachments: taglib-problem.diff
>
>
> JDK 5.0 changed the signature of Method.invoke() to using varargs for the second argument. The ExpressionEvaluatorProxy for JSP 2.1 passes null, which presumably gets coerced into new Object[] { null } by the compiler. This causes an exception because the runtime arguments for JspApplicationContexts.getExpressionFactory() do not match its signature. Passing an empty array Object[] {} to Method.invoke() resolves this ambiguity.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.