On Dec 19, 2005, at 14:48, Mazhar, Osman (Home Office) wrote:
Is cycle.activate() the only way of going from one page to another
- or can
this be encapsulated in a config file - i.e. outside of the java code?
Tapestry has no built-in way to set up page flow via an external
file, though I could think of several ways to do it fairly easily.
If you wanted to code it yourself, you could do it by writing a bit
of code to read your table definition, then:
1) Creating a common subclass for all of your pages and include the
"go to next page" feature there, or
2) Put the "look up and go to next page" function in a utility class
and plug it into Hivemind (for Tapestry 4), then...
2a) inject this information into each page, or
2b) intercept (via Hivemind) whatever function you're calling from a
page's form and trigger the redirection to the next page.
There might even be a good place to just stick a class in the request
processing pipeline. Howard could likely tell you.
...Richard
P.S. Tapestry is rather different from Struts or JSF. I consider that
a feature (as surely many others here do.) You might spend some more
time prototyping with it and then see if you're still hungering for
an external page-flow configuration file.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
