On Thu, 26 May 2016 05:51:11 -0300, Jaroslav Ciml
wrote:
Hi, Thiago!
Hi!
Thanks for your reply.
Is there a way to validate the t:formdata parameter please? Can I detect
whether this parameter contains some meaningful value or not?
I'm sorry, I don't know.
--
Thiago H. de Paula Figue
Hi, Thiago!
Thanks for your reply.
Is there a way to validate the t:formdata parameter please? Can I detect
whether this parameter contains some meaningful value or not?
Best wishes
Jarda
> On May25, 2016, at 16:50, Thiago H de Paula Figueiredo
> wrote:
>
> On Wed, 25 May 2016 08:48:17 -03
On Wed, 25 May 2016 08:48:17 -0300, Jaroslav Ciml
wrote:
Hi Barry,
Hello, Jaroslav!
This pattern (form data groupped in DTO, simple initialization for POST
requests in prepare for submit handler, more complex initialization for
GET requests in prepare for render handler) is used about
Hi,
there are just two assignments to formData:
@OnEvent(value = EventConstants.PREPARE_FOR_RENDER, component = "searchForm")
void prepareForRender()
{
formData = new ServiceSearchFormData();
// more initialization here, i.e. calling setters like
formData.setCity(DEFAULT_CITY_NAME);
}
.
Hi,
@Barry, yes, your solution should fix null pointer exception, but probably
it would break the application. A better way:
public SearchFormData getFormData() {
if (formData == null) {
formData = new SearchFormData();
}
return formData;
}
However, it is still interesting that fo
Hi Barry,
thanks for nice hint.
I cannot fix it so simply just by adding this one-line method but it shows the
way to go anyway.
This pattern (form data groupped in DTO, simple initialization for POST
requests in prepare for submit handler, more complex initialization for GET
requests in prepa
It's difficult to say why it might be null but changing the code to
public SearchFormData getFormData() {
return new SearchFormData();
}
should fix it
On Monday, May 23, 2016, Jaroslav Ciml wrote:
> Hi,
>
> I am getting a strange exception during submit of a Tapestry form that I
> cannot ex
Hi,
I am getting a strange exception during submit of a Tapestry form that I cannot
explain. It happens just rarely (but regularily) in the production environment.
I cannot even reproduce the exception.
I have a form in tml file of a Tapestry component.
...
..
And her
