[ http://issues.apache.org/jira/browse/BEEHIVE-1116?page=all ]
Eddie O'Neil resolved BEEHIVE-1116:
-----------------------------------
Resolution: Won't Fix
Actually, this is working as expected -- the <jsp:include> creates a new
PageContext object, so any implicit objects that are PageContext scoped won't
be available inside of the include. Additionally, neither Struts nor NetUI
dataSource binding read the "actionForm" object from the PageContext.
Instead, it's read from the ServletRequest using a custom attribute key which
is used by Struts and by the NetUI dataSource attribute when data binding.
One possible fix could be to the <netui:form> tag to put the actionForm into
the request's attribute map, but it's possible that could interfere with
existing applications because it would be new behavior occupying a common name
in a Servlet attribute map. It'd be possible to consider it as a possible
enhancement, but please open a separate request for that.
Otherwise, the tags are operating as expected -- ${actionForm} shouldn't work
in a <jsp:include>.
There would be two ways to deal with it -- write a custom JSP tag that puts a
reference in the PageContext as "actionForm" or write scriptlet in the page to
do the same thing.
> CLONE -the netui:form tag doesn't work when the body is in a <jsp:include>
> --------------------------------------------------------------------------
>
> Key: BEEHIVE-1116
> URL: http://issues.apache.org/jira/browse/BEEHIVE-1116
> Project: Beehive
> Type: Bug
> Components: NetUI
> Versions: V1, 1.0.1
> Reporter: Srinivas Surapaneni
> Assignee: Eddie O'Neil
> Fix For: v.next
>
> The <netui:form> tag often uses the "actionForm" implicit object for data
> binding, but in this situation:
> <netui:form>
> <!-- foo-include.jsp -->
> </netui:form>
> foo-include.jsp
>
> <netui:textBox dataSource="actionForm.foo"/>
> the expression in the dataSource attribute is unable to find the actionForm
> object. The problem is that NetUI is unable to find the "actionForm"
> implicit object because it just uses the JspContext's VariableResolver. The
> fix is to wrap this VR in another one that is aware of the "actionForm"
> object.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
