You are viewing a plain text version of this content. The canonical link for it is here.

Posted to users@myfaces.apache.org by Marcus Beyer <mb...@thomas-daily.de> on 2007/07/27 11:25:54 UTC

LoggingSettings

Greetings!

I got (and now solved) the problem stated here:

<http://wiki.apache.org/myfaces/Tomahawk_1%2e1%2e4_to_1%2e1%2e5>

However I did not get any "Invalid Option" error massages.

Do I have to change one of these settings to get them?

<http://wiki.apache.org/myfaces/LoggingSettings>

thanks!
Marcus

RE: Client validation configuration

Posted by Balaji Phani Krishna Annangi <ba...@Chordiant.com>.

Thanks Danny - I'm using old jar files. Working fine with 1.0.1 

Krishna Annangi
--------------------

________________________________________
From: Danny Robinson [mailto:dannyjrobinson@gmail.com] 
Sent: Friday, July 27, 2007 6:05 PM
To: MyFaces Discussion
Subject: Re: Client validation configuration

Which version of Trinidad are you using, as client-validation=INLINE was only available in 1.0.1 onwards.
On 7/27/07, Balaji Phani Krishna Annangi < balaji.annangi@chordiant.com> wrote:

Hi Everyone,

I am trying to configure the client side validation [inline/disabled/alert] of UI components. But no matter how I configured,
The client validations are always shown as alerts. I removed the configuration-still the validations are
Shown as alerts - I'm trying to validate <tr:inputText> component in Trinidad components demo using 
<tr:validateRegExp id="id" pattern="[0-9]*" messageDetailNoMatch="Error message" />

Also I am getting the following console warning when I use <client-validation>inline</client-validation>

WARNING: Element client-validation is not understood

Any help?

Thanks,
K.Annangi

-- 
Chordiant Software Inc.
www.chordiant.com

Re: Client validation configuration

Posted by Danny Robinson <da...@gmail.com>.

Which version of Trinidad are you using, as client-validation=INLINE was
only available in 1.0.1 onwards.

On 7/27/07, Balaji Phani Krishna Annangi <ba...@chordiant.com>
wrote:
>
>
>
> Hi Everyone,
>
>
>
> I am trying to configure the client side validation
> [inline/disabled/alert] of UI components. But no matter how I configured,
>
> The client validations are always shown as alerts. I removed the
> configuration-still the validations are
>
> Shown as alerts – I'm trying to validate <tr:inputText> component in
> Trinidad components demo using
>
> <tr:validateRegExp id="id" pattern="[0-9]*" messageDetailNoMatch="Error
> message" />
>
>
>
> Also I am getting the following console warning when I use
> <client-validation>inline</client-validation>
>
>
>
> WARNING: Element client-validation is not understood
>
>
>
> Any help?
>
>
>
> Thanks,
>
> K.Annangi
>



-- 
Chordiant Software Inc.
www.chordiant.com

Client validation configuration

Posted by Balaji Phani Krishna Annangi <ba...@Chordiant.com>.

 

Hi Everyone,

 

I am trying to configure the client side validation
[inline/disabled/alert] of UI components. But no matter how I
configured,

The client validations are always shown as alerts. I removed the
configuration-still the validations are

Shown as alerts - I'm trying to validate <tr:inputText> component in
Trinidad components demo using 

<tr:validateRegExp id="id" pattern="[0-9]*" messageDetailNoMatch="Error
message" />

 

Also I am getting the following console warning when I use
<client-validation>inline</client-validation>

 

WARNING: Element client-validation is not understood

 

Any help?

 

Thanks,

K.Annangi