On 2/14/06, Rick Reumann <[EMAIL PROTECTED]> wrote: > Mark Lowe wrote the following on 2/14/2006 2:32 PM: > > > > The only other suggestion i would make if this were an issue is use > > separate action mappings for each point of entry.. > > Actually that seems pretty clean to me. Even if he has a lot of points > of entry it can't be "that" many.
One occasion when i use the forward to referer was when i had a basket/cart presented all over the place.. Rather than have a boring old, go to basket page do some basket stuff, i wanted the user to be able to maniuplate the cart with out going anywhere, on anypage.. I guess there could be other ways, but sometimes you do have N amount of entry points.. Or another option is to simply embed > some param that gets passed when the Action is called and you can call > different forwards based on that. Simply define several forwards in the > config... > > <action > path="/someAction" > name="someForm" > type="com.WhateverAction" > scope="request" > parameter="dispatch"> > <forward name="fromFooPage" path="/WEB-INF/jsp/someOtherPageA.jsp"/> > <forward name="fromBarPage" path="/WEB-INF/jsp/someOtherPageB.jsp"/> > > Or they may even be global forwards. > > In the action just look for some param like "fromPage" and key off of > that for your return. (Of course a drawback is you'll need to remember > to set this var on the pages that need it - of course there are ways you > could simplify that even, if really necessary). > > In the case of a few entry points I see how this could be okay.. But if you've something thats present through out a load of pages, I'd take my chances using the Referer header. Mark > > -- > Rick > > --------------------------------------------------------------------- > 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]
