>From: Richard Wallace <[EMAIL PROTECTED]> 
>
> Gary VanMatre wrote: 

> Interesting options. I decided that for this case it's not incredibly 
> important to have the html mockup so went and created my first ever 
> component in the clay-config.xml. 

Cool.  You should check out the shale tiger extention.  You can register
a component like this:

@FacesComponent ("org.apache.shale.SomeComponent")
class public SomeComponent ....

No, XML config.

The whole JSF component is much cleaner that JSP tags.  I think
all of the pieces/layers are good but it's nice to be able to create
a component without a JSP tag and Renderer.

>Came out perfect the first time. I'm 
> amazed at how easy it was to do. Still, it would be nice to have a good 
> way to do this from the pure html file. I'm not sure exactly what that 
> should look like tho. All the spans just look messy and would is quite 
> a bit harder to understand. Why not add an attribute to the 

I was only thinking in terms of *no extra* XML config but the best way would be 
to handle the radio something like this:


HTML:
<input type=radio jsfid="businessState">

XML Config:
<component jsfid="businessState" extends="selectOneRadio" id="businessState" 
allowBody="false"> 
  <attributes>
     <set name="value" value="[EMAIL PROTECTED]" />
     <set name="required" value="true" />       
  </attributes>
 
  <element renderId="0" jsfid="selectItems"> 
     <attributes>
        <set name="value" value="#{rolodexDao.states}" />
     </attributes>
  </element>
</component>



> like "group"? Then, in my example, rather than name="response" on all 
> the related radio buttons you have group="response". The biggest 
> problem that I can see with that is that it would be impossible to do a 
> single pass through the document to determine what radio buttons make up 
> the same selectOneRadio component. Maybe this would call for a new JSF 
> component or something. I don't know, just throwing some ideas out there. 
> 
I'll try a couple more options but the XML backing is the best here since there 
is not a good HTML to XML mapping.

> As long as we're on the subject,one thing that I really don't like about 
> the SelectOneRadio component in JSF is that the radio buttons need to be 
> right next to each other. So, there's no easy way, for instance, to 
> have a radio button in the far right of each row of a table to allow the 
> user to select the row they want to perform some action on. 

I'm not sure about this one. Maybe thru CSS?

> > 
> >> Thanks, 
> >> Rich 
> >> 

Gary
> >> --------------------------------------------------------------------- 
> >> To unsubscribe, e-mail: [EMAIL PROTECTED] 
> >> For additional commands, e-mail: [EMAIL PROTECTED] 
> >> 
> >> 
> 
> 
> --------------------------------------------------------------------- 
> To unsubscribe, e-mail: [EMAIL PROTECTED] 
> For additional commands, e-mail: [EMAIL PROTECTED] 
> 

Reply via email to