Presumably you would want such a construct to work regardless of what path a 
user took to get to a specific page (assuming there ARE multiple paths in your 
app, maybe there aren't).  So, if it was me, I'd be thinking a linked list 
stored in session.  Each page that is presented would append itself to the 
list.  Clicking a link would have to break the list at the point of the page 
that was clicked (i.e., if there are six pages in the nav trail and the user 
clicks the third, you basically want to discard the last three, which just 
means removing the link to the next element from the element of the page the 
user clicked).  You would of course have to add enough information to each 
element in the list as to allow your app to go to that page when clicked.  
Might just be storing the Action path, might mean each element is really a 
HashMap with a bunch of information, you would have to decide.

I'm not sure something like this exists yet, I'd certainly think it does 
though.  If you have to roll your own, I suspect it wouldn't be too difficult 
using this approach (assuming I haven't glossed over something that makes it 
impossible or overly difficult of course!)

-- 
Frank W. Zammetti
Founder and Chief Software Architect
Omnytex Technologies
http://www.omnytex.com

Donie Kelly wrote:

> Hi all
>
>  
>
> Anybody got an example of how to implement a page navigation link for the
> top of a page like so...
>
>  
>
> Home > MainFgorm > wizardpage1 > wizard page 2
>  
>
> The last entry would be the name of the current page and would not be a
> link. I'm thinking of a session object where the page inserts it's name
> somehow so that if the page is re-used in different areas it puts it's link
> in the correct place.
>
>  
>
> Just wondering how this can be achieved easily with struts and without
> hardcoding the paths on each page.
>  
>
> Thanks
>
> Donie
>
>  
>
>




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to