[EMAIL PROTECTED] wrote:
I see. So you might have a template that looks like this?
Enter your Name: #set( $component = $JSFHelper.createComponent("input") #set(
$component.action = "#{managedBean.name}")
I'm not sure how you would merge the output in the template with the rendering of the component tree without dual processing? The inline text "Enter your Name: " should also be a jsf component.
No not even that complicated... I do not talk about altering the
component tree, I just talk about pure rendering....
more someting along the line of replacing java as the language for the
renderer with velocity...
example:
#########
## mycontrol example
#########
<div>
whatever
$linkTool.renderLink("outcomedefinedin faces-config","value which has to
be displayed")
$linkTool.renderLink("#{somebean.someAction}","value of display")
<p> additional html code in here.... $component.value is the value of
$component.id ....
##############
## end of control rendering code
##############
---
I think this give a clearer picture, this is sort of the way how turbine
does the rendering, but on a page scope, while I talk about using single
velocity templates per control rendering.
Sort of a simplified rendering write process for the control developers.
