Date validation in a form

classic Classic list List threaded Threaded
20 messages Options
Reply | Threaded
Open this post in threaded view
|

Date validation in a form

Charles Moulliard
I would like to know How I can validate the string date inputted by a
user in a textfield of my form ?

e.g : The SimpleDateformat to be used to create a java Date is : dd/MM/yyyy
So I would like to check that the user has well introduced its date
using this format

Regards,

Charles Moulliard
Senior Enterprise Architect
Apache Camel Committer

*****************************
blog : http://cmoulliard.blogspot.com

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

FXValidationAjaxHandler - Javascript not added if component is set visible(false) in page constructor

christian.giambalvo
Hi all,

ich have a component (textfield) with an FXValidationAjaxHandler. If i
set this component in pageconstructor to visible(false) then the needed
javascript code for validation is not contributed to pageheader. if set
to visible(true) all is fine.
does anyone had the same problem and if so, is there a workaround
available?

greets chris

snippet:
...
pComponent.add(new FXValidationAjaxHandler(pFXJavascriptEvent));
this.pComponent.setOutputMarkupPlaceholderTag(true);
this.pComponent.setOutputMarkupId(true)
this.pComponent.setVisible(false); // no javascript is added
//this.pComponent.setVisible(true); // javascript is added
form.add(this.pComponent);
...

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: FXValidationAjaxHandler - Javascript not added if component is set visible(false) in page constructor

Igor Vaynberg-2
javascript contributions do not show up for components that are not
visible, add it to a visible component instead.

-igor

On Wed, Sep 23, 2009 at 7:15 AM, Giambalvo, Christian
<[hidden email]> wrote:

> Hi all,
>
> ich have a component (textfield) with an FXValidationAjaxHandler. If i
> set this component in pageconstructor to visible(false) then the needed
> javascript code for validation is not contributed to pageheader. if set
> to visible(true) all is fine.
> does anyone had the same problem and if so, is there a workaround
> available?
>
> greets chris
>
> snippet:
> ...
> pComponent.add(new FXValidationAjaxHandler(pFXJavascriptEvent));
> this.pComponent.setOutputMarkupPlaceholderTag(true);
> this.pComponent.setOutputMarkupId(true)
> this.pComponent.setVisible(false); // no javascript is added
> //this.pComponent.setVisible(true); // javascript is added
> form.add(this.pComponent);
> ...
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Date validation in a form

Igor Vaynberg-2
In reply to this post by Charles Moulliard
see DateTextField in extensions

-igor

On Wed, Sep 23, 2009 at 7:13 AM, Charles Moulliard <[hidden email]> wrote:

> I would like to know How I can validate the string date inputted by a
> user in a textfield of my form ?
>
> e.g : The SimpleDateformat to be used to create a java Date is : dd/MM/yyyy
> So I would like to check that the user has well introduced its date
> using this format
>
> Regards,
>
> Charles Moulliard
> Senior Enterprise Architect
> Apache Camel Committer
>
> *****************************
> blog : http://cmoulliard.blogspot.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

AW: FXValidationAjaxHandler - Javascript not added if component is set visible(false) in page constructor

christian.giambalvo
In reply to this post by Igor Vaynberg-2
Hi,

first thanks for reply.
Well, it's not possible to add it to a visible component.
Let me explain.
I have 2 custom panels and depending on the selection in a dropdownchoice the corresponding panel gets visible or hidden. Because one of these panels need to be invisible on page construction (so not both are showing up) i need to set it invisible. If i then select it in the dropdownchoice i gets visible.
And now the problem begins. Cause of the initial invisibility the needed javascript code for validation of the panel fields isn't injected. How can i workaround this?

Thanks in advance
chris


-----Ursprüngliche Nachricht-----
Von: Igor Vaynberg [mailto:[hidden email]]
Gesendet: Mi 23.09.2009 19:20
An: [hidden email]
Betreff: Re: FXValidationAjaxHandler - Javascript not added if component is set visible(false) in page constructor
 
javascript contributions do not show up for components that are not
visible, add it to a visible component instead.

-igor

On Wed, Sep 23, 2009 at 7:15 AM, Giambalvo, Christian
<[hidden email]> wrote:

> Hi all,
>
> ich have a component (textfield) with an FXValidationAjaxHandler. If i
> set this component in pageconstructor to visible(false) then the needed
> javascript code for validation is not contributed to pageheader. if set
> to visible(true) all is fine.
> does anyone had the same problem and if so, is there a workaround
> available?
>
> greets chris
>
> snippet:
> ...
> pComponent.add(new FXValidationAjaxHandler(pFXJavascriptEvent));
> this.pComponent.setOutputMarkupPlaceholderTag(true);
> this.pComponent.setOutputMarkupId(true)
> this.pComponent.setVisible(false); // no javascript is added
> //this.pComponent.setVisible(true); // javascript is added
> form.add(this.pComponent);
> ...
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]


Reply | Threaded
Open this post in threaded view
|

Re: FXValidationAjaxHandler - Javascript not added if component is set visible(false) in page constructor

Igor Vaynberg-2
put the two panels into a parent container that is always visible.

-igor

On Wed, Sep 23, 2009 at 1:37 PM, Giambalvo, Christian
<[hidden email]> wrote:

> Hi,
>
> first thanks for reply.
> Well, it's not possible to add it to a visible component.
> Let me explain.
> I have 2 custom panels and depending on the selection in a dropdownchoice the corresponding panel gets visible or hidden. Because one of these panels need to be invisible on page construction (so not both are showing up) i need to set it invisible. If i then select it in the dropdownchoice i gets visible.
> And now the problem begins. Cause of the initial invisibility the needed javascript code for validation of the panel fields isn't injected. How can i workaround this?
>
> Thanks in advance
> chris
>
>
> -----Ursprüngliche Nachricht-----
> Von: Igor Vaynberg [mailto:[hidden email]]
> Gesendet: Mi 23.09.2009 19:20
> An: [hidden email]
> Betreff: Re: FXValidationAjaxHandler - Javascript not added if component is set visible(false) in page constructor
>
> javascript contributions do not show up for components that are not
> visible, add it to a visible component instead.
>
> -igor
>
> On Wed, Sep 23, 2009 at 7:15 AM, Giambalvo, Christian
> <[hidden email]> wrote:
>> Hi all,
>>
>> ich have a component (textfield) with an FXValidationAjaxHandler. If i
>> set this component in pageconstructor to visible(false) then the needed
>> javascript code for validation is not contributed to pageheader. if set
>> to visible(true) all is fine.
>> does anyone had the same problem and if so, is there a workaround
>> available?
>>
>> greets chris
>>
>> snippet:
>> ...
>> pComponent.add(new FXValidationAjaxHandler(pFXJavascriptEvent));
>> this.pComponent.setOutputMarkupPlaceholderTag(true);
>> this.pComponent.setOutputMarkupId(true)
>> this.pComponent.setVisible(false); // no javascript is added
>> //this.pComponent.setVisible(true); // javascript is added
>> form.add(this.pComponent);
>> ...
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

AW: FXValidationAjaxHandler - Javascript not added if component is set visible(false) in page constructor

christian.giambalvo
AW: FXValidationAjaxHandler - Javascript not added if component is set visible(false) in page constructor

i'm sorry, but doesn't work.

i attached a simple project.
i added the needed components to a webmarkupcontainer.
instead of panels this time i used requiredtextfields to keep it as simple as possible.
one textfield is visible the other invisible.

here is the generated markup:

<?xml version="1.0" encoding="UTF-8"?>
<html xmlns="http://www.w3.org/1999/xhtml" xmlns:wicket="http://wicket.apache.org/dtds.data/wicket-xhtml1.4-strict.dtd">
    <head>
        <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
        <title>Wicket Demo</title>
        <link rel="stylesheet" type="text/css" href="/css/style.css"/>
    <script type="text/javascript" src="resources/org.apache.wicket.markup.html.WicketEventReference/wicket-event.js"></script>
<script type="text/javascript" src="resources/org.apache.wicket.ajax.WicketAjaxReference/wicket-ajax.js"></script>
<script type="text/javascript" src="resources/org.apache.wicket.ajax.AbstractDefaultAjaxBehavior/wicket-ajax-debug.js"></script>

<script type="text/javascript" id="wicket-ajax-debug-enable"><!--/*--><![CDATA[/*><!--*/
wicketAjaxDebugEnable=true;
/*-->]]>*/</script>

<script type="text/javascript" id="org.wicketstuff.dojo.AbstractDefaultDojoBehavior/debug"><!--/*--><![CDATA[/*><!--*/
var djConfig = {};
djConfig.isDebug = true;
djConfig.parseWidgets = false;
djConfig.searchIds = []

/*-->]]>*/</script>

<script type="text/javascript" src="resources/org.wicketstuff.dojo.AbstractDefaultDojoBehavior/dojo-0.4/dojo.js"></script>
<script type="text/javascript" src="resources/org.wicketstuff.dojo.AbstractRequireDojoBehavior/dojo-wicket/dojoWicket.js"></script>
<script type="text/javascript" id="org.wicketstuff.dojo.AbstractDefaultDojoBehavior/namespaces/wicketstuff"><!--/*--><![CDATA[/*><!--*/
dojo.registerModulePath("wicketstuff", "../../../resources/org.wicketstuff.dojo.AbstractDefaultDojoBehavior");
/*-->]]>*/</script>

<script type="text/javascript" id="org.wicketstuff.dojo.AbstractDefaultDojoBehavior/consoleDebug"><!--/*--><![CDATA[/*><!--*/
dojo.require("dojo.debug.console");
dojo.require("dojo.widget.Tree");

/*-->]]>*/</script>

<script type="text/javascript" id="org.wicketstuff.dojo.AbstractRequireDojoBehavior"><!--/*--><![CDATA[/*><!--*/
        dojo.require("dojo.lfx.*");
        dojo.require("dojo.gfx.*");
        dojo.require("dojo.html.*");


/*-->]]>*/</script>

<script type="text/javascript" id="txt11DojoParse"><!--/*--><![CDATA[/*><!--*/
djConfig.searchIds.push("txt11");
/*-->]]>*/</script>

<script language='JavaScript' type='text/javascript'>
        var txt11_first = false;
        function txt11_validate(type) {
                with(dojo.byId('txt11').style){backgroundColor = '#FFF';}               if (type=='valid'){
                        dojo.lfx.html.highlight('txt11', dojo.gfx.color.hex2rgb('#98c27d'), 200).play(0)
                        dojo.lfx.html.unhighlight('txt11', dojo.gfx.color.hex2rgb('#98c27d'), 200).play(200)
                }else{
                        dojo.lfx.html.highlight('txt11', dojo.gfx.color.hex2rgb('#fc8682'), 200).play(0)
;                       dojo.lfx.html.unhighlight('txt11', dojo.gfx.color.hex2rgb('#fc8682'), 200).play(200)
;               }
        }
</script>
</head>
    <body>
        <span wicket:id="container">
            <input id="txt11" onblur="javascript:var wcall=wicketAjaxGet('?wicket:interface=:0:container:txt1::IActivePageBehaviorListener:0:&wicket:ignoreIfNotActive=true&amp;container:txt1=' + this.value, function() { }, function() { });return !wcall;" name="container:txt1" widgetId="txt11" value="" type="text" wicket:id="txt1"/>
            <input id="txt22" style="display:none"></input>
        </span>

    </body>
</html>



-----Ursprüngliche Nachricht-----
Von: Igor Vaynberg [[hidden email]]
Gesendet: Do 24.09.2009 00:06
An: [hidden email]
Betreff: Re: FXValidationAjaxHandler - Javascript not added if component is set visible(false) in page constructor

put the two panels into a parent container that is always visible.

-igor

On Wed, Sep 23, 2009 at 1:37 PM, Giambalvo, Christian
<[hidden email]> wrote:
> Hi,
>
> first thanks for reply.
> Well, it's not possible to add it to a visible component.
> Let me explain.
> I have 2 custom panels and depending on the selection in a dropdownchoice the corresponding panel gets visible or hidden. Because one of these panels need to be invisible on page construction (so not both are showing up) i need to set it invisible. If i then select it in the dropdownchoice i gets visible.
> And now the problem begins. Cause of the initial invisibility the needed javascript code for validation of the panel fields isn't injected. How can i workaround this?
>
> Thanks in advance
> chris
>
>
> -----Ursprüngliche Nachricht-----
> Von: Igor Vaynberg [[hidden email]]
> Gesendet: Mi 23.09.2009 19:20
> An: [hidden email]
> Betreff: Re: FXValidationAjaxHandler - Javascript not added if component is set visible(false) in page constructor
>
> javascript contributions do not show up for components that are not
> visible, add it to a visible component instead.
>
> -igor
>
> On Wed, Sep 23, 2009 at 7:15 AM, Giambalvo, Christian
> <[hidden email]> wrote:
>> Hi all,
>>
>> ich have a component (textfield) with an FXValidationAjaxHandler. If i
>> set this component in pageconstructor to visible(false) then the needed
>> javascript code for validation is not contributed to pageheader. if set
>> to visible(true) all is fine.
>> does anyone had the same problem and if so, is there a workaround
>> available?
>>
>> greets chris
>>
>> snippet:
>> ...
>> pComponent.add(new FXValidationAjaxHandler(pFXJavascriptEvent));
>> this.pComponent.setOutputMarkupPlaceholderTag(true);
>> this.pComponent.setOutputMarkupId(true)
>> this.pComponent.setVisible(false); // no javascript is added
>> //this.pComponent.setVisible(true); // javascript is added
>> form.add(this.pComponent);
>> ...
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]





---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Wicket-Test.tar.gz (16K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: FXValidationAjaxHandler - Javascript not added if component is set visible(false) in page constructor

Igor Vaynberg-2
i meant add the javascript to a container that is visible.

components that are not visible do not render their javascript, it
wouldnt make any sense for them to do otherwise.

-igor

On Wed, Sep 23, 2009 at 5:16 PM, Giambalvo, Christian
<[hidden email]> wrote:

> i'm sorry, but doesn't work.
>
> i attached a simple project.
> i added the needed components to a webmarkupcontainer.
> instead of panels this time i used requiredtextfields to keep it as simple
> as possible.
> one textfield is visible the other invisible.
>
> here is the generated markup:
>
> <?xml version="1.0" encoding="UTF-8"?>
> <html xmlns="http://www.w3.org/1999/xhtml"
> xmlns:wicket="http://wicket.apache.org/dtds.data/wicket-xhtml1.4-strict.dtd">
>     <head>
>         <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
>         <title>Wicket Demo</title>
>         <link rel="stylesheet" type="text/css" href="/css/style.css"/>
>     <script type="text/javascript"
> src="resources/org.apache.wicket.markup.html.WicketEventReference/wicket-event.js"></script>
> <script type="text/javascript"
> src="resources/org.apache.wicket.ajax.WicketAjaxReference/wicket-ajax.js"></script>
> <script type="text/javascript"
> src="resources/org.apache.wicket.ajax.AbstractDefaultAjaxBehavior/wicket-ajax-debug.js"></script>
>
> <script type="text/javascript"
> id="wicket-ajax-debug-enable"><!--/*--><![CDATA[/*><!--*/
> wicketAjaxDebugEnable=true;
> /*-->]]>*/</script>
>
> <script type="text/javascript"
> id="org.wicketstuff.dojo.AbstractDefaultDojoBehavior/debug"><!--/*--><![CDATA[/*><!--*/
> var djConfig = {};
> djConfig.isDebug = true;
> djConfig.parseWidgets = false;
> djConfig.searchIds = []
>
> /*-->]]>*/</script>
>
> <script type="text/javascript"
> src="resources/org.wicketstuff.dojo.AbstractDefaultDojoBehavior/dojo-0.4/dojo.js"></script>
> <script type="text/javascript"
> src="resources/org.wicketstuff.dojo.AbstractRequireDojoBehavior/dojo-wicket/dojoWicket.js"></script>
> <script type="text/javascript"
> id="org.wicketstuff.dojo.AbstractDefaultDojoBehavior/namespaces/wicketstuff"><!--/*--><![CDATA[/*><!--*/
> dojo.registerModulePath("wicketstuff",
> "../../../resources/org.wicketstuff.dojo.AbstractDefaultDojoBehavior");
> /*-->]]>*/</script>
>
> <script type="text/javascript"
> id="org.wicketstuff.dojo.AbstractDefaultDojoBehavior/consoleDebug"><!--/*--><![CDATA[/*><!--*/
> dojo.require("dojo.debug.console");
> dojo.require("dojo.widget.Tree");
>
> /*-->]]>*/</script>
>
> <script type="text/javascript"
> id="org.wicketstuff.dojo.AbstractRequireDojoBehavior"><!--/*--><![CDATA[/*><!--*/
>         dojo.require("dojo.lfx.*");
>         dojo.require("dojo.gfx.*");
>         dojo.require("dojo.html.*");
>
>
> /*-->]]>*/</script>
>
> <script type="text/javascript"
> id="txt11DojoParse"><!--/*--><![CDATA[/*><!--*/
> djConfig.searchIds.push("txt11");
> /*-->]]>*/</script>
>
> <script language='JavaScript' type='text/javascript'>
>         var txt11_first = false;
>         function txt11_validate(type) {
>                 with(dojo.byId('txt11').style){backgroundColor =
> '#FFF';}               if (type=='valid'){
>                         dojo.lfx.html.highlight('txt11',
> dojo.gfx.color.hex2rgb('#98c27d'), 200).play(0)
>                         dojo.lfx.html.unhighlight('txt11',
> dojo.gfx.color.hex2rgb('#98c27d'), 200).play(200)
>                 }else{
>                         dojo.lfx.html.highlight('txt11',
> dojo.gfx.color.hex2rgb('#fc8682'), 200).play(0)
> ;                       dojo.lfx.html.unhighlight('txt11',
> dojo.gfx.color.hex2rgb('#fc8682'), 200).play(200)
> ;               }
>         }
> </script>
> </head>
>     <body>
>         <span wicket:id="container">
>             <input id="txt11" onblur="javascript:var
> wcall=wicketAjaxGet('?wicket:interface=:0:container:txt1::IActivePageBehaviorListener:0:&wicket:ignoreIfNotActive=true&amp;container:txt1='
> + this.value, function() { }, function() { });return !wcall;"
> name="container:txt1" widgetId="txt11" value="" type="text"
> wicket:id="txt1"/>
>             <input id="txt22" style="display:none"></input>
>         </span>
>
>     </body>
> </html>
>
>
>
> -----Ursprüngliche Nachricht-----
> Von: Igor Vaynberg [mailto:[hidden email]]
> Gesendet: Do 24.09.2009 00:06
> An: [hidden email]
> Betreff: Re: FXValidationAjaxHandler - Javascript not added if component is
> set visible(false) in page constructor
>
> put the two panels into a parent container that is always visible.
>
> -igor
>
> On Wed, Sep 23, 2009 at 1:37 PM, Giambalvo, Christian
> <[hidden email]> wrote:
>> Hi,
>>
>> first thanks for reply.
>> Well, it's not possible to add it to a visible component.
>> Let me explain.
>> I have 2 custom panels and depending on the selection in a dropdownchoice
>> the corresponding panel gets visible or hidden. Because one of these panels
>> need to be invisible on page construction (so not both are showing up) i
>> need to set it invisible. If i then select it in the dropdownchoice i gets
>> visible.
>> And now the problem begins. Cause of the initial invisibility the needed
>> javascript code for validation of the panel fields isn't injected. How can i
>> workaround this?
>>
>> Thanks in advance
>> chris
>>
>>
>> -----Ursprüngliche Nachricht-----
>> Von: Igor Vaynberg [mailto:[hidden email]]
>> Gesendet: Mi 23.09.2009 19:20
>> An: [hidden email]
>> Betreff: Re: FXValidationAjaxHandler - Javascript not added if component
>> is set visible(false) in page constructor
>>
>> javascript contributions do not show up for components that are not
>> visible, add it to a visible component instead.
>>
>> -igor
>>
>> On Wed, Sep 23, 2009 at 7:15 AM, Giambalvo, Christian
>> <[hidden email]> wrote:
>>> Hi all,
>>>
>>> ich have a component (textfield) with an FXValidationAjaxHandler. If i
>>> set this component in pageconstructor to visible(false) then the needed
>>> javascript code for validation is not contributed to pageheader. if set
>>> to visible(true) all is fine.
>>> does anyone had the same problem and if so, is there a workaround
>>> available?
>>>
>>> greets chris
>>>
>>> snippet:
>>> ...
>>> pComponent.add(new FXValidationAjaxHandler(pFXJavascriptEvent));
>>> this.pComponent.setOutputMarkupPlaceholderTag(true);
>>> this.pComponent.setOutputMarkupId(true)
>>> this.pComponent.setVisible(false); // no javascript is added
>>> //this.pComponent.setVisible(true); // javascript is added
>>> form.add(this.pComponent);
>>> ...
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: [hidden email]
>>> For additional commands, e-mail: [hidden email]
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

AW: FXValidationAjaxHandler - Javascript not added if component is set visible(false) in page constructor

christian.giambalvo
well, it makes no sense to add the javascript to another container.
how should i validate the textfields if the javascript points to a different component?
or could you give me an example?


-----Ursprüngliche Nachricht-----
Von: Igor Vaynberg [mailto:[hidden email]]
Gesendet: Do 24.09.2009 02:32
An: [hidden email]
Betreff: Re: FXValidationAjaxHandler - Javascript not added if component is set visible(false) in page constructor
 
i meant add the javascript to a container that is visible.

components that are not visible do not render their javascript, it
wouldnt make any sense for them to do otherwise.

-igor

On Wed, Sep 23, 2009 at 5:16 PM, Giambalvo, Christian
<[hidden email]> wrote:

> i'm sorry, but doesn't work.
>
> i attached a simple project.
> i added the needed components to a webmarkupcontainer.
> instead of panels this time i used requiredtextfields to keep it as simple
> as possible.
> one textfield is visible the other invisible.
>
> here is the generated markup:
>
> <?xml version="1.0" encoding="UTF-8"?>
> <html xmlns="http://www.w3.org/1999/xhtml"
> xmlns:wicket="http://wicket.apache.org/dtds.data/wicket-xhtml1.4-strict.dtd">
>     <head>
>         <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
>         <title>Wicket Demo</title>
>         <link rel="stylesheet" type="text/css" href="/css/style.css"/>
>     <script type="text/javascript"
> src="resources/org.apache.wicket.markup.html.WicketEventReference/wicket-event.js"></script>
> <script type="text/javascript"
> src="resources/org.apache.wicket.ajax.WicketAjaxReference/wicket-ajax.js"></script>
> <script type="text/javascript"
> src="resources/org.apache.wicket.ajax.AbstractDefaultAjaxBehavior/wicket-ajax-debug.js"></script>
>
> <script type="text/javascript"
> id="wicket-ajax-debug-enable"><!--/*--><![CDATA[/*><!--*/
> wicketAjaxDebugEnable=true;
> /*-->]]>*/</script>
>
> <script type="text/javascript"
> id="org.wicketstuff.dojo.AbstractDefaultDojoBehavior/debug"><!--/*--><![CDATA[/*><!--*/
> var djConfig = {};
> djConfig.isDebug = true;
> djConfig.parseWidgets = false;
> djConfig.searchIds = []
>
> /*-->]]>*/</script>
>
> <script type="text/javascript"
> src="resources/org.wicketstuff.dojo.AbstractDefaultDojoBehavior/dojo-0.4/dojo.js"></script>
> <script type="text/javascript"
> src="resources/org.wicketstuff.dojo.AbstractRequireDojoBehavior/dojo-wicket/dojoWicket.js"></script>
> <script type="text/javascript"
> id="org.wicketstuff.dojo.AbstractDefaultDojoBehavior/namespaces/wicketstuff"><!--/*--><![CDATA[/*><!--*/
> dojo.registerModulePath("wicketstuff",
> "../../../resources/org.wicketstuff.dojo.AbstractDefaultDojoBehavior");
> /*-->]]>*/</script>
>
> <script type="text/javascript"
> id="org.wicketstuff.dojo.AbstractDefaultDojoBehavior/consoleDebug"><!--/*--><![CDATA[/*><!--*/
> dojo.require("dojo.debug.console");
> dojo.require("dojo.widget.Tree");
>
> /*-->]]>*/</script>
>
> <script type="text/javascript"
> id="org.wicketstuff.dojo.AbstractRequireDojoBehavior"><!--/*--><![CDATA[/*><!--*/
>         dojo.require("dojo.lfx.*");
>         dojo.require("dojo.gfx.*");
>         dojo.require("dojo.html.*");
>
>
> /*-->]]>*/</script>
>
> <script type="text/javascript"
> id="txt11DojoParse"><!--/*--><![CDATA[/*><!--*/
> djConfig.searchIds.push("txt11");
> /*-->]]>*/</script>
>
> <script language='JavaScript' type='text/javascript'>
>         var txt11_first = false;
>         function txt11_validate(type) {
>                 with(dojo.byId('txt11').style){backgroundColor =
> '#FFF';}               if (type=='valid'){
>                         dojo.lfx.html.highlight('txt11',
> dojo.gfx.color.hex2rgb('#98c27d'), 200).play(0)
>                         dojo.lfx.html.unhighlight('txt11',
> dojo.gfx.color.hex2rgb('#98c27d'), 200).play(200)
>                 }else{
>                         dojo.lfx.html.highlight('txt11',
> dojo.gfx.color.hex2rgb('#fc8682'), 200).play(0)
> ;                       dojo.lfx.html.unhighlight('txt11',
> dojo.gfx.color.hex2rgb('#fc8682'), 200).play(200)
> ;               }
>         }
> </script>
> </head>
>     <body>
>         <span wicket:id="container">
>             <input id="txt11" onblur="javascript:var
> wcall=wicketAjaxGet('?wicket:interface=:0:container:txt1::IActivePageBehaviorListener:0:&wicket:ignoreIfNotActive=true&amp;container:txt1='
> + this.value, function() { }, function() { });return !wcall;"
> name="container:txt1" widgetId="txt11" value="" type="text"
> wicket:id="txt1"/>
>             <input id="txt22" style="display:none"></input>
>         </span>
>
>     </body>
> </html>
>
>
>
> -----Ursprüngliche Nachricht-----
> Von: Igor Vaynberg [mailto:[hidden email]]
> Gesendet: Do 24.09.2009 00:06
> An: [hidden email]
> Betreff: Re: FXValidationAjaxHandler - Javascript not added if component is
> set visible(false) in page constructor
>
> put the two panels into a parent container that is always visible.
>
> -igor
>
> On Wed, Sep 23, 2009 at 1:37 PM, Giambalvo, Christian
> <[hidden email]> wrote:
>> Hi,
>>
>> first thanks for reply.
>> Well, it's not possible to add it to a visible component.
>> Let me explain.
>> I have 2 custom panels and depending on the selection in a dropdownchoice
>> the corresponding panel gets visible or hidden. Because one of these panels
>> need to be invisible on page construction (so not both are showing up) i
>> need to set it invisible. If i then select it in the dropdownchoice i gets
>> visible.
>> And now the problem begins. Cause of the initial invisibility the needed
>> javascript code for validation of the panel fields isn't injected. How can i
>> workaround this?
>>
>> Thanks in advance
>> chris
>>
>>
>> -----Ursprüngliche Nachricht-----
>> Von: Igor Vaynberg [mailto:[hidden email]]
>> Gesendet: Mi 23.09.2009 19:20
>> An: [hidden email]
>> Betreff: Re: FXValidationAjaxHandler - Javascript not added if component
>> is set visible(false) in page constructor
>>
>> javascript contributions do not show up for components that are not
>> visible, add it to a visible component instead.
>>
>> -igor
>>
>> On Wed, Sep 23, 2009 at 7:15 AM, Giambalvo, Christian
>> <[hidden email]> wrote:
>>> Hi all,
>>>
>>> ich have a component (textfield) with an FXValidationAjaxHandler. If i
>>> set this component in pageconstructor to visible(false) then the needed
>>> javascript code for validation is not contributed to pageheader. if set
>>> to visible(true) all is fine.
>>> does anyone had the same problem and if so, is there a workaround
>>> available?
>>>
>>> greets chris
>>>
>>> snippet:
>>> ...
>>> pComponent.add(new FXValidationAjaxHandler(pFXJavascriptEvent));
>>> this.pComponent.setOutputMarkupPlaceholderTag(true);
>>> this.pComponent.setOutputMarkupId(true)
>>> this.pComponent.setVisible(false); // no javascript is added
>>> //this.pComponent.setVisible(true); // javascript is added
>>> form.add(this.pComponent);
>>> ...
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: [hidden email]
>>> For additional commands, e-mail: [hidden email]
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]


Reply | Threaded
Open this post in threaded view
|

AW: FXValidationAjaxHandler - Javascript not added if component is set visible(false) in page constructor

christian.giambalvo
maybe i'm to stupid to understand what you mean.
so please provide an example.
thx

-----Ursprüngliche Nachricht-----
Von: Giambalvo, Christian [mailto:[hidden email]]
Gesendet: Do 24.09.2009 02:45
An: [hidden email]
Betreff: AW: FXValidationAjaxHandler - Javascript not added if component is set visible(false) in page constructor
 
well, it makes no sense to add the javascript to another container.
how should i validate the textfields if the javascript points to a different component?
or could you give me an example?


-----Ursprüngliche Nachricht-----
Von: Igor Vaynberg [mailto:[hidden email]]
Gesendet: Do 24.09.2009 02:32
An: [hidden email]
Betreff: Re: FXValidationAjaxHandler - Javascript not added if component is set visible(false) in page constructor
 
i meant add the javascript to a container that is visible.

components that are not visible do not render their javascript, it
wouldnt make any sense for them to do otherwise.

-igor

On Wed, Sep 23, 2009 at 5:16 PM, Giambalvo, Christian
<[hidden email]> wrote:

> i'm sorry, but doesn't work.
>
> i attached a simple project.
> i added the needed components to a webmarkupcontainer.
> instead of panels this time i used requiredtextfields to keep it as simple
> as possible.
> one textfield is visible the other invisible.
>
> here is the generated markup:
>
> <?xml version="1.0" encoding="UTF-8"?>
> <html xmlns="http://www.w3.org/1999/xhtml"
> xmlns:wicket="http://wicket.apache.org/dtds.data/wicket-xhtml1.4-strict.dtd">
>     <head>
>         <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
>         <title>Wicket Demo</title>
>         <link rel="stylesheet" type="text/css" href="/css/style.css"/>
>     <script type="text/javascript"
> src="resources/org.apache.wicket.markup.html.WicketEventReference/wicket-event.js"></script>
> <script type="text/javascript"
> src="resources/org.apache.wicket.ajax.WicketAjaxReference/wicket-ajax.js"></script>
> <script type="text/javascript"
> src="resources/org.apache.wicket.ajax.AbstractDefaultAjaxBehavior/wicket-ajax-debug.js"></script>
>
> <script type="text/javascript"
> id="wicket-ajax-debug-enable"><!--/*--><![CDATA[/*><!--*/
> wicketAjaxDebugEnable=true;
> /*-->]]>*/</script>
>
> <script type="text/javascript"
> id="org.wicketstuff.dojo.AbstractDefaultDojoBehavior/debug"><!--/*--><![CDATA[/*><!--*/
> var djConfig = {};
> djConfig.isDebug = true;
> djConfig.parseWidgets = false;
> djConfig.searchIds = []
>
> /*-->]]>*/</script>
>
> <script type="text/javascript"
> src="resources/org.wicketstuff.dojo.AbstractDefaultDojoBehavior/dojo-0.4/dojo.js"></script>
> <script type="text/javascript"
> src="resources/org.wicketstuff.dojo.AbstractRequireDojoBehavior/dojo-wicket/dojoWicket.js"></script>
> <script type="text/javascript"
> id="org.wicketstuff.dojo.AbstractDefaultDojoBehavior/namespaces/wicketstuff"><!--/*--><![CDATA[/*><!--*/
> dojo.registerModulePath("wicketstuff",
> "../../../resources/org.wicketstuff.dojo.AbstractDefaultDojoBehavior");
> /*-->]]>*/</script>
>
> <script type="text/javascript"
> id="org.wicketstuff.dojo.AbstractDefaultDojoBehavior/consoleDebug"><!--/*--><![CDATA[/*><!--*/
> dojo.require("dojo.debug.console");
> dojo.require("dojo.widget.Tree");
>
> /*-->]]>*/</script>
>
> <script type="text/javascript"
> id="org.wicketstuff.dojo.AbstractRequireDojoBehavior"><!--/*--><![CDATA[/*><!--*/
>         dojo.require("dojo.lfx.*");
>         dojo.require("dojo.gfx.*");
>         dojo.require("dojo.html.*");
>
>
> /*-->]]>*/</script>
>
> <script type="text/javascript"
> id="txt11DojoParse"><!--/*--><![CDATA[/*><!--*/
> djConfig.searchIds.push("txt11");
> /*-->]]>*/</script>
>
> <script language='JavaScript' type='text/javascript'>
>         var txt11_first = false;
>         function txt11_validate(type) {
>                 with(dojo.byId('txt11').style){backgroundColor =
> '#FFF';}               if (type=='valid'){
>                         dojo.lfx.html.highlight('txt11',
> dojo.gfx.color.hex2rgb('#98c27d'), 200).play(0)
>                         dojo.lfx.html.unhighlight('txt11',
> dojo.gfx.color.hex2rgb('#98c27d'), 200).play(200)
>                 }else{
>                         dojo.lfx.html.highlight('txt11',
> dojo.gfx.color.hex2rgb('#fc8682'), 200).play(0)
> ;                       dojo.lfx.html.unhighlight('txt11',
> dojo.gfx.color.hex2rgb('#fc8682'), 200).play(200)
> ;               }
>         }
> </script>
> </head>
>     <body>
>         <span wicket:id="container">
>             <input id="txt11" onblur="javascript:var
> wcall=wicketAjaxGet('?wicket:interface=:0:container:txt1::IActivePageBehaviorListener:0:&wicket:ignoreIfNotActive=true&amp;container:txt1='
> + this.value, function() { }, function() { });return !wcall;"
> name="container:txt1" widgetId="txt11" value="" type="text"
> wicket:id="txt1"/>
>             <input id="txt22" style="display:none"></input>
>         </span>
>
>     </body>
> </html>
>
>
>
> -----Ursprüngliche Nachricht-----
> Von: Igor Vaynberg [mailto:[hidden email]]
> Gesendet: Do 24.09.2009 00:06
> An: [hidden email]
> Betreff: Re: FXValidationAjaxHandler - Javascript not added if component is
> set visible(false) in page constructor
>
> put the two panels into a parent container that is always visible.
>
> -igor
>
> On Wed, Sep 23, 2009 at 1:37 PM, Giambalvo, Christian
> <[hidden email]> wrote:
>> Hi,
>>
>> first thanks for reply.
>> Well, it's not possible to add it to a visible component.
>> Let me explain.
>> I have 2 custom panels and depending on the selection in a dropdownchoice
>> the corresponding panel gets visible or hidden. Because one of these panels
>> need to be invisible on page construction (so not both are showing up) i
>> need to set it invisible. If i then select it in the dropdownchoice i gets
>> visible.
>> And now the problem begins. Cause of the initial invisibility the needed
>> javascript code for validation of the panel fields isn't injected. How can i
>> workaround this?
>>
>> Thanks in advance
>> chris
>>
>>
>> -----Ursprüngliche Nachricht-----
>> Von: Igor Vaynberg [mailto:[hidden email]]
>> Gesendet: Mi 23.09.2009 19:20
>> An: [hidden email]
>> Betreff: Re: FXValidationAjaxHandler - Javascript not added if component
>> is set visible(false) in page constructor
>>
>> javascript contributions do not show up for components that are not
>> visible, add it to a visible component instead.
>>
>> -igor
>>
>> On Wed, Sep 23, 2009 at 7:15 AM, Giambalvo, Christian
>> <[hidden email]> wrote:
>>> Hi all,
>>>
>>> ich have a component (textfield) with an FXValidationAjaxHandler. If i
>>> set this component in pageconstructor to visible(false) then the needed
>>> javascript code for validation is not contributed to pageheader. if set
>>> to visible(true) all is fine.
>>> does anyone had the same problem and if so, is there a workaround
>>> available?
>>>
>>> greets chris
>>>
>>> snippet:
>>> ...
>>> pComponent.add(new FXValidationAjaxHandler(pFXJavascriptEvent));
>>> this.pComponent.setOutputMarkupPlaceholderTag(true);
>>> this.pComponent.setOutputMarkupId(true)
>>> this.pComponent.setVisible(false); // no javascript is added
>>> //this.pComponent.setVisible(true); // javascript is added
>>> form.add(this.pComponent);
>>> ...
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: [hidden email]
>>> For additional commands, e-mail: [hidden email]
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]



Reply | Threaded
Open this post in threaded view
|

maven/quickstart question

chrisco484
I've been using wicket under for a while now, always using ant, but now
I have to create a quickstart app and I'm new to maven...

I've created the quickstart app and it runs under Jetty no problem but
where does it store the Wicket and Jetty .jars?

They don't seem to be under the directory I created using the maven
'archetype:create' command.

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: maven/quickstart question

Pedro Santos
They probably are at user home. You can know more about maven settings at:

http://maven.apache.org/settings.html
*
localRepository*: This value is the path of this build system's local
repository. The default value is ${user.home}/.m2/repository. This element
is especially useful for a main build server allowing all logged-in users to
build from a common local repository.

On Wed, Sep 23, 2009 at 11:01 PM, Chris Colman <[hidden email]
> wrote:

> I've been using wicket under for a while now, always using ant, but now
> I have to create a quickstart app and I'm new to maven...
>
> I've created the quickstart app and it runs under Jetty no problem but
> where does it store the Wicket and Jetty .jars?
>
> They don't seem to be under the directory I created using the maven
> 'archetype:create' command.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>


--
Pedro Henrique Oliveira dos Santos
Reply | Threaded
Open this post in threaded view
|

Re: FXValidationAjaxHandler - Javascript not added if component is set visible(false) in page constructor

jeremy@wickettraining.com
In reply to this post by christian.giambalvo
Why validate the input on a textfield that isn't displayed to the user?

--
Jeremy Thomerson
http://www.wickettraining.com



On Wed, Sep 23, 2009 at 7:45 PM, Giambalvo, Christian <
[hidden email]> wrote:

> well, it makes no sense to add the javascript to another container.
> how should i validate the textfields if the javascript points to a
> different component?
> or could you give me an example?
>
>
> -----Ursprüngliche Nachricht-----
> Von: Igor Vaynberg [mailto:[hidden email]]
> Gesendet: Do 24.09.2009 02:32
> An: [hidden email]
> Betreff: Re: FXValidationAjaxHandler - Javascript not added if component is
> set visible(false) in page constructor
>
> i meant add the javascript to a container that is visible.
>
> components that are not visible do not render their javascript, it
> wouldnt make any sense for them to do otherwise.
>
> -igor
>
> On Wed, Sep 23, 2009 at 5:16 PM, Giambalvo, Christian
> <[hidden email]> wrote:
> > i'm sorry, but doesn't work.
> >
> > i attached a simple project.
> > i added the needed components to a webmarkupcontainer.
> > instead of panels this time i used requiredtextfields to keep it as
> simple
> > as possible.
> > one textfield is visible the other invisible.
> >
> > here is the generated markup:
> >
> > <?xml version="1.0" encoding="UTF-8"?>
> > <html xmlns="http://www.w3.org/1999/xhtml"
> > xmlns:wicket="
> http://wicket.apache.org/dtds.data/wicket-xhtml1.4-strict.dtd">
> >     <head>
> >         <meta http-equiv="Content-Type" content="text/html;
> charset=UTF-8"/>
> >         <title>Wicket Demo</title>
> >         <link rel="stylesheet" type="text/css" href="/css/style.css"/>
> >     <script type="text/javascript"
> >
> src="resources/org.apache.wicket.markup.html.WicketEventReference/wicket-event.js"></script>
> > <script type="text/javascript"
> >
> src="resources/org.apache.wicket.ajax.WicketAjaxReference/wicket-ajax.js"></script>
> > <script type="text/javascript"
> >
> src="resources/org.apache.wicket.ajax.AbstractDefaultAjaxBehavior/wicket-ajax-debug.js"></script>
> >
> > <script type="text/javascript"
> > id="wicket-ajax-debug-enable"><!--/*--><![CDATA[/*><!--*/
> > wicketAjaxDebugEnable=true;
> > /*-->]]>*/</script>
> >
> > <script type="text/javascript"
> >
> id="org.wicketstuff.dojo.AbstractDefaultDojoBehavior/debug"><!--/*--><![CDATA[/*><!--*/
> > var djConfig = {};
> > djConfig.isDebug = true;
> > djConfig.parseWidgets = false;
> > djConfig.searchIds = []
> >
> > /*-->]]>*/</script>
> >
> > <script type="text/javascript"
> >
> src="resources/org.wicketstuff.dojo.AbstractDefaultDojoBehavior/dojo-0.4/dojo.js"></script>
> > <script type="text/javascript"
> >
> src="resources/org.wicketstuff.dojo.AbstractRequireDojoBehavior/dojo-wicket/dojoWicket.js"></script>
> > <script type="text/javascript"
> >
> id="org.wicketstuff.dojo.AbstractDefaultDojoBehavior/namespaces/wicketstuff"><!--/*--><![CDATA[/*><!--*/
> > dojo.registerModulePath("wicketstuff",
> > "../../../resources/org.wicketstuff.dojo.AbstractDefaultDojoBehavior");
> > /*-->]]>*/</script>
> >
> > <script type="text/javascript"
> >
> id="org.wicketstuff.dojo.AbstractDefaultDojoBehavior/consoleDebug"><!--/*--><![CDATA[/*><!--*/
> > dojo.require("dojo.debug.console");
> > dojo.require("dojo.widget.Tree");
> >
> > /*-->]]>*/</script>
> >
> > <script type="text/javascript"
> >
> id="org.wicketstuff.dojo.AbstractRequireDojoBehavior"><!--/*--><![CDATA[/*><!--*/
> >         dojo.require("dojo.lfx.*");
> >         dojo.require("dojo.gfx.*");
> >         dojo.require("dojo.html.*");
> >
> >
> > /*-->]]>*/</script>
> >
> > <script type="text/javascript"
> > id="txt11DojoParse"><!--/*--><![CDATA[/*><!--*/
> > djConfig.searchIds.push("txt11");
> > /*-->]]>*/</script>
> >
> > <script language='JavaScript' type='text/javascript'>
> >         var txt11_first = false;
> >         function txt11_validate(type) {
> >                 with(dojo.byId('txt11').style){backgroundColor =
> > '#FFF';}               if (type=='valid'){
> >                         dojo.lfx.html.highlight('txt11',
> > dojo.gfx.color.hex2rgb('#98c27d'), 200).play(0)
> >                         dojo.lfx.html.unhighlight('txt11',
> > dojo.gfx.color.hex2rgb('#98c27d'), 200).play(200)
> >                 }else{
> >                         dojo.lfx.html.highlight('txt11',
> > dojo.gfx.color.hex2rgb('#fc8682'), 200).play(0)
> > ;                       dojo.lfx.html.unhighlight('txt11',
> > dojo.gfx.color.hex2rgb('#fc8682'), 200).play(200)
> > ;               }
> >         }
> > </script>
> > </head>
> >     <body>
> >         <span wicket:id="container">
> >             <input id="txt11" onblur="javascript:var
> >
> wcall=wicketAjaxGet('?wicket:interface=:0:container:txt1::IActivePageBehaviorListener:0:&wicket:ignoreIfNotActive=true&amp;container:txt1='
> > + this.value, function() { }, function() { });return !wcall;"
> > name="container:txt1" widgetId="txt11" value="" type="text"
> > wicket:id="txt1"/>
> >             <input id="txt22" style="display:none"></input>
> >         </span>
> >
> >     </body>
> > </html>
> >
> >
> >
> > -----Ursprüngliche Nachricht-----
> > Von: Igor Vaynberg [mailto:[hidden email]]
> > Gesendet: Do 24.09.2009 00:06
> > An: [hidden email]
> > Betreff: Re: FXValidationAjaxHandler - Javascript not added if component
> is
> > set visible(false) in page constructor
> >
> > put the two panels into a parent container that is always visible.
> >
> > -igor
> >
> > On Wed, Sep 23, 2009 at 1:37 PM, Giambalvo, Christian
> > <[hidden email]> wrote:
> >> Hi,
> >>
> >> first thanks for reply.
> >> Well, it's not possible to add it to a visible component.
> >> Let me explain.
> >> I have 2 custom panels and depending on the selection in a
> dropdownchoice
> >> the corresponding panel gets visible or hidden. Because one of these
> panels
> >> need to be invisible on page construction (so not both are showing up) i
> >> need to set it invisible. If i then select it in the dropdownchoice i
> gets
> >> visible.
> >> And now the problem begins. Cause of the initial invisibility the needed
> >> javascript code for validation of the panel fields isn't injected. How
> can i
> >> workaround this?
> >>
> >> Thanks in advance
> >> chris
> >>
> >>
> >> -----Ursprüngliche Nachricht-----
> >> Von: Igor Vaynberg [mailto:[hidden email]]
> >> Gesendet: Mi 23.09.2009 19:20
> >> An: [hidden email]
> >> Betreff: Re: FXValidationAjaxHandler - Javascript not added if component
> >> is set visible(false) in page constructor
> >>
> >> javascript contributions do not show up for components that are not
> >> visible, add it to a visible component instead.
> >>
> >> -igor
> >>
> >> On Wed, Sep 23, 2009 at 7:15 AM, Giambalvo, Christian
> >> <[hidden email]> wrote:
> >>> Hi all,
> >>>
> >>> ich have a component (textfield) with an FXValidationAjaxHandler. If i
> >>> set this component in pageconstructor to visible(false) then the needed
> >>> javascript code for validation is not contributed to pageheader. if set
> >>> to visible(true) all is fine.
> >>> does anyone had the same problem and if so, is there a workaround
> >>> available?
> >>>
> >>> greets chris
> >>>
> >>> snippet:
> >>> ...
> >>> pComponent.add(new FXValidationAjaxHandler(pFXJavascriptEvent));
> >>> this.pComponent.setOutputMarkupPlaceholderTag(true);
> >>> this.pComponent.setOutputMarkupId(true)
> >>> this.pComponent.setVisible(false); // no javascript is added
> >>> //this.pComponent.setVisible(true); // javascript is added
> >>> form.add(this.pComponent);
> >>> ...
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: [hidden email]
> >>> For additional commands, e-mail: [hidden email]
> >>>
> >>>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: [hidden email]
> >> For additional commands, e-mail: [hidden email]
> >>
> >>
> >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [hidden email]
> > For additional commands, e-mail: [hidden email]
> >
> >
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [hidden email]
> > For additional commands, e-mail: [hidden email]
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>
>
Reply | Threaded
Open this post in threaded view
|

RE: maven/quickstart question

chrisco484
In reply to this post by Pedro Santos
Cool, thanks for the info. That repository looks like the manually
managed one I maintain for ant's use to allow sharing of jars across
multiple projects. I guess maven has automated that process somewhat.

> The default value is ${user.home}/.m2/repository. This element
> is especially useful for a main build server allowing all logged-in
users
> to build from a common local repository.
>
> On Wed, Sep 23, 2009 at 11:01 PM, Chris Colman
> <[hidden email]
> > wrote:
>
> > I've been using wicket under for a while now, always using ant, but
now
> > I have to create a quickstart app and I'm new to maven...
> >
> > I've created the quickstart app and it runs under Jetty no problem
but
> > where does it store the Wicket and Jetty .jars?
> >
> > They don't seem to be under the directory I created using the maven
> > 'archetype:create' command.
> >
> >
---------------------------------------------------------------------
> > To unsubscribe, e-mail: [hidden email]
> > For additional commands, e-mail: [hidden email]
> >
> >
>
>
> --
> Pedro Henrique Oliveira dos Santos

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

re: FXValidationAjaxHandler - Javascript not added if component is set visible(false) in page constructor

Cemal Bayramoglu
In reply to this post by christian.giambalvo
Chris,

The fact that you've chosen to use Wicket probably shows there's not so much danger of that!

To better see what's going on, try the snippet below in the project you attached

    // ... mark t2 final and
    // append this to your BasePage constructor
    con.add(t2.setOutputMarkupId(true));
    add(new AjaxLink("toggleVisiblity"){
       @Override
       public void onClick(AjaxRequestTarget target) {
           t2.setVisible(!t2.isVisible());
           target.addComponent(t2);
       }
    });

Fix your BasePage.html accordingly eg, add an anchor to the body with wicket:id="toggleVisiblity".

When you fire up your app, click on that link once and you can use FireBug in Firefox to verify that the "onblur" code you wanted is indeed in place.

Is that the effect you were after?

Regards - Cemal
jWeekend
OO & Java Technologies, Wicket Training and Development
http://jWeekend.com

PS Nabble is not showing posts to our list (I think it's pointing back to SourceForge again!) so I am replying here in case you need a solution quickly and this happens to be the actual issue you are faced with!


> maybe i'm to stupid to understand what you mean.
> so please provide an example.
> thx
>
> -----Ursprüngliche Nachricht-----
> Von: Giambalvo, Christian [mailto:[hidden email]]
> Gesendet: Do 24.09.2009 02:45
> An: [hidden email]
> Betreff: AW: FXValidationAjaxHandler - Javascript not added if component is set visible(false) in page constructor
> - Hide quoted text -
>
> well, it makes no sense to add the javascript to another container.
> how should i validate the textfields if the javascript points to a different component?
> or could you give me an example?
>
>
> -----Ursprüngliche Nachricht-----
> Von: Igor Vaynberg [mailto:[hidden email]]
> Gesendet: Do 24.09.2009 02:32
> An: [hidden email]
> Betreff: Re: FXValidationAjaxHandler - Javascript not added if component is set visible(false) in page constructor
>
> i meant add the javascript to a container that is visible.
>
> components that are not visible do not render their javascript, it
> wouldnt make any sense for them to do otherwise.
>
> -igor
>
> On Wed, Sep 23, 2009 at 5:16 PM, Giambalvo, Christian
> <[hidden email]> wrote:
>> i'm sorry, but doesn't work.
>>
>> i attached a simple project.
>> i added the needed components to a webmarkupcontainer.
>> instead of panels this time i used requiredtextfields to keep it as simple
>> as possible.
>> one textfield is visible the other invisible.
>>
>> here is the generated markup:
>>
>> <?xml version="1.0" encoding="UTF-8"?>
>> <html xmlns="http://www.w3.org/1999/xhtml"
>> xmlns:wicket="http://wicket.apache.org/dtds.data/wicket-xhtml1.4-strict.dtd">
>>     <head>
>>         <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
>>         <title>Wicket Demo</title>
>>         <link rel="stylesheet" type="text/css" href="/css/style.css"/>
>>     <script type="text/javascript"
>> src="resources/org.apache.wicket.markup.html.WicketEventReference/wicket-event.js"></script>
>> <script type="text/javascript"
>> src="resources/org.apache.wicket.ajax.WicketAjaxReference/wicket-ajax.js"></script>
>> <script type="text/javascript"
>> src="resources/org.apache.wicket.ajax.AbstractDefaultAjaxBehavior/wicket-ajax-debug.js"></script>
>>
>> <script type="text/javascript"
>> id="wicket-ajax-debug-enable"><!--/*--><![CDATA[/*><!--*/
>> wicketAjaxDebugEnable=true;
>> /*-->]]>*/</script>
>>
>> <script type="text/javascript"
>> id="org.wicketstuff.dojo.AbstractDefaultDojoBehavior/debug"><!--/*--><![CDATA[/*><!--*/
>> var djConfig = {};
>> djConfig.isDebug = true;
>> djConfig.parseWidgets = false;
>> djConfig.searchIds = []
>>
>> /*-->]]>*/</script>
>>
>> <script type="text/javascript"
>> src="resources/org.wicketstuff.dojo.AbstractDefaultDojoBehavior/dojo-0.4/dojo.js"></script>
>> <script type="text/javascript"
>> src="resources/org.wicketstuff.dojo.AbstractRequireDojoBehavior/dojo-wicket/dojoWicket.js"></script>
>> <script type="text/javascript"
>> id="org.wicketstuff.dojo.AbstractDefaultDojoBehavior/namespaces/wicketstuff"><!--/*--><![CDATA[/*><!--*/
>> dojo.registerModulePath("wicketstuff",
>> "../../../resources/org.wicketstuff.dojo.AbstractDefaultDojoBehavior");
>> /*-->]]>*/</script>
>>
>> <script type="text/javascript"
>> id="org.wicketstuff.dojo.AbstractDefaultDojoBehavior/consoleDebug"><!--/*--><![CDATA[/*><!--*/
>> dojo.require("dojo.debug.console");
>> dojo.require("dojo.widget.Tree");
>>
>> /*-->]]>*/</script>
>>
>> <script type="text/javascript"
>> id="org.wicketstuff.dojo.AbstractRequireDojoBehavior"><!--/*--><![CDATA[/*><!--*/
>>         dojo.require("dojo.lfx.*");
>>         dojo.require("dojo.gfx.*");
>>         dojo.require("dojo.html.*");
>>
>>
>> /*-->]]>*/</script>
>>
>> <script type="text/javascript"
>> id="txt11DojoParse"><!--/*--><![CDATA[/*><!--*/
>> djConfig.searchIds.push("txt11");
>> /*-->]]>*/</script>
>>
>> <script language='JavaScript' type='text/javascript'>
>>         var txt11_first = false;
>>         function txt11_validate(type) {
>>                 with(dojo.byId('txt11').style){backgroundColor =
>> '#FFF';}               if (type=='valid'){
>>                         dojo.lfx.html.highlight('txt11',
>> dojo.gfx.color.hex2rgb('#98c27d'), 200).play(0)
>>                         dojo.lfx.html.unhighlight('txt11',
>> dojo.gfx.color.hex2rgb('#98c27d'), 200).play(200)
>>                 }else{
>>                         dojo.lfx.html.highlight('txt11',
>> dojo.gfx.color.hex2rgb('#fc8682'), 200).play(0)
>> ;                       dojo.lfx.html.unhighlight('txt11',
>> dojo.gfx.color.hex2rgb('#fc8682'), 200).play(200)
>> ;               }
>>         }
>> </script>
>> </head>
>>     <body>
>>         <span wicket:id="container">
>>             <input id="txt11" onblur="javascript:var
>> wcall=wicketAjaxGet('?wicket:interface=:0:container:txt1::IActivePageBehaviorListener:0:&wicket:ignoreIfNotActive=true&amp;container:txt1='
>> + this.value, function() { }, function() { });return !wcall;"
>> name="container:txt1" widgetId="txt11" value="" type="text"
>> wicket:id="txt1"/>
>>             <input id="txt22" style="display:none"></input>
>>         </span>
>>
>>     </body>
>> </html>
>>
>>
>>
>> -----Ursprüngliche Nachricht-----
>> Von: Igor Vaynberg [mailto:[hidden email]]
>> Gesendet: Do 24.09.2009 00:06
>> An: [hidden email]
>> Betreff: Re: FXValidationAjaxHandler - Javascript not added if component is
>> set visible(false) in page constructor
>>
>> put the two panels into a parent container that is always visible.
>>
>> -igor
>>
>> On Wed, Sep 23, 2009 at 1:37 PM, Giambalvo, Christian
>> <[hidden email]> wrote:
>>> Hi,
>>>
>>> first thanks for reply.
>>> Well, it's not possible to add it to a visible component.
>>> Let me explain.
>>> I have 2 custom panels and depending on the selection in a dropdownchoice
>>> the corresponding panel gets visible or hidden. Because one of these panels
>>> need to be invisible on page construction (so not both are showing up) i
>>> need to set it invisible. If i then select it in the dropdownchoice i gets
>>> visible.
>>> And now the problem begins. Cause of the initial invisibility the needed
>>> javascript code for validation of the panel fields isn't injected. How can i
>>> workaround this?
>>>
>>> Thanks in advance
>>> chris
>>>
>>>
>>> -----Ursprüngliche Nachricht-----
>>> Von: Igor Vaynberg [mailto:[hidden email]]
>>> Gesendet: Mi 23.09.2009 19:20
>>> An: [hidden email]
>>> Betreff: Re: FXValidationAjaxHandler - Javascript not added if component
>>> is set visible(false) in page constructor
>>>
>>> javascript contributions do not show up for components that are not
>>> visible, add it to a visible component instead.
>>>
>>> -igor
>>>
>>> On Wed, Sep 23, 2009 at 7:15 AM, Giambalvo, Christian
>>> <[hidden email]> wrote:
>>>> Hi all,
>>>>
>>>> ich have a component (textfield) with an FXValidationAjaxHandler. If i
>>>> set this component in pageconstructor to visible(false) then the needed
>>>> javascript code for validation is not contributed to pageheader. if set
>>>> to visible(true) all is fine.
>>>> does anyone had the same problem and if so, is there a workaround
>>>> available?
>>>>
>>>> greets chris
>>>>
>>>> snippet:
>>>> ...
>>>> pComponent.add(new FXValidationAjaxHandler(pFXJavascriptEvent));
>>>> this.pComponent.setOutputMarkupPlaceholderTag(true);
>>>> this.pComponent.setOutputMarkupId(true)
>>>> this.pComponent.setVisible(false); // no javascript is added
>>>> //this.pComponent.setVisible(true); // javascript is added
>>>> form.add(this.pComponent);
>>>> ...
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: [hidden email]
>>>> For additional commands, e-mail: [hidden email]
>>>>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: [hidden email]
>>> For additional commands, e-mail: [hidden email]
>>>
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>



---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Date validation in a form

Charles Moulliard
In reply to this post by Charles Moulliard
I would like to know How I can validate the string date inputted by a
user in a textfield of my form ?

e.g : The SimpleDateformat to be used to create a java Date is : dd/MM/yyyy
So I would like to check that the user has well introduced its date
using this format

Regards,

Charles Moulliard
Senior Enterprise Architect
Apache Camel Committer

*****************************
blog : http://cmoulliard.blogspot.com

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

AW: Date validation in a form

christian.giambalvo
What about org.apache.wicket.validation.validator.PatternValidator

Mit freundlichen Grüßen
Christian Giambalvo
--
Fachinformatiker für Anwendungsentwicklung

EXCELSIS Informationssysteme GmbH
Wilhelmsplatz 8 - 70182 Stuttgart
Mobile +49 176 196 32 406
Office +49 711 6 20 30 406
[hidden email]
www.excelsisnet.com
 
Sitz Stuttgart
Amtsgericht Stuttgart, HRB 21104
Geschäftsführer: Christian Sauter, Dr. Nils Herda, Frank Wolf

-----Ursprüngliche Nachricht-----
Von: Charles Moulliard [mailto:[hidden email]]
Gesendet: Donnerstag, 24. September 2009 10:10
An: [hidden email]
Betreff: Date validation in a form

I would like to know How I can validate the string date inputted by a
user in a textfield of my form ?

e.g : The SimpleDateformat to be used to create a java Date is : dd/MM/yyyy
So I would like to check that the user has well introduced its date
using this format

Regards,

Charles Moulliard
Senior Enterprise Architect
Apache Camel Committer

*****************************
blog : http://cmoulliard.blogspot.com

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Date validation in a form

Per Lundholm
In reply to this post by Charles Moulliard
Hi!

Don't forget to setLenient false.

Hope snippet below is enough.

/Per

public final class LocalDateFormatValidator extends StringValidator {
    private static final long serialVersionUID = 1L;
    private final SimpleDateFormat dateFormat;

    public LocalDateFormatValidator(Locale locale) {
        this.dateFormat = (SimpleDateFormat) new
DateConverter().getDateFormat(locale);
        this.dateFormat.setLenient(false);
    }

(...)

    @Override
    protected void onValidate(IValidatable<String> validatable) {
        String dateString = validatable.getValue();
        try {
            dateFormat.parse(dateString);
        } catch (ParseException e) {
            error(validatable);
        }
    }
}

On Thu, Sep 24, 2009 at 10:10 AM, Charles Moulliard <[hidden email]>wrote:

> I would like to know How I can validate the string date inputted by a
> user in a textfield of my form ?
>
> e.g : The SimpleDateformat to be used to create a java Date is : dd/MM/yyyy
> So I would like to check that the user has well introduced its date
> using this format
>
> Regards,
>
> Charles Moulliard
> Senior Enterprise Architect
> Apache Camel Committer
>
> *****************************
> blog : http://cmoulliard.blogspot.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>
Reply | Threaded
Open this post in threaded view
|

Re: Date validation in a form

Reinout van Schouwen-4
In reply to this post by Igor Vaynberg-2
Hi,

Op woensdag 23-09-2009 om 10:38 uur [tijdzone -0700], schreef Igor
Vaynberg:
> see DateTextField in extensions
>
> > e.g : The SimpleDateformat to be used to create a java Date is : dd/MM/yyyy
> > So I would like to check that the user has well introduced its date
> > using this format

I happened to be looking for the same thing yesterday (more specifically
about how to do client side validation) and found these two interesting
links:

http://www.jroller.com/wireframe/entry/wicket_client_side_validation
http://cwiki.apache.org/WICKET/fancy-validation-using-ajax-alternatives-to-feedbackpanel.html

regards,

--
Reinout van Schouwen


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: FXValidationAjaxHandler - Javascript not added if component is set visible(false) in page constructor

nmelendez@getsense.com.ar
In reply to this post by Cemal Bayramoglu
hi, in your example, there aren't behaviours, or where are they?

On Thu, Sep 24, 2009 at 5:54 AM, jWeekend <[hidden email]>wrote:

> Chris,
>
> The fact that you've chosen to use Wicket probably shows there's not so
> much danger of that!
>
> To better see what's going on, try the snippet below in the project you
> attached
>   // ... mark t2 final and
>   // append this to your BasePage constructor
>   con.add(t2.setOutputMarkupId(true));
>   add(new AjaxLink("toggleVisiblity"){
>      @Override
>      public void onClick(AjaxRequestTarget target) {
>          t2.setVisible(!t2.isVisible());
>          target.addComponent(t2);
>      }
>   });
>
> Fix your BasePage.html accordingly eg, add an anchor to the body with
> wicket:id="toggleVisiblity".
>
> When you fire up your app, click on that link once and you can use FireBug
> in Firefox to verify that the "onblur" code you wanted is indeed in place.
>
> Is that the effect you were after?
>
> Regards - Cemal
> jWeekend
> OO & Java Technologies, Wicket Training and Development
> http://jWeekend.com
>
> PS Nabble is not showing posts to our list (I think it's pointing back to
> SourceForge again!) so I am replying here in case you need a solution
> quickly and this happens to be the actual issue you are faced with!
>
>
>  maybe i'm to stupid to understand what you mean.
>> so please provide an example.
>> thx
>>
>> -----Ursprüngliche Nachricht-----
>> Von: Giambalvo, Christian [mailto:[hidden email]]
>> Gesendet: Do 24.09.2009 02:45
>> An: [hidden email]
>> Betreff: AW: FXValidationAjaxHandler - Javascript not added if component
>> is set visible(false) in page constructor
>> - Hide quoted text -
>>
>>
>> well, it makes no sense to add the javascript to another container.
>> how should i validate the textfields if the javascript points to a
>> different component?
>> or could you give me an example?
>>
>>
>> -----Ursprüngliche Nachricht-----
>> Von: Igor Vaynberg [mailto:[hidden email]]
>> Gesendet: Do 24.09.2009 02:32
>> An: [hidden email]
>> Betreff: Re: FXValidationAjaxHandler - Javascript not added if component
>> is set visible(false) in page constructor
>>
>> i meant add the javascript to a container that is visible.
>>
>> components that are not visible do not render their javascript, it
>> wouldnt make any sense for them to do otherwise.
>>
>> -igor
>>
>> On Wed, Sep 23, 2009 at 5:16 PM, Giambalvo, Christian
>> <[hidden email]> wrote:
>>
>>> i'm sorry, but doesn't work.
>>>
>>> i attached a simple project.
>>> i added the needed components to a webmarkupcontainer.
>>> instead of panels this time i used requiredtextfields to keep it as
>>> simple
>>> as possible.
>>> one textfield is visible the other invisible.
>>>
>>> here is the generated markup:
>>>
>>> <?xml version="1.0" encoding="UTF-8"?>
>>> <html xmlns="http://www.w3.org/1999/xhtml"
>>> xmlns:wicket="
>>> http://wicket.apache.org/dtds.data/wicket-xhtml1.4-strict.dtd">
>>>    <head>
>>>        <meta http-equiv="Content-Type" content="text/html;
>>> charset=UTF-8"/>
>>>        <title>Wicket Demo</title>
>>>        <link rel="stylesheet" type="text/css" href="/css/style.css"/>
>>>    <script type="text/javascript"
>>>
>>> src="resources/org.apache.wicket.markup.html.WicketEventReference/wicket-event.js"></script>
>>> <script type="text/javascript"
>>>
>>> src="resources/org.apache.wicket.ajax.WicketAjaxReference/wicket-ajax.js"></script>
>>> <script type="text/javascript"
>>>
>>> src="resources/org.apache.wicket.ajax.AbstractDefaultAjaxBehavior/wicket-ajax-debug.js"></script>
>>>
>>> <script type="text/javascript"
>>> id="wicket-ajax-debug-enable"><!--/*--><![CDATA[/*><!--*/
>>> wicketAjaxDebugEnable=true;
>>> /*-->]]>*/</script>
>>>
>>> <script type="text/javascript"
>>>
>>> id="org.wicketstuff.dojo.AbstractDefaultDojoBehavior/debug"><!--/*--><![CDATA[/*><!--*/
>>> var djConfig = {};
>>> djConfig.isDebug = true;
>>> djConfig.parseWidgets = false;
>>> djConfig.searchIds = []
>>>
>>> /*-->]]>*/</script>
>>>
>>> <script type="text/javascript"
>>>
>>> src="resources/org.wicketstuff.dojo.AbstractDefaultDojoBehavior/dojo-0.4/dojo.js"></script>
>>> <script type="text/javascript"
>>>
>>> src="resources/org.wicketstuff.dojo.AbstractRequireDojoBehavior/dojo-wicket/dojoWicket.js"></script>
>>> <script type="text/javascript"
>>>
>>> id="org.wicketstuff.dojo.AbstractDefaultDojoBehavior/namespaces/wicketstuff"><!--/*--><![CDATA[/*><!--*/
>>> dojo.registerModulePath("wicketstuff",
>>> "../../../resources/org.wicketstuff.dojo.AbstractDefaultDojoBehavior");
>>> /*-->]]>*/</script>
>>>
>>> <script type="text/javascript"
>>>
>>> id="org.wicketstuff.dojo.AbstractDefaultDojoBehavior/consoleDebug"><!--/*--><![CDATA[/*><!--*/
>>> dojo.require("dojo.debug.console");
>>> dojo.require("dojo.widget.Tree");
>>>
>>> /*-->]]>*/</script>
>>>
>>> <script type="text/javascript"
>>>
>>> id="org.wicketstuff.dojo.AbstractRequireDojoBehavior"><!--/*--><![CDATA[/*><!--*/
>>>        dojo.require("dojo.lfx.*");
>>>        dojo.require("dojo.gfx.*");
>>>        dojo.require("dojo.html.*");
>>>
>>>
>>> /*-->]]>*/</script>
>>>
>>> <script type="text/javascript"
>>> id="txt11DojoParse"><!--/*--><![CDATA[/*><!--*/
>>> djConfig.searchIds.push("txt11");
>>> /*-->]]>*/</script>
>>>
>>> <script language='JavaScript' type='text/javascript'>
>>>        var txt11_first = false;
>>>        function txt11_validate(type) {
>>>                with(dojo.byId('txt11').style){backgroundColor =
>>> '#FFF';}               if (type=='valid'){
>>>                        dojo.lfx.html.highlight('txt11',
>>> dojo.gfx.color.hex2rgb('#98c27d'), 200).play(0)
>>>                        dojo.lfx.html.unhighlight('txt11',
>>> dojo.gfx.color.hex2rgb('#98c27d'), 200).play(200)
>>>                }else{
>>>                        dojo.lfx.html.highlight('txt11',
>>> dojo.gfx.color.hex2rgb('#fc8682'), 200).play(0)
>>> ;                       dojo.lfx.html.unhighlight('txt11',
>>> dojo.gfx.color.hex2rgb('#fc8682'), 200).play(200)
>>> ;               }
>>>        }
>>> </script>
>>> </head>
>>>    <body>
>>>        <span wicket:id="container">
>>>            <input id="txt11" onblur="javascript:var
>>>
>>> wcall=wicketAjaxGet('?wicket:interface=:0:container:txt1::IActivePageBehaviorListener:0:&wicket:ignoreIfNotActive=true&amp;container:txt1='
>>> + this.value, function() { }, function() { });return !wcall;"
>>> name="container:txt1" widgetId="txt11" value="" type="text"
>>> wicket:id="txt1"/>
>>>            <input id="txt22" style="display:none"></input>
>>>        </span>
>>>
>>>    </body>
>>> </html>
>>>
>>>
>>>
>>> -----Ursprüngliche Nachricht-----
>>> Von: Igor Vaynberg [mailto:[hidden email]]
>>> Gesendet: Do 24.09.2009 00:06
>>> An: [hidden email]
>>> Betreff: Re: FXValidationAjaxHandler - Javascript not added if component
>>> is
>>> set visible(false) in page constructor
>>>
>>> put the two panels into a parent container that is always visible.
>>>
>>> -igor
>>>
>>> On Wed, Sep 23, 2009 at 1:37 PM, Giambalvo, Christian
>>> <[hidden email]> wrote:
>>>
>>>> Hi,
>>>>
>>>> first thanks for reply.
>>>> Well, it's not possible to add it to a visible component.
>>>> Let me explain.
>>>> I have 2 custom panels and depending on the selection in a
>>>> dropdownchoice
>>>> the corresponding panel gets visible or hidden. Because one of these
>>>> panels
>>>> need to be invisible on page construction (so not both are showing up) i
>>>> need to set it invisible. If i then select it in the dropdownchoice i
>>>> gets
>>>> visible.
>>>> And now the problem begins. Cause of the initial invisibility the needed
>>>> javascript code for validation of the panel fields isn't injected. How
>>>> can i
>>>> workaround this?
>>>>
>>>> Thanks in advance
>>>> chris
>>>>
>>>>
>>>> -----Ursprüngliche Nachricht-----
>>>> Von: Igor Vaynberg [mailto:[hidden email]]
>>>> Gesendet: Mi 23.09.2009 19:20
>>>> An: [hidden email]
>>>> Betreff: Re: FXValidationAjaxHandler - Javascript not added if component
>>>> is set visible(false) in page constructor
>>>>
>>>> javascript contributions do not show up for components that are not
>>>> visible, add it to a visible component instead.
>>>>
>>>> -igor
>>>>
>>>> On Wed, Sep 23, 2009 at 7:15 AM, Giambalvo, Christian
>>>> <[hidden email]> wrote:
>>>>
>>>>> Hi all,
>>>>>
>>>>> ich have a component (textfield) with an FXValidationAjaxHandler. If i
>>>>> set this component in pageconstructor to visible(false) then the needed
>>>>> javascript code for validation is not contributed to pageheader. if set
>>>>> to visible(true) all is fine.
>>>>> does anyone had the same problem and if so, is there a workaround
>>>>> available?
>>>>>
>>>>> greets chris
>>>>>
>>>>> snippet:
>>>>> ...
>>>>> pComponent.add(new FXValidationAjaxHandler(pFXJavascriptEvent));
>>>>> this.pComponent.setOutputMarkupPlaceholderTag(true);
>>>>> this.pComponent.setOutputMarkupId(true)
>>>>> this.pComponent.setVisible(false); // no javascript is added
>>>>> //this.pComponent.setVisible(true); // javascript is added
>>>>> form.add(this.pComponent);
>>>>> ...
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: [hidden email]
>>>>> For additional commands, e-mail: [hidden email]
>>>>>
>>>>>
>>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: [hidden email]
>>>> For additional commands, e-mail: [hidden email]
>>>>
>>>>
>>>>
>>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: [hidden email]
>>> For additional commands, e-mail: [hidden email]
>>>
>>>
>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: [hidden email]
>>> For additional commands, e-mail: [hidden email]
>>>
>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>