You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by "Aaron J. Garcia" <ag...@rentec.com> on 2014/03/11 19:27:17 UTC
More Wicket JSESSION_ID Issues
I finally got around to upgrading to Wicket 6.14.0 yesterday. With the new
changes in Wicket, I no longer get the exception spit out to the log when I
change the JSESSION_ID to JSESSION_ID_MYAPP. Thanks for that!
I have another issue now:
When I run my app in my IDE (I use Intellij 13.0.2 and Tomcat 7.0.39), it
usually opens up a browser window for me pointing to the sign in page of my
app. If JSESSION_ID is left alone, this behavior continues to work fine.
Once I change my JSESSION_ID to something else, I get a message from
Intellij that says "Cannot open URL. Please check this URL is correct:". It
then shows the URL of my sign in page.
Of course, if I navigate there directly, it comes up fine. This is
perplexing to me. Perhaps something in Wicket isn't playing nice with this
functionality? This was all working fine with Wicket 6.13.0, so I don't
know what changed.
Would someone mind trying to reproduce?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: More Wicket JSESSION_ID Issues
Posted by Martin Grigorov <mg...@apache.org>.
Hi,
On Wed, Mar 12, 2014 at 9:52 PM, Aaron J. Garcia <ag...@rentec.com> wrote:
>
>
> Martin Grigorov <mgrigorov <at> apache.org> writes:
>
> >
> > Hi,
> >
> > It sounds like an issue with the IDE.
> > What is the produced url with the custom jsession id ? Does it work if
> you
> > paste this url directly in the browser address bar without involving the
> > IDE ?
> >
> > And what is "the sign of my page" ?
> >
> > Martin Grigorov
> > Wicket Training and Consulting
> >
>
> Hi Martin,
>
> Sorry for the delayed response.
>
> The URLs are identical in both cases: http://machine:8085/appName/
>
> Wicket turns this into: http://machine:8085/appName/app/SignInPage
>
> Intellij tries to open the first URL (http://machine:8085/appName/), but
> it
> fails with this error message "Cannot open URL. Please check this URL is
> correct:". When I copy and paste that same URL
> (http://machine:8085/appName/) and paste it into my browser, it works
> fine,
> and directs me to sign in page.
>
> (That's what I meant by sign of my page... sorry for not catching that
> sooner).
>
> What is interesting is that if I remove any of the JSESSIONID changes I
> made
> (or downgrade to Wicket 6.13.0), everything works fine, and Intellij opens
> up http://machine:8085/appName/ like I would expect.
>
There must be something that IDEA hides from you.
http://machine:8085/appName/ is a valid url. But I guess it is actually
something like http://machine:8085/appName/;myjsessionid=123456 and IDEA
thinks that ;myjsessionid=123456 is the invalid part.
Since the url loads the page in the browser then the IDE is the problem.
>
> -- Aaron
>
> P.S. I don't need an immediate solution to this, because I figured out a
> workaround yesterday. I would like to get to the bottom of the issue
> though, as the change in behavior is surprising.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
Re: More Wicket JSESSION_ID Issues
Posted by "Aaron J. Garcia" <ag...@rentec.com>.
Martin Grigorov <mgrigorov <at> apache.org> writes:
>
> Hi,
>
> It sounds like an issue with the IDE.
> What is the produced url with the custom jsession id ? Does it work if you
> paste this url directly in the browser address bar without involving the
> IDE ?
>
> And what is "the sign of my page" ?
>
> Martin Grigorov
> Wicket Training and Consulting
>
Hi Martin,
Sorry for the delayed response.
The URLs are identical in both cases: http://machine:8085/appName/
Wicket turns this into: http://machine:8085/appName/app/SignInPage
Intellij tries to open the first URL (http://machine:8085/appName/), but it
fails with this error message "Cannot open URL. Please check this URL is
correct:". When I copy and paste that same URL
(http://machine:8085/appName/) and paste it into my browser, it works fine,
and directs me to sign in page.
(That's what I meant by sign of my page... sorry for not catching that sooner).
What is interesting is that if I remove any of the JSESSIONID changes I made
(or downgrade to Wicket 6.13.0), everything works fine, and Intellij opens
up http://machine:8085/appName/ like I would expect.
-- Aaron
P.S. I don't need an immediate solution to this, because I figured out a
workaround yesterday. I would like to get to the bottom of the issue
though, as the change in behavior is surprising.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: More Wicket JSESSION_ID Issues
Posted by Martin Grigorov <mg...@apache.org>.
Hi,
It sounds like an issue with the IDE.
What is the produced url with the custom jsession id ? Does it work if you
paste this url directly in the browser address bar without involving the
IDE ?
And what is "the sign of my page" ?
Martin Grigorov
Wicket Training and Consulting
On Tue, Mar 11, 2014 at 8:27 PM, Aaron J. Garcia <ag...@rentec.com> wrote:
> I finally got around to upgrading to Wicket 6.14.0 yesterday. With the new
> changes in Wicket, I no longer get the exception spit out to the log when I
> change the JSESSION_ID to JSESSION_ID_MYAPP. Thanks for that!
>
> I have another issue now:
>
> When I run my app in my IDE (I use Intellij 13.0.2 and Tomcat 7.0.39), it
> usually opens up a browser window for me pointing to the sign in page of my
> app. If JSESSION_ID is left alone, this behavior continues to work fine.
> Once I change my JSESSION_ID to something else, I get a message from
> Intellij that says "Cannot open URL. Please check this URL is correct:".
> It
> then shows the URL of my sign in page.
>
> Of course, if I navigate there directly, it comes up fine. This is
> perplexing to me. Perhaps something in Wicket isn't playing nice with this
> functionality? This was all working fine with Wicket 6.13.0, so I don't
> know what changed.
>
> Would someone mind trying to reproduce?
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>