>Oh that is great !!!
>I never knew we could do these things using Clay.
It's a new feature that Sergey Smirnov requested. It's good to hear
feedback:-)
>But I have some questions about ur example,
>1) <span jsfid="loadBundle" var="messages" >basename="com.acme.mywidgets" />
>I guess it is ur custom component.. What is baseName ? Could you explain
>this line for me.
Yep, The LoadBundle is one of Clay's. It was contributed by Manfred Klug. It
simulates the JSF loadBundle JSP tag. The basename is the path to a resource
bundle. The cool thing about JSF's approach to a resource bundle is wrappered
by a Map making it available to EL. This component will load the bundle into
request scope.
Craig commited a LoadBundle "bean" in the core Shale code base last weekend.
It's a managed bean verses a JSF component. The benefit is that you can
control the scope the bundle is loaded (request, session, application).
>2) <input id="city" type=text value="#{managed-bean-name.city}" size=25/>
>(assumed mapping to outputText)
>What you mean by "mapping to outputText" ?
There is a assumed mapping to some html elements to JSF components. These
include: a, form, input/text, input/checkbox, input/radio, input/submit,
label, option, select and textarea. You don't have to specify a jsfid binding
for these components (input/submit is currently broken).
Other html "begin" nodes that don't fall into the assumed mapping require a
jsfid. This was limited to just the span element but now applies to anything.
Maybe the the assumed mapping is just confusing now? At first I thought it was
important to protect/restrict the mapping but I'm not sure now.
>Gary please do create thrid rolodex example using this method.
I'll add that example.
Thanks for the feedback,
Gary
