Re: AuthenticatedWebApplication Problem
Yes, there was an index.jsp in the root context. I removed this, and it will now work with filter-mapping filter-namemyapp/filter-name url-pattern/*/url-pattern /filter-mapping This seems like a rather obscure problem. Is this documented somewhere or can it be fixed so others won't have to spend time on it. I spend two days trying to figure out what was wrong. As far as Maurice's question, I saw the continueToOriginalDestination() method buried in the SignInPanel.java source. So yes it is being used. I am using the stock code for this panel, and am not sure how to get the url at that point in the stack. Thanks to all for helping with this problem --Tim Martijn Dashorst wrote: do you have an index.jsp in your root context? If so, remove that and try again. Martijn On Mon, Jul 28, 2008 at 5:24 PM, Ames, Tim [EMAIL PROTECTED] wrote: 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 -- Become a Wicket expert, learn from the best: http://wicketinaction.com Apache Wicket 1.3.4 is released Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/AuthenticatedWebApplication-Problem-tp18692918p18717912.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]
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 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ EMAIL CONFIDENTIALITY NOTICE This Email message, and any attachments, may contain confidential patient health information that is legally protected. This information is intended only for the use of the individual or entity named above. The authorized recipient of this information is prohibited from disclosing this information to any other party unless required to do so by law or regulation and is required to destroy the information after its stated need has been fulfilled. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or action taken in reliance on the contents of this message is strictly prohibited. If you have received this information in error, please notify the sender immediately by replying to this message and delete the message from your system.
RE: AuthenticatedWebApplication Problem
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: users@wicket.apache.org 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 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ EMAIL CONFIDENTIALITY NOTICE This Email message, and any attachments, may contain confidential patient health information that is legally protected. This information is intended only for the use of the individual or entity named above. The authorized recipient of this information is prohibited from disclosing this information to any other party unless required to do so by law or regulation and is required to destroy the information after its stated need has been fulfilled. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or action taken in reliance on the contents of this message is strictly prohibited. If you have received this information in error, please notify the sender immediately by replying to this message and delete the message from your system. _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ EMAIL CONFIDENTIALITY NOTICE This Email message, and any attachments, may contain confidential patient health information that is legally protected. This information is intended only for the use of the individual or entity named above. The authorized recipient of this information is prohibited from disclosing this information to any other party unless required to do so by law or regulation and is required to destroy the information after its stated need has been fulfilled. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or action taken in reliance on the contents of this message is strictly prohibited. If you have received this information in error, please notify the sender immediately by replying to this message and delete the message from your system. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: AuthenticatedWebApplication Problem
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-namemyapp/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: users@wicket.apache.org 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]
Re: AuthenticatedWebApplication Problem
do you have an index.jsp in your root context? If so, remove that and try again. Martijn On Mon, Jul 28, 2008 at 5:24 PM, Ames, Tim [EMAIL PROTECTED] wrote: 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 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ EMAIL CONFIDENTIALITY NOTICE This Email message, and any attachments, may contain confidential patient health information that is legally protected. This information is intended only for the use of the individual or entity named above. The authorized recipient of this information is prohibited from disclosing this information to any other party unless required to do so by law or regulation and is required to destroy the information after its stated need has been fulfilled. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or action taken in reliance on the contents of this message is strictly prohibited. If you have received this information in error, please notify the sender immediately by replying to this message and delete the message from your system. -- Become a Wicket expert, learn from the best: http://wicketinaction.com Apache Wicket 1.3.4 is released Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
