> Gary VanMatre wrote:
> 
> >>Another question about html views (since they are more interesting in 
> >>practical use). For example I have main.html component and profile.html 
> >>component. The both have submit buttons - but I want distinguish that 
> >>one button is for main.html and another one - for profile.html. In 
> >>rolodex example all components are specified in one config file without 
> >>any hierarchy - so I should invent some naming convention (e.g 
> >>mainPageSubmitButton,profilePageSubmitButton, 
> >>addressBookPanelNotesTabSubmitButton etc) to be sure that component ids 
> >>will not fail to conflict. It's not convenient - because if I'll change 
> >>name for mainPage I should change names for all component. Is it 
> >>possible to do by other way?
> >>
> >>    
> >>
> >
> >
> >The clay component itself is a naming container.  This is the same as the 
> subview.  This means that components under it have unique clientId's.  
> Another 
> consideration is a faces form will uniquely identify anything under it.  
> Using 
> these two containers, you can reuse a single commandButton definition in a 
> clay 
> XML config, nested under two different forms.
> >
> >  
> >
> 
> sory for typo - I mean jsfid ;(
> so I need the same hierarchy as id
> 


The jsfid is a Clay manufactured attribute that represents a top-level 
component.  What I mean by top-level is that it can be a root or aggregated 
under another component.  The jsfid must be unique. 

The id attribute corresponds to the faces components id attribute.  The id 
attribute is used when rendering the html and will be used to create target 
html element’s id.  In JSF the renders use the clientId of each component as 
the html identity (the hierarchy or xpath).  The client id represents the 
containment within the component tree that defines the page (viewId).  This 
allows you to reuse visual fragments.  The standard approach is to use the 
subview naming container.

Clay is a standard faces component that just taps into the functionality that 
already exists in the JSF API.  It expands the JSP tag piece of vanilla JSF.

Gary




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

Reply via email to