The anti-Struts/MVC argument, and it isn't mine, is that whereas
Tapestry and JSF will generate the HTML/JSP, with Struts it has to be
written and maintained. Now I haven't spent that much time with
either Tapestry or JSF, but from what little I have read; it would
appear that they can generate the HTML/JSP it without the need for it
to be directly written (in HTML etc). That seems to be the gist of it.
Cheers
Christopher Marsh-Bourdon
www.marsh-bourdon.com
AIM: marshbourdon
On 8 Aug 2005, at 21:58, Leon Rosenberg wrote:
"JSP/HTML/XHTML is a messy mark-up. It is cumbersome to
refactor and a bugger to work out. We could use Tapestry or
JSF and forget about HTML."
That's right, but as long as you deliver html to the customer, you
have to
deal with it, regardless of your technology.
At the end of the day, someone has to produce the html. It can be a
view
component as in JSF, a tile as in Struts, or whatever, but it has
to be
done, and the HTML code is ABSOLUTELY IDENTICAL in all cases :-)
So sorry, but this is no argument pro or contra struts.
So, I've gone back and revisited our JSPs to see if this
criticism is correct; and to be honest it is. I am a fairly
careful coder and I adhere to the XHTML standards as
diligently as possible, but it still looks pretty confusing.
Now the main issue is that we really (a team of three) never
had the time to get the basics right prior to launching into
the migration from .net to Struts. By the basics, I mean
working out an encompassing* CSS.
Good decision :-)
So, I've gone back and re-
factored the JSP to use an encompassing* CSS document, and lo
and behold the code (JSP) is cleaner and so much better to work with.
Now maybe everyone but me and my team uses an encompassing*
CSS throughout their JSP as standard and never deviates from
that path, but if you don't; take a little while to research
what it can do for your development. I have still to
convince this new manager that Struts is the way, but I've
removed one of the major arguments to going down the
Tapestry/JSF route for now (not that they don't use CSSes)!
* By "encompassing', I mean no formatting is used directly in
the JSP where it can be deferred to a style.
Again, what exactly is the difference in framework you use, as long
as the
resulting HTML page looks the same?
Don't misunderstand me, I congratulate you to better code and
encourage you
to use css, but I don't see how the usage of css can influence a
pro- or
contra-struts solution?
Regards
Leon
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
