Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Not entirely sure what you're describing - it's not quite clear, but see if this helps: </p> <p>This can happen when some Ajax call causes the page to change, but refreshing the page (which isn't bookmarkable) who's urls refers to the expired version causes this exception. I had this problem at one point when we had multiple iframes calling into our wicket app (sorry for the fuzzy explanation - it was a while ago).</p> <p>In the end, for our application, we had to split the different iframe sources into different servlets within web.xml - in order to completely isolate the sessions of the different pages - but that's another story.</p> <p>Try adding this to your wicket application init method.</p> <pre><code>// debug code for fixing session issue (multiple ajax using pages inside // one browser) get().getPageSettings().setAutomaticMultiWindowSupport(true); </code></pre> <p>And check out the documentation here: <a href="http://wicket.apache.org/docs/1.4/org/apache/wicket/jmx/PageSettings.html#getAutomaticMultiWindowSupport()" rel="nofollow noreferrer">http://wicket.apache.org/docs/1.4/org/apache/wicket/jmx/PageSettings.html#getAutomaticMultiWindowSupport()</a></p> <p>Can you show the stack trace?</p> <p>What version of Wicket are you using?</p> <p>There was a bit of a miss-communication in the javadoc prior to 1.4-rc3 as well, patched here: <a href="http://svn.apache.org/viewvc/wicket/trunk/wicket/src/main/java/org/apache/wicket/settings/IPageSettings.java?r1=647167&amp;r2=768578&amp;pathrev=768578&amp;diff_format=h" rel="nofollow noreferrer">http://svn.apache.org/viewvc/wicket/trunk/wicket/src/main/java/org/apache/wicket/settings/IPageSettings.java?r1=647167&amp;r2=768578&amp;pathrev=768578&amp;diff_format=h</a></p> <p>The issue here: <a href="https://issues.apache.org/jira/browse/WICKET-2233" rel="nofollow noreferrer">https://issues.apache.org/jira/browse/WICKET-2233</a></p> <p>Here is the updated comment in the javadoc from IPageSettings:</p> <pre><code>/** * Gets whether Wicket should try to support opening multiple windows for the same session * transparently. If this is true - the default setting -, Wicket tries to detect whether a new * window was opened by a user (e.g. in Internet Explorer by pressing ctrl+n or ctrl+click on a * link), and if it detects that, it creates a new page map for that window on the fly. As a * page map represents the 'history' of one window, each window will then have their own * history. If two windows would share the same page map, the non-bookmarkable links on one * window could refer to stale state after working a while in the other window. * &lt;p&gt; * &lt;strong&gt; Currently, Wicket trying to do this is a best effort that is not completely fail * safe. When the client does not support cookies, support gets tricky and incomplete. See * {@link WebPage}'s internals for the implementation. &lt;/strong&gt; * &lt;/p&gt; * * @return Whether Wicket should try to support multiple windows transparently */ boolean getAutomaticMultiWindowSupport(); </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POProblem in Wicket
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USAntony Stubbs
    1. USAntony Stubbs
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POProblem in Wicket
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI'm using wicket 1.3.5 I did'nt got you. do you want tomcat log or debuging stack trace?
      singulars
      1. PO
      1. USJGC
    2. COTry upgrading to wicket-1.4-rc7. Wicket 1.4 is about to go final any day now, so you may as well migrate to 1.4-rc7 until then. So retest with 1.4-rc7 and see if you still get the same problem. I was asking for the stack trace.
      singulars
      1. PO
      1. USAntony Stubbs
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload