Hi,
is disableClientWindow completely implemented?
I can see the attribute in UIOutcomeTarget but i can't see (via file
search) any code that calls the getter or do a
#getAttribute(disableClientWindow).
Regards,
Thomas
Hi Leo,
sounds fine! thanks :)
2013/12/9 Leonardo Uribe lu4...@gmail.com
Hi
I think we could add it as a parameter for f:view tag, for example call it
oamEnableViewPool. The patch proposed uses already an attribute for disable
the pool in some cases, but after doing some experiments
Hi
It seems we forgot to include those lines. The fix should be done in
org.apache.myfaces.shared.renderkit.html.util.OutcomeTargetUtils.getOutcomeTargetHref(...).
Please create an issue for this one in jira.
regards,
Leonardo Uribe
2013/12/9 Thomas Andraschko andraschko.tho...@gmail.com
Thomas Andraschko created MYFACES-3832:
--
Summary: disableClientWindow is not fully implemented
Key: MYFACES-3832
URL: https://issues.apache.org/jira/browse/MYFACES-3832
Project: MyFaces Core
[
https://issues.apache.org/jira/browse/MYFACES-3465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Andraschko resolved MYFACES-3465.
Resolution: Duplicate
JSF 2.2 provides stateless views and MyFaces 2.2 AFAIK
Hi
It seems we have an inconsistency between what was proposed to enable the
view pool and the inclusion of the new parameter.
At start we have this:
org.apache.myfaces.VIEW_POOL_ENABLED (enable / disable for all pages in the
app, by default false)
But if we use an attribute in f:view like
