Don't know if I am making a fool of myself here but isn't the first "?wicket" part of the jessionid?
The jsessionid is generated by the container, right? Try changing the settings for that and see if something becomes different. /Per On Tue, Aug 11, 2009 at 3:28 AM, Jeff Longland <[email protected]>wrote: > That's the thing that I can't seem to figure out. The app works on > GlassFish v2 and Tomcat, but I'm having this problem on Sun Java App > Server 7. > > As suggested in ##wicket, I switched from the wicket filter to the > wicket servlet - but I'm still having the problem where there are two > "?wicket" in the URL after onSubmit. ex. > > https://host/app/;jsessionid=24DE33C36DE4E699D304CD19573DDB31?wicket:?wicket:interface=:1:: > :: > I'm assuming this is what's causing the HomePage to be rendered even > though the ResultPage is being requested? > > Anyone have any thoughts on why I'm getting two ?wicket params in the > URL? This doesn't happen on either GlassFish or Tomcat. > > Jeff > > On Mon, Aug 10, 2009 at 4:22 PM, Igor Vaynberg<[email protected]> > wrote: > > no clue either. wicket is just a filter, if it works in one container > > it should work in them all. try a couple of other containers, maybe it > > will help you to narrow the problem. > > > > -igor > > > > On Mon, Aug 10, 2009 at 12:31 PM, Jeff Longland<[email protected]> > wrote: > >> Not much in the way of clues... The ResultPage is being instantiated, > >> but instead of being rendered the HomePage is reloaded. Everything is > >> fine on GlassFish v2.. but Sun Java App Server 7 = no dice. I'm at a > >> loss for what to do next. > >> > >> On Mon, Aug 10, 2009 at 10:29 AM, Igor Vaynberg<[email protected]> > wrote: > >>> turn the logging to debug level and look at the logs for any clues. > >>> > >>> -igor > >>> > >>> On Mon, Aug 10, 2009 at 7:22 AM, Jeff Longland<[email protected]> > wrote: > >>>> I've been developing a Wicket app on GlassFish v2 and everything works > >>>> fine. But when I deploy the application to our production server > >>>> which runs Sun Java App Server 7, setResponsePage() isn't working > >>>> properly. What's particularly infuriating is that I can see in the > >>>> database that the request is being processed (new rows) but in the > >>>> browser the page isn't being redirected. Does anyone have any > >>>> suggestions for troubleshooting this problem? And no, I can't upgrade > >>>> the production server to a newer version or Jetty for that matter :( > >>>> Any help would be greatly appreciated as I need to get this app > >>>> running. > >>>> > >>>> Thanks again, > >>>> Jeff > >>>> > >>>> --------------------------------------------------------------------- > >>>> To unsubscribe, e-mail: [email protected] > >>>> For additional commands, e-mail: [email protected] > >>>> > >>>> > >>> > >>> --------------------------------------------------------------------- > >>> To unsubscribe, e-mail: [email protected] > >>> For additional commands, e-mail: [email protected] > >>> > >>> > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: [email protected] > >> For additional commands, e-mail: [email protected] > >> > >> > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
