I found the problem, but I do not know what the solution would be.
In my web.xml if I put in a specific url-pattern like
<filter-mapping>
<filter-name>myapp</filter-name>
<url-pattern>/myapp/*</url-pattern>
</filter-mapping>
it then works. If I use plain <url-pattern>/*</url-pattern>, then it drops
the context.
So with the new url-pattern in the filter mapping, I have to use the
address:
http://localhost:8080/MyApp/myapp/
and everything works OK.
Should this be submitted as a bug or am I missing something in the big
picture?
--Tim
trames wrote:
>
> Additionally, if I then type the address
>
> http://localhost:8080/MyApp/ the home page shows like it should
>
>
>
> -----Original Message-----
> From: Ames, Tim [mailto:[EMAIL PROTECTED]
> Sent: Monday, July 28, 2008 11:24 AM
> To: [email protected]
> Subject: AuthenticatedWebApplication Problem
>
> Using wicket 1.3.4 - production/stable version
>
>
>
> I am testing AuthenticatedWebApplication and AuthenticatedWebSession set
> up similar to the wicket-examples.
>
>
>
> I have the @AuthorizationInstantiation annotation set up on the home
> page.
>
>
>
> I start up a session using the address: http://localhost:8080/MyApp/
>
>
>
> As expected, the Sign In page shows with an address of:
> http://localhost:8080/MyApp/?wicket:bookmarkablePage=:org.apache.wicket.
> authentication.pages.SignInPage
>
> I log in, the user and password are valid, and I click Sign In.
>
>
>
> At this point is where the problem occurs. I loose the context "MyApp"
> in the address. The address now shows: http://localhost:8080/index.jsp
>
>
>
>
>
> Thanks for any insight.
>
> --Tim
>
>
>
>
>
--
View this message in context:
http://www.nabble.com/AuthenticatedWebApplication-Problem-tp18692918p18696591.html
Sent from the Wicket - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
