But this won't work when you have multiple components of the same type (let's say 3 inputText's), that all need a default styleClass. You can't have all 3 inputText tags bind to the same component, right?
On Tue, 7 Dec 2004 21:06:37 +0100, Martin Marinschek <[EMAIL PROTECTED]> wrote: > Hmmm... What I know that Manfred is doing in such a case (especially > if there are many such parameters), is using a component binding - > then he initializes the component in source-code, and only has to do > that once. He widely uses this approach with data-tables, there is a > lot to initialize there. > > regards, > > Martin > > On Mon, 6 Dec 2004 18:15:17 -0600, Heath Borders > > > <[EMAIL PROTECTED]> wrote: > > Unfortunately, no there is not. We were hoping we could just override > > the TLD definitions to provide defaults, but that doesn't end up > > working. > > > > The next best solution might be to override the createComponent() > > method of Application to do your defaulting (and back it with an xml > > file). > > > > > > > > > > On Fri, 03 Dec 2004 12:00:35 -0700, Matt Raible <[EMAIL PROTECTED]> wrote: > > > Is it possible to set a default styleClass for a component? All my > > > <h:message> tags are going to use the "fieldError" styleClass. Is there > > > a way to specify this in faces-config.xml, so I don't have to type it > > > every time? > > > > > > <h:message for="confirmPassword" styleClass="fieldError"/> > > > > > > Thanks, > > > > > > Matt > > > > > > > > > > > > -- > > If you don't have a GMail account, I probably have 5 invites. Just ask! > > -Heath Borders-Wing > > [EMAIL PROTECTED] > > > -- If you don't have a GMail account, I probably have 5 invites. Just ask! -Heath Borders-Wing [EMAIL PROTECTED]
