<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
On 12/15/09 9:18 AM, Ed Burns wrote:<br>
<blockquote cite="mid:19239.43222.362699.138785@sun.com" type="cite">
<pre wrap="">Though I'm delighted to see all the traffic on this topic, I have to
weigh in and oppose adding many more tags. The design focus of JSF
views has always been to mix template text and components. In my
opinion, this is widely seen as a strength for server-side UI
technologies such as JSF.
</pre>
</blockquote>
I think I agree with Ed here. At first, I thought adding a plethora of
new tags might be a good idea for those case where you might want to
interact with that particular DOM element on the client using various
JSF facilities. I think, though, the concern of an avalanche of tags
might be off-putting, actually feeding into the complaints from some
camps (I'm looking at you, Wicket people :) of tag soup. For those
cases where you do need access to a DOM element, "wrapper" components
(such as the now-and-sadly-defunct Woodstock's webuijsf:markup:
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
<code style="color: rgb(0, 0, 0);"><webuijsf:markup tag="div"
style="color:blue" /)</code> would probably suffice. Granted, it
doesn't look as intuitive on the page, but in... I forget how many
years of doing JSF, I've rarely needed such a component.<br>
<pre class="moz-signature" cols="72">--
Jason Lee, SCJP
President, Oklahoma City Java Users Group
Senior Java Developer, Sun Microsystems
<a class="moz-txt-link-freetext" href="http://blogs.steeplesoft.com">http://blogs.steeplesoft.com</a></pre>
</body>
</html>