> Volker Schmitt wrote: > > In our eCommerce Portal we have something like a > PartnerSelection which is needed by different modules > OrderCreate/OrderStatus/Prices. So the idea was to use one > pipeline for this PartnerSelection screen. If the selection > is finished the flow will continue with the next application > screen. We are not using flow in the moment. What we have > done is a forward to the PartnerSelection and then dep. on > the "requestURI" a redirect back to the application screen. > > So the use case is, using the same page from different > locations in the application without using the same URL. We > also need the diffent URL's for the same page to manage the > menu correctly (highlight the current location). > Hmm, ok, so you could for example use flow or you could use a workaround like storing the original request uri in an request attribute before the redirect and refer to that value (or something similar).
Now, I don't say, that a forward doesn't make sense at all, so it would be interesting to see what others think about it. Carsten
