Hi.
I work for a software publisher making web applications and we currently
use Turbine.
We find that our applications are hard to maintain because of the way we
handle the navigation: currently, we just use the TemplateLink tool in
velocity templates and in Action classes, to build the URLs pointing to
the different parts of the application.
I've been assigned the task to see if there was a better way to handle
these aspects. I looked to other web frameworks and most of them have a
way to declare externaly the navigation rules (eg: struts-config.xml for
Struts, faces-config.xml for JSF, Spring Web Flow for Spring, xwork.xml
for Webwork). Basically, these files document the flow of navigation in
a single place, and that's what we'd like to have.
Now my questions are:
1/ did I miss something (is there anything similar that could be used in
Turbine)?
2/ if not, is there any development planned in that direction, for
future versions of Turbine?
And I guess a more general question is: how do you guys deal with these
problems? Do you just use the TemplateLink tool? And do you have the
same feeling that it's a problem to have the links at several parts of
the application?
Thank you very much for your help.
BoD
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
