In JSF1.2, the tree is built before the rendering happens - so
everything that is plain HTML is converted into a part of the
component tree anyways. Maybe we should just wait for this to happen
;) ?
Facelets is another question. No clue.
regards,
Martin
On 9/22/06, Gerald Müllan [EMAIL
I think there may be a LiteralText or LiteralTextBlock element in
facelets. Whether it's internal only or available as a public
component, I don't know.
On 9/22/06, Thomas Spiegl [EMAIL PROTECTED] wrote:
Is there a new component in JSF 1.2 to store HTML output?
On 9/22/06, Mike Kienenberger
The goal with JSF 1.2's rendering is that the ViewHandler, while it
builds the view, shouldn't render anything at all. So using JSP as your
view or Facelets as your view, the act of evaluating those artifacts
shouldn't push anything to the response.
Once you have the full component tree from
From: "Mike Kienenberger" [EMAIL PROTECTED] Like JSP 1.2, Facelets builds the tree before rendering. Facelets might even have originated the idea :-)
Actually, Clay was sitting in a bugzilla ticket as a proposed enhancement to the shale subview component before Jacob started facelets
On 9/22/06, Gary VanMatre [EMAIL PROTECTED] wrote:
Actually, Clay was sitting in a bugzilla ticket as a proposed enhancement to
the shale subview component before Jacob started facelets
(http://weblogs.java.net/blog/edburns/archive/2005/04/javaserver_face_1.html).
Clay also builds the tree
Declaring subviews and ajax regions is only a partial solution-- when JSF in fact should be able to re-render any component without being explicitly declared as a refreshable region (that's what we were pushing out of Facelets and JSF 1.2). Ajax4Jsf does this by decoration of existing, non-ajax
From: [EMAIL PROTECTED]
Declaring subviews and ajax regions is only a partial solution-- when JSF in fact
should be able to re-render any component without being explicitly declared as a
refreshable region (that's what we were pushing out of Facelets and JSF 1.2).
Ajax4Jsf does this by
The UIViewRoot unique id must be persisted to guarantee that no matter the
state saving lifecycle of the component tree, that the UIViewRoot can always
produce a unique ID, despite changes to the structure of the view at 'build
time'.
I understand what you are going for with Verbatims and
Hi Gary,
yes, this is what we are doing, exactly. And for the same reasons. I
haven't found a better way - without JspIdConsumers around ;).
regards,
Martin
On 9/22/06, Gary VanMatre [EMAIL PROTECTED] wrote:
From: [EMAIL PROTECTED]
Declaring subviews and ajax regions is only a partial
From: [EMAIL PROTECTED] The UIViewRoot unique id must be persisted to guarantee that no matter the state saving lifecycle of the component tree, that the UIViewRoot can always produce a unique ID, despite changes to the structure of the view at 'build time'. I understand what you are going for
Martin and Jacob,
Thanks for the info. I'll take a better look at the new JspIdConsumer.
Gary
-- Original message -- From: "Martin Marinschek" [EMAIL PROTECTED] Hi Gary, yes, this is what we are doing, exactly. And for the same reasons. I haven't found a better way
11 matches
Mail list logo
