I agree the validators should not have ids. Currently id is specified on the commons validator definition in the clay-config.xml packaged with clay. I think this probably should be removed, along with any ids in the definitions.
On 11/7/05, Gary VanMatre <[EMAIL PROTECTED]> wrote: > > >Gary, > > overriding the behavior of the getId and setId in the ValidatorBean, > >ValueChangeListenerBean and ConverterBean is not enough. > > Since these can potentially inherit from a plain ComponentBean, the will > >inherit the attributes of that ComponentBean. > > For example, commons validator is defined > > > ><component jsfid="commonsValidator" id="commonsValidator" componentType=" > >org.apache.shale.CommonsValidator" allowBody="false">.../<component> > >so when I say <validator jsfid="commonsValidator">...<validator> > > my validator is going to inherit the id from it's parent in > >ComponentConfigBean.realizingInheritance and later cause an exception > trying > >to set property id. > > To fix, we need to also in ValidatorBean, ValueChangeListenerBean and > >ConverterBean override addAttribute and setAttributes to not store the id > >attribute. > > Ah, That's a good point. I missed that one. Although, the id is not > required for a component node. I think we should fix this but why even > specify an "id" attribute for a validator?. > > Gary > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
