Personally I would say it is just the opposite. There is more code
writing in struts than in Tags, which are totally optional. The coding
comes from the Actions (controller logic). As for the views, many have
pointed out, and used, XML output instead of JSP output for their views.
In some cases this may be transformed into HTML or perhaps WML, etc.
There is even a project started on sourceforge for accessing struts via
web services (Axis4Struts is the project name I believe).
- Robert
Guido wrote:
What do you think about this (from
http://barracuda.enhydra.org/cvs_source/Barracuda/docs/barracuda_vs_struts.html)
?
Unlike Barracuda, Struts is aimed primarily at the Page Author types.
This is not to say that Struts does not require Java coding--after all,
you still need developer types to implement Tag libraries and write
Controller code. Rather, it aims to suggest that it is Page Authors who
will get the most mileage from the framework; if you do not adopt a JSP
strategy for rendering views, the value of Struts is greatly diminished.
Guido Garcia Bernardo
[EMAIL PROTECTED]
[EMAIL PROTECTED]
stat rosa pristina
nomine, nomina nuda tenemus.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
