You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@shale.apache.org by "Stan Zapryanov (JIRA)" <ji...@apache.org> on 2006/12/22 01:02:57 UTC
[jira] Created: (SHALE-371) prerender() executes for ViewController
not rendered when navigating to page/bean not implementing ViewController
prerender() executes for ViewController not rendered when navigating to page/bean not implementing ViewController
-----------------------------------------------------------------------------------------------------------------
Key: SHALE-371
URL: http://issues.apache.org/struts/browse/SHALE-371
Project: Shale
Issue Type: Bug
Components: View
Affects Versions: 1.0.4-SNAPSHOT
Environment: Windows XP Pro, Tomcat 5.5, JDK 1.5.0_04, MyFaces
Reporter: Stan Zapryanov
Not sure if this is a bug but it looks like it.
When navigating to a view (JSF) not implementing the ViewHandler framework from a ViewController t(JSF/bean) that does, currently the prerender() method gets executed on the viewcontroller that you are leaving (that won't get rendered).
My guess is that currently the old FacesConstants.VIEW_NAME_RENDERED entry remains in the request map even though you are not rendering that viewconroller, and that triggers the execution of prerender().
Here is a suggested fix (that I have NOT tested) and I woudn't know if it may brake other stuff..
In the setupViewController() method of the ViewViewHandler class:
vc = vr.resolveVariable(context, viewName);
if (vc == null) {
if (log.isDebugEnabled()) {
log.debug(messages.getMessage("view.noViewController",
new Object[] { viewId, viewName }));
// ----PROPOSED FIX (not tested) ----
context.getExternalContext().getRequestMap() .remove(FacesConstants.VIEW_NAME_RENDERED);
//------END OF FIX-------
}
return;
}
Hope all makes sense and was helpful.
Cheers!
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/struts/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SHALE-371) prerender() executes for
ViewController not rendered when navigating to page/bean not implementing
ViewController
Posted by "Stan Zapryanov (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/struts/browse/SHALE-371?page=comments#action_39151 ]
Stan Zapryanov commented on SHALE-371:
--------------------------------------
I observed the previously described behavior using shale-view.jar and shale-core.jar taken from the shale-framework-20061220.zip that I downloaded from the nightly builds folder.
Looking at the code I see that whenever vr.resolveVariable(context, viewName)==null then the old viewName remains in the map because the method returns without setting a new viewName. Note that the existing code nevertheless sets the new viewName even if vc !=null and vc is NOT instance of ViewController.
If I have to redefine the 'bug' I would say:
Navigating to a viewName for which the ViewControllerMapper returned mapping (name) is not a valid JSF backing bean name would cause the prerender() to execute on the originating viewcontroller bean.
So it seems the "bug" is observed when the viewControllerMapper returns a viewName for which no backing bean is defined in faces-config.xml, disregarding if that bean is an instance of viewcontroller or not.
Simple scenario that would recreate the bug:
/folder1/bean1.jsp with h:commandLink going to /folder2/bean2.jsp
with only folder1$bean1 backing bean defined in faces-config.xml
In that scenario, 'vc' remains null since no bean is defined/found and the setupViewController method returns with 'folder1$bean1' still in the map.
If folder12$bean2 was defined.. no matter if ViewController or not, the map would be containing 'folder12$bean2' as viewName at the end of the method, and prerender() would not be called on 'folder1$bean1'.
Sorry I didn't get it quite right in my initial analysis. Hopefully this time it should make more sense.
Happy holidays!
> prerender() executes for ViewController not rendered when navigating to page/bean not implementing ViewController
> -----------------------------------------------------------------------------------------------------------------
>
> Key: SHALE-371
> URL: http://issues.apache.org/struts/browse/SHALE-371
> Project: Shale
> Issue Type: Bug
> Components: View
> Affects Versions: 1.0.4-SNAPSHOT
> Environment: Windows XP Pro, Tomcat 5.5, JDK 1.5.0_04, MyFaces
> Reporter: Stan Zapryanov
> Assigned To: Craig McClanahan
> Fix For: 1.0.4-SNAPSHOT
>
>
> Not sure if this is a bug but it looks like it.
> When navigating to a view (JSF) not implementing the ViewHandler framework from a ViewController t(JSF/bean) that does, currently the prerender() method gets executed on the viewcontroller that you are leaving (that won't get rendered).
> My guess is that currently the old FacesConstants.VIEW_NAME_RENDERED entry remains in the request map even though you are not rendering that viewconroller, and that triggers the execution of prerender().
> Here is a suggested fix that appears to correct the problem described but I woudn't know if it may brake other stuff.. :
> In the setupViewController() method of the ViewViewHandler class:
> vc = vr.resolveVariable(context, viewName);
> if (vc == null) {
> if (log.isDebugEnabled()) {
> log.debug(messages.getMessage("view.noViewController",
> new Object[] { viewId, viewName }));
> }
> // ---- START OF PROPOSED FIX
> context.getExternalContext().getRequestMap() .remove(FacesConstants.VIEW_NAME_RENDERED);
> //------END OF FIX-------
> return;
> }
> Hope all makes sense and was helpful.
> Cheers!
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/struts/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SHALE-371) prerender() executes for
ViewController not rendered when navigating to page/bean not implementing
ViewController
Posted by "Craig McClanahan (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/struts/browse/SHALE-371?page=comments#action_39153 ]
Craig McClanahan commented on SHALE-371:
----------------------------------------
OK, that makes sense ... and my current test case doesn't cover that combination. I'll dig back in -- thanks for the follow-up details!
> prerender() executes for ViewController not rendered when navigating to page/bean not implementing ViewController
> -----------------------------------------------------------------------------------------------------------------
>
> Key: SHALE-371
> URL: http://issues.apache.org/struts/browse/SHALE-371
> Project: Shale
> Issue Type: Bug
> Components: View
> Affects Versions: 1.0.4-SNAPSHOT
> Environment: Windows XP Pro, Tomcat 5.5, JDK 1.5.0_04, MyFaces
> Reporter: Stan Zapryanov
> Assigned To: Craig McClanahan
> Fix For: 1.0.4-SNAPSHOT
>
>
> Not sure if this is a bug but it looks like it.
> When navigating to a view (JSF) not implementing the ViewHandler framework from a ViewController t(JSF/bean) that does, currently the prerender() method gets executed on the viewcontroller that you are leaving (that won't get rendered).
> My guess is that currently the old FacesConstants.VIEW_NAME_RENDERED entry remains in the request map even though you are not rendering that viewconroller, and that triggers the execution of prerender().
> Here is a suggested fix that appears to correct the problem described but I woudn't know if it may brake other stuff.. :
> In the setupViewController() method of the ViewViewHandler class:
> vc = vr.resolveVariable(context, viewName);
> if (vc == null) {
> if (log.isDebugEnabled()) {
> log.debug(messages.getMessage("view.noViewController",
> new Object[] { viewId, viewName }));
> }
> // ---- START OF PROPOSED FIX
> context.getExternalContext().getRequestMap() .remove(FacesConstants.VIEW_NAME_RENDERED);
> //------END OF FIX-------
> return;
> }
> Hope all makes sense and was helpful.
> Cheers!
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/struts/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SHALE-371) prerender() executes for ViewController
not rendered when navigating to page/bean not implementing ViewController
Posted by "Craig McClanahan (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/struts/browse/SHALE-371?page=all ]
Craig McClanahan updated SHALE-371:
-----------------------------------
Fix Version/s: 1.0.4-SNAPSHOT
This is indeed a bug ... the view controller interface promises to call prerender() only for the view that will actually be rendered, so calling it on the "from" view in this case is definitely wrong. On the surface, your fix looks good ... I'll test it before committing. This fix is needed for 1.0.4, but should not take too long.
> prerender() executes for ViewController not rendered when navigating to page/bean not implementing ViewController
> -----------------------------------------------------------------------------------------------------------------
>
> Key: SHALE-371
> URL: http://issues.apache.org/struts/browse/SHALE-371
> Project: Shale
> Issue Type: Bug
> Components: View
> Affects Versions: 1.0.4-SNAPSHOT
> Environment: Windows XP Pro, Tomcat 5.5, JDK 1.5.0_04, MyFaces
> Reporter: Stan Zapryanov
> Assigned To: Craig McClanahan
> Fix For: 1.0.4-SNAPSHOT
>
>
> Not sure if this is a bug but it looks like it.
> When navigating to a view (JSF) not implementing the ViewHandler framework from a ViewController t(JSF/bean) that does, currently the prerender() method gets executed on the viewcontroller that you are leaving (that won't get rendered).
> My guess is that currently the old FacesConstants.VIEW_NAME_RENDERED entry remains in the request map even though you are not rendering that viewconroller, and that triggers the execution of prerender().
> Here is a suggested fix that appears to correct the problem described but I woudn't know if it may brake other stuff.. :
> In the setupViewController() method of the ViewViewHandler class:
> vc = vr.resolveVariable(context, viewName);
> if (vc == null) {
> if (log.isDebugEnabled()) {
> log.debug(messages.getMessage("view.noViewController",
> new Object[] { viewId, viewName }));
> }
> // ---- START OF PROPOSED FIX
> context.getExternalContext().getRequestMap() .remove(FacesConstants.VIEW_NAME_RENDERED);
> //------END OF FIX-------
> return;
> }
> Hope all makes sense and was helpful.
> Cheers!
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/struts/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SHALE-371) prerender() executes for
ViewController not rendered when navigating to page/bean not implementing
ViewController
Posted by "Craig McClanahan (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/struts/browse/SHALE-371?page=comments#action_39148 ]
Craig McClanahan commented on SHALE-371:
----------------------------------------
Hmm ... what version of Shale are you seeing these problems with? I just added test cases to the shale-test-view and shale-test-tiger applications for validating the correct behavior of this condition, and I cannot reproduce the behavior you report -- for me, prerender() is *not* being called for the "from" page.
> prerender() executes for ViewController not rendered when navigating to page/bean not implementing ViewController
> -----------------------------------------------------------------------------------------------------------------
>
> Key: SHALE-371
> URL: http://issues.apache.org/struts/browse/SHALE-371
> Project: Shale
> Issue Type: Bug
> Components: View
> Affects Versions: 1.0.4-SNAPSHOT
> Environment: Windows XP Pro, Tomcat 5.5, JDK 1.5.0_04, MyFaces
> Reporter: Stan Zapryanov
> Assigned To: Craig McClanahan
> Fix For: 1.0.4-SNAPSHOT
>
>
> Not sure if this is a bug but it looks like it.
> When navigating to a view (JSF) not implementing the ViewHandler framework from a ViewController t(JSF/bean) that does, currently the prerender() method gets executed on the viewcontroller that you are leaving (that won't get rendered).
> My guess is that currently the old FacesConstants.VIEW_NAME_RENDERED entry remains in the request map even though you are not rendering that viewconroller, and that triggers the execution of prerender().
> Here is a suggested fix that appears to correct the problem described but I woudn't know if it may brake other stuff.. :
> In the setupViewController() method of the ViewViewHandler class:
> vc = vr.resolveVariable(context, viewName);
> if (vc == null) {
> if (log.isDebugEnabled()) {
> log.debug(messages.getMessage("view.noViewController",
> new Object[] { viewId, viewName }));
> }
> // ---- START OF PROPOSED FIX
> context.getExternalContext().getRequestMap() .remove(FacesConstants.VIEW_NAME_RENDERED);
> //------END OF FIX-------
> return;
> }
> Hope all makes sense and was helpful.
> Cheers!
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/struts/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Assigned: (SHALE-371) prerender() executes for
ViewController not rendered when navigating to page/bean not implementing
ViewController
Posted by "Craig McClanahan (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/struts/browse/SHALE-371?page=all ]
Craig McClanahan reassigned SHALE-371:
--------------------------------------
Assignee: Craig McClanahan
> prerender() executes for ViewController not rendered when navigating to page/bean not implementing ViewController
> -----------------------------------------------------------------------------------------------------------------
>
> Key: SHALE-371
> URL: http://issues.apache.org/struts/browse/SHALE-371
> Project: Shale
> Issue Type: Bug
> Components: View
> Affects Versions: 1.0.4-SNAPSHOT
> Environment: Windows XP Pro, Tomcat 5.5, JDK 1.5.0_04, MyFaces
> Reporter: Stan Zapryanov
> Assigned To: Craig McClanahan
>
> Not sure if this is a bug but it looks like it.
> When navigating to a view (JSF) not implementing the ViewHandler framework from a ViewController t(JSF/bean) that does, currently the prerender() method gets executed on the viewcontroller that you are leaving (that won't get rendered).
> My guess is that currently the old FacesConstants.VIEW_NAME_RENDERED entry remains in the request map even though you are not rendering that viewconroller, and that triggers the execution of prerender().
> Here is a suggested fix that appears to correct the problem described but I woudn't know if it may brake other stuff.. :
> In the setupViewController() method of the ViewViewHandler class:
> vc = vr.resolveVariable(context, viewName);
> if (vc == null) {
> if (log.isDebugEnabled()) {
> log.debug(messages.getMessage("view.noViewController",
> new Object[] { viewId, viewName }));
> }
> // ---- START OF PROPOSED FIX
> context.getExternalContext().getRequestMap() .remove(FacesConstants.VIEW_NAME_RENDERED);
> //------END OF FIX-------
> return;
> }
> Hope all makes sense and was helpful.
> Cheers!
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/struts/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (SHALE-371) prerender() executes for
ViewController not rendered when navigating to page/bean not implementing
ViewController
Posted by "Craig McClanahan (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/struts/browse/SHALE-371?page=all ]
Craig McClanahan resolved SHALE-371.
------------------------------------
Resolution: Fixed
Stan, your analysis is spot on. I've added test cases (for both shale-test-view and shale-test-tiger) to execute your test case, and added your one-line fix to make it work correctly. This will be available on the 20061224 nightly build, and the upcoming 1.0.4 release. Thanks for the patch, and the patience to get the details through my head :-).
> prerender() executes for ViewController not rendered when navigating to page/bean not implementing ViewController
> -----------------------------------------------------------------------------------------------------------------
>
> Key: SHALE-371
> URL: http://issues.apache.org/struts/browse/SHALE-371
> Project: Shale
> Issue Type: Bug
> Components: View
> Affects Versions: 1.0.4-SNAPSHOT
> Environment: Windows XP Pro, Tomcat 5.5, JDK 1.5.0_04, MyFaces
> Reporter: Stan Zapryanov
> Assigned To: Craig McClanahan
> Fix For: 1.0.4-SNAPSHOT
>
>
> Not sure if this is a bug but it looks like it.
> When navigating to a view (JSF) not implementing the ViewHandler framework from a ViewController t(JSF/bean) that does, currently the prerender() method gets executed on the viewcontroller that you are leaving (that won't get rendered).
> My guess is that currently the old FacesConstants.VIEW_NAME_RENDERED entry remains in the request map even though you are not rendering that viewconroller, and that triggers the execution of prerender().
> Here is a suggested fix that appears to correct the problem described but I woudn't know if it may brake other stuff.. :
> In the setupViewController() method of the ViewViewHandler class:
> vc = vr.resolveVariable(context, viewName);
> if (vc == null) {
> if (log.isDebugEnabled()) {
> log.debug(messages.getMessage("view.noViewController",
> new Object[] { viewId, viewName }));
> }
> // ---- START OF PROPOSED FIX
> context.getExternalContext().getRequestMap() .remove(FacesConstants.VIEW_NAME_RENDERED);
> //------END OF FIX-------
> return;
> }
> Hope all makes sense and was helpful.
> Cheers!
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/struts/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SHALE-371) prerender() executes for ViewController
not rendered when navigating to page/bean not implementing ViewController
Posted by "Stan Zapryanov (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/struts/browse/SHALE-371?page=all ]
Stan Zapryanov updated SHALE-371:
---------------------------------
Description:
Not sure if this is a bug but it looks like it.
When navigating to a view (JSF) not implementing the ViewHandler framework from a ViewController t(JSF/bean) that does, currently the prerender() method gets executed on the viewcontroller that you are leaving (that won't get rendered).
My guess is that currently the old FacesConstants.VIEW_NAME_RENDERED entry remains in the request map even though you are not rendering that viewconroller, and that triggers the execution of prerender().
Here is a suggested fix (that I have NOT tested) and I woudn't know if it may brake other stuff..
In the setupViewController() method of the ViewViewHandler class:
vc = vr.resolveVariable(context, viewName);
if (vc == null) {
if (log.isDebugEnabled()) {
log.debug(messages.getMessage("view.noViewController",
new Object[] { viewId, viewName }));
}
// ----PROPOSED FIX (not tested) ----
context.getExternalContext().getRequestMap() .remove(FacesConstants.VIEW_NAME_RENDERED);
//------END OF FIX-------
return;
}
Hope all makes sense and was helpful.
Cheers!
was:
Not sure if this is a bug but it looks like it.
When navigating to a view (JSF) not implementing the ViewHandler framework from a ViewController t(JSF/bean) that does, currently the prerender() method gets executed on the viewcontroller that you are leaving (that won't get rendered).
My guess is that currently the old FacesConstants.VIEW_NAME_RENDERED entry remains in the request map even though you are not rendering that viewconroller, and that triggers the execution of prerender().
Here is a suggested fix (that I have NOT tested) and I woudn't know if it may brake other stuff..
In the setupViewController() method of the ViewViewHandler class:
vc = vr.resolveVariable(context, viewName);
if (vc == null) {
if (log.isDebugEnabled()) {
log.debug(messages.getMessage("view.noViewController",
new Object[] { viewId, viewName }));
// ----PROPOSED FIX (not tested) ----
context.getExternalContext().getRequestMap() .remove(FacesConstants.VIEW_NAME_RENDERED);
//------END OF FIX-------
}
return;
}
Hope all makes sense and was helpful.
Cheers!
> prerender() executes for ViewController not rendered when navigating to page/bean not implementing ViewController
> -----------------------------------------------------------------------------------------------------------------
>
> Key: SHALE-371
> URL: http://issues.apache.org/struts/browse/SHALE-371
> Project: Shale
> Issue Type: Bug
> Components: View
> Affects Versions: 1.0.4-SNAPSHOT
> Environment: Windows XP Pro, Tomcat 5.5, JDK 1.5.0_04, MyFaces
> Reporter: Stan Zapryanov
>
> Not sure if this is a bug but it looks like it.
> When navigating to a view (JSF) not implementing the ViewHandler framework from a ViewController t(JSF/bean) that does, currently the prerender() method gets executed on the viewcontroller that you are leaving (that won't get rendered).
> My guess is that currently the old FacesConstants.VIEW_NAME_RENDERED entry remains in the request map even though you are not rendering that viewconroller, and that triggers the execution of prerender().
> Here is a suggested fix (that I have NOT tested) and I woudn't know if it may brake other stuff..
> In the setupViewController() method of the ViewViewHandler class:
> vc = vr.resolveVariable(context, viewName);
> if (vc == null) {
> if (log.isDebugEnabled()) {
> log.debug(messages.getMessage("view.noViewController",
> new Object[] { viewId, viewName }));
> }
> // ----PROPOSED FIX (not tested) ----
> context.getExternalContext().getRequestMap() .remove(FacesConstants.VIEW_NAME_RENDERED);
> //------END OF FIX-------
> return;
> }
> Hope all makes sense and was helpful.
> Cheers!
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/struts/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SHALE-371) prerender() executes for ViewController
not rendered when navigating to page/bean not implementing ViewController
Posted by "Stan Zapryanov (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/struts/browse/SHALE-371?page=all ]
Stan Zapryanov updated SHALE-371:
---------------------------------
Description:
Not sure if this is a bug but it looks like it.
When navigating to a view (JSF) not implementing the ViewHandler framework from a ViewController t(JSF/bean) that does, currently the prerender() method gets executed on the viewcontroller that you are leaving (that won't get rendered).
My guess is that currently the old FacesConstants.VIEW_NAME_RENDERED entry remains in the request map even though you are not rendering that viewconroller, and that triggers the execution of prerender().
Here is a suggested fix that appears to correct the problem described but I woudn't know if it may brake other stuff.. :
In the setupViewController() method of the ViewViewHandler class:
vc = vr.resolveVariable(context, viewName);
if (vc == null) {
if (log.isDebugEnabled()) {
log.debug(messages.getMessage("view.noViewController",
new Object[] { viewId, viewName }));
}
// ---- START OF PROPOSED FIX
context.getExternalContext().getRequestMap() .remove(FacesConstants.VIEW_NAME_RENDERED);
//------END OF FIX-------
return;
}
Hope all makes sense and was helpful.
Cheers!
was:
Not sure if this is a bug but it looks like it.
When navigating to a view (JSF) not implementing the ViewHandler framework from a ViewController t(JSF/bean) that does, currently the prerender() method gets executed on the viewcontroller that you are leaving (that won't get rendered).
My guess is that currently the old FacesConstants.VIEW_NAME_RENDERED entry remains in the request map even though you are not rendering that viewconroller, and that triggers the execution of prerender().
Here is a suggested fix (that I have NOT tested) and I woudn't know if it may brake other stuff..
In the setupViewController() method of the ViewViewHandler class:
vc = vr.resolveVariable(context, viewName);
if (vc == null) {
if (log.isDebugEnabled()) {
log.debug(messages.getMessage("view.noViewController",
new Object[] { viewId, viewName }));
}
// ----PROPOSED FIX (not tested) ----
context.getExternalContext().getRequestMap() .remove(FacesConstants.VIEW_NAME_RENDERED);
//------END OF FIX-------
return;
}
Hope all makes sense and was helpful.
Cheers!
> prerender() executes for ViewController not rendered when navigating to page/bean not implementing ViewController
> -----------------------------------------------------------------------------------------------------------------
>
> Key: SHALE-371
> URL: http://issues.apache.org/struts/browse/SHALE-371
> Project: Shale
> Issue Type: Bug
> Components: View
> Affects Versions: 1.0.4-SNAPSHOT
> Environment: Windows XP Pro, Tomcat 5.5, JDK 1.5.0_04, MyFaces
> Reporter: Stan Zapryanov
>
> Not sure if this is a bug but it looks like it.
> When navigating to a view (JSF) not implementing the ViewHandler framework from a ViewController t(JSF/bean) that does, currently the prerender() method gets executed on the viewcontroller that you are leaving (that won't get rendered).
> My guess is that currently the old FacesConstants.VIEW_NAME_RENDERED entry remains in the request map even though you are not rendering that viewconroller, and that triggers the execution of prerender().
> Here is a suggested fix that appears to correct the problem described but I woudn't know if it may brake other stuff.. :
> In the setupViewController() method of the ViewViewHandler class:
> vc = vr.resolveVariable(context, viewName);
> if (vc == null) {
> if (log.isDebugEnabled()) {
> log.debug(messages.getMessage("view.noViewController",
> new Object[] { viewId, viewName }));
> }
> // ---- START OF PROPOSED FIX
> context.getExternalContext().getRequestMap() .remove(FacesConstants.VIEW_NAME_RENDERED);
> //------END OF FIX-------
> return;
> }
> Hope all makes sense and was helpful.
> Cheers!
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/struts/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira