|
Thanks for your help.. My problem was that I wanted to store the
page history data in the component that displays it… not the visit. I was
hoping to be able to have persistent properties to store it..
I took Howard Ship’s advice
and decided to just go old skool and throw it into
the HttpSession.. This way I have managed to make it
transparent to the rest of the application. -----Original Message----- I've got an implementation of this. I store the
current location in the Visit. In each of my listener methods that move you to
a different page, I add the current page to the stack (the home page clears the
stack). Actually I think I use an ArrayList since I need to be able to walk the
stack both ways... Then I've got a location component that displays the
stack at the top of every page. When you click on a link it pops the right
number of things off the top of the stack. This system works fine as long as no-one hits a back
button! Unfortunately it crosscuts the whole application. I would have liked to
have come up with a more aspect-oriented solution. I'm not sure why you're talking about persistent page
properties, so maybe I'm missing your point completely ;) -----Original Message----- I am trying to implement a simple page history
component (ie. Shows Main Page > Options > etc.. each as a link ).
|
Title: RE: [Tapestry-developer] Persistant properties for components
- [Tapestry-developer] Persistant properties for components Luke Galea
- RE: [Tapestry-developer] Persistant properties for compo... Phil Surette
- Luke Galea
