I committed some changes so that in the JSP case a screen is expected to be
found as <screen>.jsp.
Only for a few exceptions (Home, Admin, Info,...) respective screen classes
are searched and executed in the old Ecs style.
This works the same with all templates of course, not only with JSPs.
The new processing has mainly advantages:
* The markup is much easier to edit as its in a template and not generated
by java code. This allows non-programmers to edit the screens and use
standard tools for this task.
* The screens can much easier localized, as (ideally) all written language
can be found in the templates.
I would picture the default processing flow as the following:
1. Request come into turbine servlet which handles security stuff etc.
2. As the controller part of the program an action is caled that does some
processing on the model and places the results in the request (e.g. as a
JavaBean)
3. The Layout template is executed which includes navigations and screen.
The screen uses the data that is provided in the request for the rendering.
In my opinion, a screen shouldn't execute "real" code, i.e. no processing
on the model, no calculating of results. They should be pure views. (That
rather a description of what I'd like to have that how it's done at the
moment :-( )
However, Login.java, ConfirmRegistration.java, NewAccount.java are already
not used any more.
ingo.
BTW, does anybody know how I can add a "Error.jsp" to the directory where I
deleted a "error.jsp". CVS won't let me do that...
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/[email protected]/>
List Help?: [EMAIL PROTECTED]
