You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Live Nono (JIRA)" <ji...@apache.org> on 2009/04/21 23:50:47 UTC
[jira] Created: (WICKET-2233)
getPageSettings().setAutomaticMultiWindowSupport(true); is said to be
enabled by default in its javadoc but isn't
getPageSettings().setAutomaticMultiWindowSupport(true); is said to be enabled by default in its javadoc but isn't
------------------------------------------------------------------------------------------------------------------
Key: WICKET-2233
URL: https://issues.apache.org/jira/browse/WICKET-2233
Project: Wicket
Issue Type: Bug
Reporter: Live Nono
Priority: Minor
More info there : http://www.nabble.com/LinkTree-breaks-when-using-twice-instances-of-Firefox-(with--Unexpected-RuntimeException)-td23098156.html
I don't know whether it's just about changing the javadoc or fixing the current default...
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (WICKET-2233)
getPageSettings().setAutomaticMultiWindowSupport(true); is said to be
enabled by default in its javadoc but isn't
Posted by "Igor Vaynberg (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-2233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Igor Vaynberg resolved WICKET-2233.
-----------------------------------
Resolution: Fixed
Fix Version/s: 1.4-RC3
Assignee: Igor Vaynberg
added javadoc clarification
> getPageSettings().setAutomaticMultiWindowSupport(true); is said to be enabled by default in its javadoc but isn't
> ------------------------------------------------------------------------------------------------------------------
>
> Key: WICKET-2233
> URL: https://issues.apache.org/jira/browse/WICKET-2233
> Project: Wicket
> Issue Type: Bug
> Reporter: Live Nono
> Assignee: Igor Vaynberg
> Priority: Minor
> Fix For: 1.4-RC3
>
>
> More info there : http://www.nabble.com/LinkTree-breaks-when-using-twice-instances-of-Firefox-(with--Unexpected-RuntimeException)-td23098156.html
> I don't know whether it's just about changing the javadoc or fixing the current default...
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (WICKET-2233)
getPageSettings().setAutomaticMultiWindowSupport(true); is said to be
enabled by default in its javadoc but isn't
Posted by "Juergen Donnerstag (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-2233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12702455#action_12702455 ]
Juergen Donnerstag commented on WICKET-2233:
--------------------------------------------
What happens:
Settings.java
...
private boolean automaticMultiWindowSupport = true;
...
but SecondLevelCacheSessionStore.java
// turn automatic multi window support off by default, as we don't
// really
// need to be afraid to run out of history with this implementation.
// note that the session store is created before Application#init is
// called, so if users set this setting explicitly, it'll be overridden
// (and that's exactly what we want: provide a better default, but not
// forcing people to do away with this feature).
Application.get().getPageSettings().setAutomaticMultiWindowSupport(false);
which is the default: WebApplication.java
protected ISessionStore newSessionStore()
{
return new SecondLevelCacheSessionStore(this, new DiskPageStore());
}
> getPageSettings().setAutomaticMultiWindowSupport(true); is said to be enabled by default in its javadoc but isn't
> ------------------------------------------------------------------------------------------------------------------
>
> Key: WICKET-2233
> URL: https://issues.apache.org/jira/browse/WICKET-2233
> Project: Wicket
> Issue Type: Bug
> Reporter: Live Nono
> Priority: Minor
>
> More info there : http://www.nabble.com/LinkTree-breaks-when-using-twice-instances-of-Firefox-(with--Unexpected-RuntimeException)-td23098156.html
> I don't know whether it's just about changing the javadoc or fixing the current default...
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.