Okay, I'll look into it as soon as i get some time.

-Matej

On 5/3/07, RedFury <[EMAIL PROTECTED]> wrote:
>
>
> Ok I have spent a fair amount of time putting together a wicket example of
> my two problems.  It is a netbeans project but pretty bare-bones so it
> should be pretty easy to get working in other IDE's.  I have attached it
> here so if any of the wicket-gurus out there would take a quick look I would
> very much appreciate it.
>
> Basically there were two problems and this is how I reproduced them:
>
> Problem 1 - Ajax failing to update (requesting wrong page version maybe..?)
>
> Happens on all browsers (IE, Firefox, opera tested.)
> Open up firefox and paste app URL
> Click on Tab 3 (ajax request will put tab 3 up)
> Click back on Tab 1
> Open up second tab and paste URL
> Go back to first tab and look at Wicket Ajax debug.  Update is failling
> because the server is sending Component ID's which don't exist on the
> client.  They've got their pages mixed up.
>
> ----------------------------------------------------------------------------------------
>
> Problem 2 - Back button -> Forward button failure
>
> Happens only on Firefox (I think) so maybe a browser problem ?
> Open up firefox and go to any site, I usually used google
> Paste app URL into browser.
> Click on Tab 3
> Click the back button to go back to google.
> Wait a while for page to 'expire'. Doesn't seem to take more than about 30
> secs - 1min.
> Click forward.   Server is contacted and page reset, showing tab 1.
> Click on a subtab of tab1.  You'll get an error saying the page couldn't
> find the component/behavior, as if it still
> thinks it is on Tab 3 (?)
>
> Anyways, thats about all I can add for now.  If someone would be so kind as
> to have a quick look at the attached project and offer some feedback, that
> would be awesome.
>
> Cheers,
> Dean
>
>
>
> RedFury wrote:
> >
> > Sorry for replying to my own post, but I found another problem which seems
> > to be related or the same thing.
> > I'm not sure if its wicket 1.3 or my code but I'm going to try to write a
> > simple app to demonstrate the problem then submit it here.
> >
> > Anyways, if I open my browser (firefox latest, fully updated) and start on
> > a different, non-wicket page (say google)  Then go to my wicket app.   I
> > have a bunch of ajaxed tabs which start out on tab 1 when the page loads.
> > Each tab loads in a bunch of new html components in a panel, replacing the
> > old panel.  So I click on tab 2 and new html gets ajaxed in, replacing a
> > lot of the old components in tab 1.   Then I click 'back' to go back to
> > the non-wicket page.  I sit on that page until the wicket-page has timed
> > out, then click forward now.  Now the server loads my page again, and its
> > reset back to its original form with tab 1 showing.  However, if I try to
> > perform an ajax action within that tab, I get a server error telling me
> > that it couldn't find the panel, because the server has got some weird
> > state where even though it fetched me the reset page, it still thinks I'm
> > on the modified page when I submit an ajax request.
> >
> > All this is very weird and probably doesn't make much sense without a
> > solid example, so I'm going to try to put one together and hopefully some
> > wicket guru can find out if its a bug or something I'm doing in my code
> > which I shouldn't be.
> >
> > Cheers,
> > Dean
> >
> >
> > RedFury wrote:
> >>
> >> Hi Matej,
> >>
> >> I got the latest SVN trunk and it did indeed fix the 'session expired'
> >> problem.  However, another problem with opening a new tab still persists
> >> and I think it may have to do with page cloning combined with dynamic
> >> ajax page updates.  I will try to explain as best I can but I'm not
> >> overly familiar with the internal workings of wicket.
> >>
> >> My app has 1 main page, and everything else is loaded dynamically using
> >> Ajax.  I perform the following steps after deploying my app:
> >>
> >> -Open firefox and paste the link to my wicket servlet.  A new page, Page
> >> A, is created on the server using PageMap A.  By default, my "Page A" is
> >> constructed with 5 tab options, with the contents for Tab 1 loaded.
> >>
> >> -I click on tab 2 in Page A.  This sends of an AJAX request which
> >> dynamically replaces panels on Page A (specifically replaces
> >> tab-content-panel-1 with tab-content_panel-2.)
> >>
> >> - I open a new tab and paste the servlet link into it.  The following
> >> occurs:
> >>
> >> - Two new pages appear to be created (at least my "Page A" constructor is
> >> called twice), lets call them Page B and Page C.  Page B uses Pagemap A
> >> again, and by default is created with Tab 1 loaded again.  Page C uses a
> >> new pagemap (PageMap B) and all subsequent ajax requests from the second
> >> tab appear to go to Page C, as you would expect.
> >>
> >> - Back in Tab A, the next ajax request is activated and this is when
> >> things go bad ... I get errors because its trying to update components
> >> that don't exist on the page.  Upon inspection, what is happening is that
> >> the AJAX request from Tab 1 seems to be targetting a different page, with
> >> different page state, quite possibly page B.   It's AJAX error spits out
> >> the ID's of things it can't find and they are all ID's that belong to
> >> components inside Tab-Panel-1.  So the AJAX request to the server grabs a
> >> page which thinks its on Tab1, but in actual fact, according  to the
> >> client, we are on page 2.
> >>
> >> I hope this is enough information to go on,
> >> I've searched my code thoroughly and am not sure what else I could do to
> >> stop this issue.  It seems like wicket is replacing my 'active page' for
> >> Tab 1, but replacing it with a newly constructed page and not taking into
> >> account any ajax changes the user may have already made to that page.
> >>
> >> If you, or anyone else, could assist me with this issue I would be very
> >> appreciative.  I have tried to be detailed but if there is more info
> >> needed please let me know.
> >>
> >> Thanks heaps for your time, you guys do a great job! I am loving wicket.
> >> Regards,
> >> Dean
> >>
> >>
> >> Matej Knopp-2 wrote:
> >>>
> >>> Hi,
> >>>
> >>> This was recently fixed. Can you please try getting wicket from svn to
> >>> see if it help your problem?
> >>>
> >>> -Matej
> >>>
> >>> On 5/1/07, RedFury <[EMAIL PROTECTED]> wrote:
> >>>>  Hi fellow wicket-ers. I am attempting to write a small wicket app
> >>>> which can
> >>>> use multiple windows. The app updates a simple component using an ajax
> >>>> timer. I am doing a simple pagemap mapping in my code so I am certain
> >>>> that
> >>>> each window is using a different pagemap. With just one page it is
> >>>> fine,
> >>>> however as soon as I open up a second tab, I get a "session expired"
> >>>> message
> >>>> in the first tab when it attempts its next ajax reques.t When I follow
> >>>> the
> >>>> "return to home page" link the page refreshes and all is fine again. I
> >>>> compared the two .html pages (the one which failed and the refreshed
> >>>> one
> >>>> which works) and it seems the only difference is the value of the
> >>>> wicket:interface value in the ajax calls (0 in the old version, 3 in
> >>>> the
> >>>> new.) Now, I know that with multiple window support in wicket, it
> >>>> clones the
> >>>> original page (or something similar) whenever you open a new tab, is it
> >>>> possible that this process is somehow incrementing the page version
> >>>> number,
> >>>> then the ajax request fails because its using the wrong
> >>>> wicket:interface? I
> >>>> have tried all sorts of stuff like turning versioning and not just
> >>>> targetting the 'active' page, but to no avail. I did a lot of searches
> >>>> and
> >>>> have read other similar reports from other users but the problem never
> >>>> semed
> >>>> to get resolved? Any help on this matter would be greatly aprpeciated,
> >>>> I can
> >>>> supply some code if needed. However even with an almost-blank app
> >>>> (simple
> >>>> label component and an AjaxSelfUpdating behavior which does nothing)
> >>>> the
> >>>> "session expired" message still appears in the original tab after
> >>>> opening a
> >>>> second tab. Thanks Dean
> >>>> ________________________________
> >>>>  View this message in context: Ajax Request problem with new window
> >>>> tabs
> >>>> (Wicket 1.3 snapshot)
> >>>>  Sent from the Wicket - User mailing list archive at Nabble.com.
> >>>>
> >>>> -------------------------------------------------------------------------
> >>>> This SF.net email is sponsored by DB2 Express
> >>>> Download DB2 Express C - the FREE version of DB2 express and take
> >>>> control of your XML. No limits. Just data. Click to get it now.
> >>>> http://sourceforge.net/powerbar/db2/
> >>>> _______________________________________________
> >>>> Wicket-user mailing list
> >>>> Wicket-user@lists.sourceforge.net
> >>>> https://lists.sourceforge.net/lists/listinfo/wicket-user
> >>>>
> >>>>
> >>>
> >>> -------------------------------------------------------------------------
> >>> This SF.net email is sponsored by DB2 Express
> >>> Download DB2 Express C - the FREE version of DB2 express and take
> >>> control of your XML. No limits. Just data. Click to get it now.
> >>> http://sourceforge.net/powerbar/db2/
> >>> _______________________________________________
> >>> Wicket-user mailing list
> >>> Wicket-user@lists.sourceforge.net
> >>> https://lists.sourceforge.net/lists/listinfo/wicket-user
> >>>
> >>>
> >>
> >>
> >
> >
> http://www.nabble.com/file/8194/WicketTabExample.7z WicketTabExample.7z
> --
> View this message in context: 
> http://www.nabble.com/Ajax-Request-problem-with-new-window-tabs-%28Wicket-1.3-snapshot%29-tf3673608.html#a10300091
> Sent from the Wicket - User mailing list archive at Nabble.com.
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> Wicket-user mailing list
> Wicket-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wicket-user
>

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

Reply via email to