Re: Wicket 6.4.0 Session/URL bug?

2012-12-21 Thread Martijn Dashorst
On Fri, Dec 21, 2012 at 1:41 AM, Chris Colman wrote: > Oh, I didn't realize there was a separate ASF based repository. That is the canonical one. The github ones were just mirrors. "If it ain't at Apache it isn't Apacheā„¢" > It there a manual (human) based process for changes migrating from the >

RE: Wicket 6.4.0 Session/URL bug?

2012-12-20 Thread Chris Colman
.com] >Sent: Thursday, 20 December 2012 6:42 PM >To: users@wicket.apache.org >Subject: Re: Wicket 6.4.0 Session/URL bug? > >Don't use github if you want the changes right now, it is not the canonical >repository. Our ASF based one is. The github repo can be behind for days. > &

Re: Wicket 6.4.0 Session/URL bug?

2012-12-20 Thread Bertrand Guay-Paquet
ed on github master branch that have any core code changes that may have fixed this. Are the changes still in progress? Chris -Original Message- From: Jesus Mireles [mailto:toxi...@gmail.com] Sent: Thursday, 20 December 2012 3:20 AM To: users@wicket.apache.org Subject: Re: Wicket

Re: Wicket 6.4.0 Session/URL bug?

2012-12-19 Thread Martijn Dashorst
rsday, 20 December 2012 3:20 AM >> To: users@wicket.apache.org >> Subject: Re: Wicket 6.4.0 Session/URL bug? >> >> I have uploaded a quickstart and created a new issue: >> >> https://issues.apache.org/jira/browse/WICKET-4935 >> >> Something inter

Re: Wicket 6.4.0 Session/URL bug?

2012-12-19 Thread Sven Meier
e the changes still in progress? Chris -Original Message- From: Jesus Mireles [mailto:toxi...@gmail.com] Sent: Thursday, 20 December 2012 3:20 AM To: users@wicket.apache.org Subject: Re: Wicket 6.4.0 Session/URL bug? I have uploaded a quickstart and created a new issue: https://issues.apach

RE: Wicket 6.4.0 Session/URL bug?

2012-12-19 Thread Chris Colman
Got the changes now, thanks Sven! >-Original Message- >From: Chris Colman [mailto:chr...@stepaheadsoftware.com] >Sent: Thursday, 20 December 2012 6:32 AM >To: users@wicket.apache.org >Subject: RE: Wicket 6.4.0 Session/URL bug? > >Jira says this has been fixed but I c

RE: Wicket 6.4.0 Session/URL bug?

2012-12-19 Thread Chris Colman
y, 20 December 2012 3:20 AM >To: users@wicket.apache.org >Subject: Re: Wicket 6.4.0 Session/URL bug? > >I have uploaded a quickstart and created a new issue: > >https://issues.apache.org/jira/browse/WICKET-4935 > >Something interesting, if I dont mount any pages, it works as

Re: Wicket 6.4.0 Session/URL bug?

2012-12-19 Thread Bertrand Guay-Paquet
To be clear, I don't use wicket's auth module. I suspect that what was reported is caused by stateful/stateless pages. On 19/12/2012 12:51 PM, Bertrand Guay-Paquet wrote: Hi, I'm trying 6.4.0 now and seeing the same issue. My use-case is a little bit different though: 1) Without active sessio

Re: Wicket 6.4.0 Session/URL bug?

2012-12-19 Thread Bertrand Guay-Paquet
Hi, I'm trying 6.4.0 now and seeing the same issue. My use-case is a little bit different though: 1) Without active session, go to stateless page 2) Go to stateful page The first stateful page loaded is wrong like so: http://localhost:8080/SERVLET_CONTEXT/SERVLET_CONTEXT;jsessionid=7C9C4B53381D

Re: Wicket 6.4.0 Session/URL bug?

2012-12-19 Thread Jesus Mireles
I have uploaded a quickstart and created a new issue: https://issues.apache.org/jira/browse/WICKET-4935 Something interesting, if I dont mount any pages, it works as expected. I was only able to recreate when I actually used mountPackage to mount the private page. Thanks, Jesus M. On Wed, D

Re: Wicket 6.4.0 Session/URL bug?

2012-12-18 Thread Sven Meier
Hi Nick, WICKET-4920 might be related. Please create a quickstart showing the problem. Thanks Sven On 12/19/2012 06:39 AM, Chris Colman wrote: I have seen this exact same issue. I first saw it after I reported the, possibly related, bug: https://issues.apache.org/jira/browse/WICKET-4920 a

RE: Wicket 6.4.0 Session/URL bug?

2012-12-18 Thread Chris Colman
I have seen this exact same issue. I first saw it after I reported the, possibly related, bug: https://issues.apache.org/jira/browse/WICKET-4920 and then was verifying that it was fixed. I only noticed the bug you describe after I built with a version of Wicket that included the above fix. I'm