From: "Michael Jouravlev" <[EMAIL PROTECTED]>
With Tapestry you create HTML template for each page, then stick data
into it, using jwcid attribute. Your webdesigner is happy.
With JSF you compose page using JSF tags either manually or using
visual IDE, and then JSP/JSF engine will generate HT
On 8/8/05, Michael Jouravlev <[EMAIL PROTECTED]> wrote:
> On 8/8/05, Christopher Marsh-Bourdon <[EMAIL PROTECTED]> wrote:
> > Over the past
> > six months we have been migrating our front-ends from .net to Java
> > based technologies, and Struts in the main. Now a new manager has
> > come on board
With Tapestry you create HTML template for each page, then stick data
into it, using jwcid attribute. Your webdesigner is happy.
With JSF you compose page using JSF tags either manually or using
visual IDE, and then JSP/JSF engine will generate HTML in the runtime
(I don't know how HTML is generat
www.csszengarden.com
www.alistapart.com
On 8/8/05, Johnson, Kaerstin <[EMAIL PROTECTED]> wrote:
>
> I am not understanding what you mean by this (encompassing* CSS), or
> perhaps I am not familiar with some technique, can you elaborate or
> provide an example? I am intrigued..
--
Sorry, the point was not to compare .net/JSF/Tapestry against Struts,
but to highlight that a bit fore thought into developing a good CSS
at the start of the project would have reduced the amount of markup
we have had to write in the last six months. It certainly makes our
life easier to m
On 8/8/05, Christopher Marsh-Bourdon <[EMAIL PROTECTED]> wrote:
> Over the past
> six months we have been migrating our front-ends from .net to Java
> based technologies, and Struts in the main. Now a new manager has
> come on board and he wishes us to revisit the reasons why we choose
> Struts.
8. August 2005 23:05
An: Struts Users Mailing List
Betreff: Re: [OT] JSP Clutter
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
Christopher Marsh-Bourdon wrote:
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;
> -Ursprüngliche Nachricht-
> Von: Christopher Marsh-Bourdon [mailto:[EMAIL PROTECTED]
> Gesendet: Montag, 8. August 2005 23:05
> An: Struts Users Mailing List
> Betreff: Re: [OT] JSP Clutter
>
> The anti-Struts/MVC argument, and it isn't mine, is that
>
I mean where you can specify how a tag is rendered (within your
browser) totally using CSS rules, rather than specifying messy and
deprecated tags such as .
I also exclude using inline CSS styles such as when it could declared as and
let a CSS define it's behavior. Inline CSS doesn't re
I am not understanding what you mean by this (encompassing* CSS), or
perhaps I am not familiar with some technique, can you elaborate or
provide an example? I am intrigued..
>* By "encompassing', I mean no formatting is used directly in the JSP
where >it can be deferred to a style.
-Ori
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 gen
>
> "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
13 matches
Mail list logo
