Avoiding "validate" event after "canceled" from BeanEditForm
Hi all! I have a t:beaneditform with t:cancel="true" When I click on cacel, I handle it with a onCanceledFromMyForm() handler, and here return another page. My problem is that after the "canceled" event the "validate" is fired, and my onValidateFromMyForm() handler is called, recording form errors shown when I return to this page. I suppose that the "validate" event shouldn't be fired after "canceled" one, don't you? Or is there another way to handle with this scenario, perhaps? The only work arround I found, is having a boolean page field, set to true in onCanceled handler and checking it in onValidate one... but I think it is quite tricky... I'll apreciate any advise! Regards, Matias.
Re: Tapestry5-JQuery Integration and tapestry-beanvalidator
Hi Emmanuel,
Yes! It worked fine!! Thank all you very much!
Now I am migrating a lot of prototype-like scripts to jquery api.
I will back to you with my experience!
Regards,
Matías.
Hi Matias,
Have you tested the solution, provided by Clément on Github ?
Thanks
Emmanuel
Saludos,
Matias.
On Wed, Jun 22, 2011 at 1:38 PM, Matias Blasi wrote:
> Hi Clément,
>
> I updated tapestry-jquery and I got the following new error:
>
> missing ; before statement
> tapestry-beanvalidator.js()tapestry-beanvalidator.js (line 15)
> var Tapestry.Validator={};
>
> Regards,
> Matias.
>
> >> You're welcome.
>
> >>
>
> >> I've just pushed some code on github for bean validator support. >> Feel
> free to test it, don't forget to update dependencies (the new jar is >>
> ready). :) >>
>
> >> Regards, >> Clément
>
> On Wed, Jun 22, 2011 at 1:17 PM, Matias Blasi wrote:
>
>> Thank you very much again Clément!
>>
>> I'm going to start migrating all my scripts.
>>
>> Regards,
>> Matías.
>>
>>
>> >> The Class you use is Prototype specific. >> As long as tapestry5-jquery
>> removes Prototype, you can't use it anymore. >> jQuery prefers to use
>> plugins -> http://docs.jquery.com/Plugins/Authoring >> or widgets (which
>> is a pattern used by jquery ui, also included in >> tapestry5-jquery) ->
>> http://jqueryui.com/docs/Developer_Guide
>>
>> On Wed, Jun 22, 2011 at 1:04 PM, Matias Blasi wrote:
>>
>>> Hi, Its me again...
>>>
>>> After skiping this issue, I am getting the following javascript error:
>>>
>>> Class is not defined
>>> MyType = Class.create({...
>>>
>>> It fails since I added tapestry5-jquery module, too.
>>> I do that every time I want to define a new Javascript type... Is there
>>> another compatible way to do that?
>>>
>>> Regards,
>>> Matias.
>>>
>>>
>>>
>>> On Wed, Jun 22, 2011 at 12:54 PM, Matias Blasi
>>> wrote:
>>>
>>>> It is not resolved by disabling the clientValidation of the form
>>>> components, it is resolved by removing the tapestry-beanvalidator module
>>>> dependency.
>>>> This module has the tapestry-beanvalidator.js which produces the
>>>> javascript error.
>>>>
>>>>
>>>> Regards,
>>>> Matias.
>>>>
>>>>
>>>>
>>>> On Wed, Jun 22, 2011 at 12:35 PM, Matias Blasi
>>>> wrote:
>>>>
>>>>> Thanks Clément,
>>>>>
>>>>> If I have a lot of forms in my application, is there any way to disable
>>>>> it globally?
>>>>>
>>>>> Best regards!
>>>>> Matías.
>>>>>
>>>>>
>>>>> The form component has a clientValidation parameter.
>>>>>
>>>>> On 22 June 2011 17:18, Matias Blasi wrote:
>>>>>
>>>>> Thank Clément,
>>>>>
>>>>> I will be waiting for this improvement anxiously!
>>>>>
>>>>> Just a question: Is there a quick way for disabling the client-side
>>>>> validation on tapestry framework?
>>>>>
>>>>> Regards,
>>>>>
>>>>> Matías.
>>>>>
>>>>> Hi Matias,
>>>>>
>>>>> Thanks for your feedback.
>>>>>
>>>>> Unfortunately bean validation doesn't work for the moment with got5
>>>>> tapestry5-jquery.
>>>>>
>>>>> I've just opened an issue.
>>>>> https://github.com/got5/tapestry5-jquery/issues/42
>>>>>
>>>>> Maybe you should try to disable client validation for the moment, until
>>>>> I
>>>>> (or someone) solve it.
>>>>>
>>>>> Regards, Clément
>>>>>
>>>>> On 21 June 2011 00:20, Matias Blasi wrote:
>>>>>
>>>>> Hi all
>>>>>
>>>>> I recently integrated my tapestry5 (5.2.5) application with the latest
>>>>> got5-jquery library (2.1.1)
>>>>>
>>>>> And I have the following error just entering to an empty page:
>>>>>
>>>>> Tapestry.Validator is undefined ---> Tapestry.Validator.notnull =
>>>>> function(field, message, spec) (tapestry-validator.js line 15) from
>>>>> tapestry-beanvalidator-5.2.5.jar
>>>>>
>>>>
>>>>
>>>
>>
>
Re: Tapestry5-JQuery Integration and tapestry-beanvalidator
Hi Clément,
I updated tapestry-jquery and I got the following new error:
missing ; before statement
tapestry-beanvalidator.js()tapestry-beanvalidator.js (line 15)
var Tapestry.Validator={};
Regards,
Matias.
>> You're welcome.
>>
>> I've just pushed some code on github for bean validator support. >> Feel
free to test it, don't forget to update dependencies (the new jar is >>
ready). :) >>
>> Regards, >> Clément
On Wed, Jun 22, 2011 at 1:17 PM, Matias Blasi wrote:
> Thank you very much again Clément!
>
> I'm going to start migrating all my scripts.
>
> Regards,
> Matías.
>
>
> >> The Class you use is Prototype specific. >> As long as tapestry5-jquery
> removes Prototype, you can't use it anymore. >> jQuery prefers to use
> plugins -> http://docs.jquery.com/Plugins/Authoring >> or widgets (which
> is a pattern used by jquery ui, also included in >> tapestry5-jquery) ->
> http://jqueryui.com/docs/Developer_Guide
>
> On Wed, Jun 22, 2011 at 1:04 PM, Matias Blasi wrote:
>
>> Hi, Its me again...
>>
>> After skiping this issue, I am getting the following javascript error:
>>
>> Class is not defined
>> MyType = Class.create({...
>>
>> It fails since I added tapestry5-jquery module, too.
>> I do that every time I want to define a new Javascript type... Is there
>> another compatible way to do that?
>>
>> Regards,
>> Matias.
>>
>>
>>
>> On Wed, Jun 22, 2011 at 12:54 PM, Matias Blasi wrote:
>>
>>> It is not resolved by disabling the clientValidation of the form
>>> components, it is resolved by removing the tapestry-beanvalidator module
>>> dependency.
>>> This module has the tapestry-beanvalidator.js which produces the
>>> javascript error.
>>>
>>>
>>> Regards,
>>> Matias.
>>>
>>>
>>>
>>> On Wed, Jun 22, 2011 at 12:35 PM, Matias Blasi
>>> wrote:
>>>
>>>> Thanks Clément,
>>>>
>>>> If I have a lot of forms in my application, is there any way to disable
>>>> it globally?
>>>>
>>>> Best regards!
>>>> Matías.
>>>>
>>>>
>>>> The form component has a clientValidation parameter.
>>>>
>>>> On 22 June 2011 17:18, Matias Blasi wrote:
>>>>
>>>> Thank Clément,
>>>>
>>>> I will be waiting for this improvement anxiously!
>>>>
>>>> Just a question: Is there a quick way for disabling the client-side
>>>> validation on tapestry framework?
>>>>
>>>> Regards,
>>>>
>>>> Matías.
>>>>
>>>> Hi Matias,
>>>>
>>>> Thanks for your feedback.
>>>>
>>>> Unfortunately bean validation doesn't work for the moment with got5
>>>> tapestry5-jquery.
>>>>
>>>> I've just opened an issue.
>>>> https://github.com/got5/tapestry5-jquery/issues/42
>>>>
>>>> Maybe you should try to disable client validation for the moment, until
>>>> I
>>>> (or someone) solve it.
>>>>
>>>> Regards, Clément
>>>>
>>>> On 21 June 2011 00:20, Matias Blasi wrote:
>>>>
>>>> Hi all
>>>>
>>>> I recently integrated my tapestry5 (5.2.5) application with the latest
>>>> got5-jquery library (2.1.1)
>>>>
>>>> And I have the following error just entering to an empty page:
>>>>
>>>> Tapestry.Validator is undefined ---> Tapestry.Validator.notnull =
>>>> function(field, message, spec) (tapestry-validator.js line 15) from
>>>> tapestry-beanvalidator-5.2.5.jar
>>>>
>>>
>>>
>>
>
Re: Tapestry5-JQuery Integration and tapestry-beanvalidator
Thank you very much again Clément!
I'm going to start migrating all my scripts.
Regards,
Matías.
>> The Class you use is Prototype specific. >> As long as tapestry5-jquery
removes Prototype, you can't use it anymore. >> jQuery prefers to use
plugins -> http://docs.jquery.com/Plugins/Authoring >> or widgets (which is
a pattern used by jquery ui, also included in >> tapestry5-jquery) ->
http://jqueryui.com/docs/Developer_Guide
On Wed, Jun 22, 2011 at 1:04 PM, Matias Blasi wrote:
> Hi, Its me again...
>
> After skiping this issue, I am getting the following javascript error:
>
> Class is not defined
> MyType = Class.create({...
>
> It fails since I added tapestry5-jquery module, too.
> I do that every time I want to define a new Javascript type... Is there
> another compatible way to do that?
>
> Regards,
> Matias.
>
>
>
> On Wed, Jun 22, 2011 at 12:54 PM, Matias Blasi wrote:
>
>> It is not resolved by disabling the clientValidation of the form
>> components, it is resolved by removing the tapestry-beanvalidator module
>> dependency.
>> This module has the tapestry-beanvalidator.js which produces the
>> javascript error.
>>
>>
>> Regards,
>> Matias.
>>
>>
>>
>> On Wed, Jun 22, 2011 at 12:35 PM, Matias Blasi wrote:
>>
>>> Thanks Clément,
>>>
>>> If I have a lot of forms in my application, is there any way to disable
>>> it globally?
>>>
>>> Best regards!
>>> Matías.
>>>
>>>
>>> The form component has a clientValidation parameter.
>>>
>>> On 22 June 2011 17:18, Matias Blasi wrote:
>>>
>>> Thank Clément,
>>>
>>> I will be waiting for this improvement anxiously!
>>>
>>> Just a question: Is there a quick way for disabling the client-side
>>> validation on tapestry framework?
>>>
>>> Regards,
>>>
>>> Matías.
>>>
>>> Hi Matias,
>>>
>>> Thanks for your feedback.
>>>
>>> Unfortunately bean validation doesn't work for the moment with got5
>>> tapestry5-jquery.
>>>
>>> I've just opened an issue.
>>> https://github.com/got5/tapestry5-jquery/issues/42
>>>
>>> Maybe you should try to disable client validation for the moment, until I
>>> (or someone) solve it.
>>>
>>> Regards, Clément
>>>
>>> On 21 June 2011 00:20, Matias Blasi wrote:
>>>
>>> Hi all
>>>
>>> I recently integrated my tapestry5 (5.2.5) application with the latest
>>> got5-jquery library (2.1.1)
>>>
>>> And I have the following error just entering to an empty page:
>>>
>>> Tapestry.Validator is undefined ---> Tapestry.Validator.notnull =
>>> function(field, message, spec) (tapestry-validator.js line 15) from
>>> tapestry-beanvalidator-5.2.5.jar
>>>
>>
>>
>
Re: Tapestry5-JQuery Integration and tapestry-beanvalidator
Hi, Its me again...
After skiping this issue, I am getting the following javascript error:
Class is not defined
MyType = Class.create({...
It fails since I added tapestry5-jquery module, too.
I do that every time I want to define a new Javascript type... Is there
another compatible way to do that?
Regards,
Matias.
On Wed, Jun 22, 2011 at 12:54 PM, Matias Blasi wrote:
> It is not resolved by disabling the clientValidation of the form
> components, it is resolved by removing the tapestry-beanvalidator module
> dependency.
> This module has the tapestry-beanvalidator.js which produces the javascript
> error.
>
>
> Regards,
> Matias.
>
>
>
> On Wed, Jun 22, 2011 at 12:35 PM, Matias Blasi wrote:
>
>> Thanks Clément,
>>
>> If I have a lot of forms in my application, is there any way to disable it
>> globally?
>>
>> Best regards!
>> Matías.
>>
>>
>> The form component has a clientValidation parameter.
>>
>> On 22 June 2011 17:18, Matias Blasi wrote:
>>
>> Thank Clément,
>>
>> I will be waiting for this improvement anxiously!
>>
>> Just a question: Is there a quick way for disabling the client-side
>> validation on tapestry framework?
>>
>> Regards,
>>
>> Matías.
>>
>> Hi Matias,
>>
>> Thanks for your feedback.
>>
>> Unfortunately bean validation doesn't work for the moment with got5
>> tapestry5-jquery.
>>
>> I've just opened an issue.
>> https://github.com/got5/tapestry5-jquery/issues/42
>>
>> Maybe you should try to disable client validation for the moment, until I
>> (or someone) solve it.
>>
>> Regards, Clément
>>
>> On 21 June 2011 00:20, Matias Blasi wrote:
>>
>> Hi all
>>
>> I recently integrated my tapestry5 (5.2.5) application with the latest
>> got5-jquery library (2.1.1)
>>
>> And I have the following error just entering to an empty page:
>>
>> Tapestry.Validator is undefined ---> Tapestry.Validator.notnull =
>> function(field, message, spec) (tapestry-validator.js line 15) from
>> tapestry-beanvalidator-5.2.5.jar
>>
>
>
Re: Tapestry5-JQuery Integration and tapestry-beanvalidator
It is not resolved by disabling the clientValidation of the form components, it is resolved by removing the tapestry-beanvalidator module dependency. This module has the tapestry-beanvalidator.js which produces the javascript error. Regards, Matias. On Wed, Jun 22, 2011 at 12:35 PM, Matias Blasi wrote: > Thanks Clément, > > If I have a lot of forms in my application, is there any way to disable it > globally? > > Best regards! > Matías. > > > The form component has a clientValidation parameter. > > On 22 June 2011 17:18, Matias Blasi wrote: > > Thank Clément, > > I will be waiting for this improvement anxiously! > > Just a question: Is there a quick way for disabling the client-side > validation on tapestry framework? > > Regards, > > Matías. > > Hi Matias, > > Thanks for your feedback. > > Unfortunately bean validation doesn't work for the moment with got5 > tapestry5-jquery. > > I've just opened an issue. > https://github.com/got5/tapestry5-jquery/issues/42 > > Maybe you should try to disable client validation for the moment, until I > (or someone) solve it. > > Regards, Clément > > On 21 June 2011 00:20, Matias Blasi wrote: > > Hi all > > I recently integrated my tapestry5 (5.2.5) application with the latest > got5-jquery library (2.1.1) > > And I have the following error just entering to an empty page: > > Tapestry.Validator is undefined ---> Tapestry.Validator.notnull = > function(field, message, spec) (tapestry-validator.js line 15) from > tapestry-beanvalidator-5.2.5.jar >
Re: Tapestry5-JQuery Integration and tapestry-beanvalidator
Thanks Clément, If I have a lot of forms in my application, is there any way to disable it globally? Best regards! Matías. The form component has a clientValidation parameter. On 22 June 2011 17:18, Matias Blasi wrote: Thank Clément, I will be waiting for this improvement anxiously! Just a question: Is there a quick way for disabling the client-side validation on tapestry framework? Regards, Matías. Hi Matias, Thanks for your feedback. Unfortunately bean validation doesn't work for the moment with got5 tapestry5-jquery. I've just opened an issue. https://github.com/got5/tapestry5-jquery/issues/42 Maybe you should try to disable client validation for the moment, until I (or someone) solve it. Regards, Clément On 21 June 2011 00:20, Matias Blasi wrote: Hi all I recently integrated my tapestry5 (5.2.5) application with the latest got5-jquery library (2.1.1) And I have the following error just entering to an empty page: Tapestry.Validator is undefined ---> Tapestry.Validator.notnull = function(field, message, spec) (tapestry-validator.js line 15) from tapestry-beanvalidator-5.2.5.jar
Re: Tapestry5-JQuery Integration and tapestry-beanvalidator
Thank Clément, I will be waiting for this improvement anxiously! Just a question: Is there a quick way for disabling the client-side validation on tapestry framework? Regards, Matías. Hi Matias, Thanks for your feedback. Unfortunately bean validation doesn't work for the moment with got5 tapestry5-jquery. I've just opened an issue. https://github.com/got5/tapestry5-jquery/issues/42 Maybe you should try to disable client validation for the moment, until I (or someone) solve it. Regards, Clément On 21 June 2011 00:20, Matias Blasi wrote: Hi all I recently integrated my tapestry5 (5.2.5) application with the latest got5-jquery library (2.1.1) And I have the following error just entering to an empty page: Tapestry.Validator is undefined ---> Tapestry.Validator.notnull = function(field, message, spec) (tapestry-validator.js line 15) from tapestry-beanvalidator-5.2.5.jar Is there any incompatibility between tapestry-beanvalidator and tapestry-jquery? Or am I loosing something? Regards, Matias.
Re: Trigger component event context
I am trying to make a zone works inside an ajaxformloop.
When the zone starts rendering it would be great to trigger an event with a
useful context in order to contextualize the rendering with the correct loop
value, this was my idea, but I am not sure to be able to provide a useful
context to that event which could be successfuly resolved during
zone-redenring phase to get the correct loop value...
For one side, I think that the trigger context parameter could be useful for
some cases... although, I think it will not help for my case.
Now I am thinking on another tricky solution:
Use the context parameter of the actionlink used to update the zone: This
paremter binding is resolved on each loop row rendering phase, so its value
is resolved correctly on each row.
Later, on the actionlink handler, I can use the recived context to trigger
an event programatically (ComponentResource.triggerEvent(eventType,
parameters[], callback)) in order to contextualize the page with the correct
row.
This task of "contextualize" the container on the correct loop row, that I
am resolving through the actionlink handler by triggering an event
programatically, I think that would be done on a more elegant way for
example with the trigger component but even if it has the context parameter
it will not work because it will be resolved till the zone is rendered...
and the binding will not work...
Do you think there is a more elegant way?
Here is a sample of my case:
Page.tml:
Component.tml:
${object.name}
click
Component.java:
onAction(String id) {
this.componentResources.triggerEvent("contextualize", new Object[] {id},
null);
}
Page.java:
onContextualizeFromComponent(String id) {
//just for contextulize a single component rendering out of the full loop
rendering.
this.row = this.findById(id);
}
This is how *Trigger* *component* is implemented. The original intention was
to provide a way to *trigger* events e.g. for rendering of JavaScript using
JavaScriptSupport service.
What is your use case? Maybe there is another way to do it?
On Tue, Jun 21, 2011 at 2:47 PM, Matias Blasi wrote:
Thanks Igor!
Is this a "*Trigger* *Component* API" limitation or there is any technical
limitation I am missing? If it is a API issue, it should be great to have a
*context* parameter into the *Trigger* *component*, do you?
Regards, Matías.
Nope, it's not possible. An event **triggered** by **Trigger**
**component**may only >> have MarkupWriter as **context** >>
On Tue, Jun 21, 2011 at 12:46 AM, Matias Blasi http://tapestry5.de
Re: Trigger component event context
Thanks Igor! Is this a "Trigger Component API" limitation or there is any technical limitation I am missing? If it is a API issue, it should be great to have a context parameter into the Trigger component, do you? Regards, Matías. >> Nope, it's not possible. An event *triggered* by *Trigger* *component*may >> only >> have MarkupWriter as *context* >> >> On Tue, Jun 21, 2011 at 12:46 AM, Matias Blasi wrote: Hi all! I am using the *trigger* *component* to fire an event. Is there any way to pass a *context* for that event? As far as I understand, the *trigger* * component* should have a '*context*' parameter, is that correct? Regards, Matias.
Trigger component event context
Hi all! I am using the trigger component to fire an event. Is there any way to pass a context for that event? As far as I understand, the trigger component should have a 'context' parameter, is that correct? Regards, Matias.
Tapestry5-JQuery Integration and tapestry-beanvalidator
Hi all I recently integrated my tapestry5 (5.2.5) application with the latest got5-jquery library (2.1.1) And I have the following error just entering to an empty page: Tapestry.Validator is undefined ---> Tapestry.Validator.notnull = function(field, message, spec) (tapestry-validator.js line 15) from tapestry-beanvalidator-5.2.5.jar Is there any incompatibility between tapestry-beanvalidator and tapestry-jquery? Or am I loosing something? Regards, Matias.
Tapestry5 + Tomcat5 + Apache2
Hi all!
I am gentting a problem with a the following scenario:
A tapestry5 application with a field with the @OnEvent mixin (chenillekit)
All this running on Tomcat5, behind Apache2.
I made a Proxy configuration in Apache2 in order to hide the server port:
http://localhost:8080/*>
Order deny,allow
Allow from all
ProxyPass / http://localhost:8080/
ProxyPassReverse/ http://localhost:8080/
ProxyRequests Off
ProxyPreserveHost On
All is working fine, with the exception of on request produced by the
http://hostname:port/app/context/page/component:internalevent...
This is the only request that contains the port number included, and seeing
the generated html I see:
new Ck.OnEvent('change', 'showInterests', false,
'http://hostname:port/app/context/page/component:internalevent',
'');
And the URL parameter is resolved by link.toAbsoluteURI().
The "OPTIONS" request is the only one that is not proxied by the Apache...
Do you know what am I missing?
All this work perfectly browsing the application through the Tomcat port,
the problem just occurs when I try to browse through apache proxy.
Saludos,
Matias.
Avoiding double form submission at server side
Hi!
I'am researching about the best way to avoid the double form submission at
the server side.
I was trying with a persistent flag
boolean onPrepareForSubmit() {
return !this.processing;
}
Object onSuccess() {
this.processing = true;
// do stuff
this.processing = false;
return this;
}
I was disapointed when I saw that the 'Succes' event is fired even when the
prepareForSubmit handler returned false.
Any suggestion?
Regards,
Matías.
Tapestry 5 and JOSSO
Hi guys, Has anyone used JOSSO as a single sign-on layer in front of a Tapestry App??? I am doing a research to integrate my Tapestry web application with Josso in order to share the login with other php application. Thank you in advance! Matías.
