> Would the fact that wicket now uses a filter instead of a servlet have > an effect on trying to forward a request. I'm trying to forward a > request from the jsp/servlet portion of our app to a bookmarkable wicket > page using RequestDispatcher.forward(), but no matter what sort of path > I send it, I get a null value when trying to create my RequestDispatcher > object. > > My wicket filter is mapped to /wicket/*, and as an experiment I tried > to forward to my app's home page. I tried passing "/wicket/", > "wicket/", and even "/wicket" (which shouldn't work), an neither case > allowed me to create a RequestDispatcher (using > request.getRequestDispatcher()). If I simply pass "/" id does forward > to my app's welcome page, and I think even passing a path for my servlet > (where the forward is occuring--or trying to at least) is recognized; > but I can't get it to recognize the wicket app. > > I tried including > > <dispatcher>REQUEST</dispatcher> > <dispatcher>FORWARD</dispatcher> > > in the filter-mapping of my web.xml, since it looked like that might > solve it, but no luck. It would be nice if I could find some way to > redirect from the old servlet back to wicket, but I haven't figured it > out yet. I've started experimenting with response.senRedirect(), but so > far that's not looking promising either. Why won't my app server > recognize my wicket path? Thanks. > > > Joel > > P.S. If someone tells me they think it's oc4j again (my app server) I > think I may cry. lol
No idea. You can still use a servlet with Wicket 1.3 if you want to test whether that makes the difference (sounds very unlikely to me, but if you test it you can make sure) and if you think it might be oc4j, you can simply test it with another servlet container and see whether the same problem exists. Eelco --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
