That's good news. Thanks for letting me know.
Geoff
On 18/04/2012, at 2:31 AM, David Canteros wrote:
> I have done a quick test and it works perfectly!
> Thanks Geoff!
>
>
> --
> David Germán Canteros
>
>
> 2012/4/12 Geoff Calle
I have done a quick test and it works perfectly!
Thanks Geoff!
--
David Germán Canteros
2012/4/12 Geoff Callender
> Hi all,
>
> I've taken on board all the suggestions and observations here about
> AjaxFormLoop problems and fixes
Hi all,
I've taken on board all the suggestions and observations here about
AjaxFormLoop problems and fixes, and done a complete rewrite of the JumpStart
examples. I've put a beta on the demo site. Is every corner case handled now? I
sure hope so. See if you can find a hole in it.
http
Hi David, after some testing I wanted to provide you with some updates based
on some scenarios I ran into.
You'll notice in the !request.isHXR condition, I'm checking for a null
lineItem id. This prevents duplicate objects from being added to the
collection.
@SuppressWarnings("unchecked")
Hi George, finally it worked! Thank you for the help!
Before I was using the ajaxformloop like as Geoff example, with the tree
arrays XXXtoCreate, XXXToChange and XXXtoDelete and the same encoder. That
made me think, probably the problem was caused by Geoff's example and not
by the loop compone
Hi David, I'm using the pr object like so
It seems to be working perfectly for me. I'm only using the prPersist object
to hold a temporary copy of the current pr at validation. When the page
reloads with the validation errors, I'm using the prPersist to extract and
populate my current lineItem o
Hi George,
i've done a quick test and it doesnt work on my code, but i will do a full
test by tomorrow. Only one question: which object are you using in the
ajaxformloop (in the tml code)? pr or prPersist?
Regards and thanks!
--
Dav
David, I have a working work around, I'm sure it's not the best, but does
work. See code below.
@Persist
private PurchaseRequest prPersist;
private PurchaseRequest pr;
private final String NEW_OBJ = "new";
void onActivate() {
if(prPersist != null) {
for(
As a temporary fix, I was looking at doing something like this.
private PurcahaseRequest pr;
@Persist
private PurchaseRequest prPersist;
Class onActivate(PurchaseRequest pr) {
this.pr = pr;
}
void onActivate() {
if (this.pr == null) {
this.pr = new PurchaseRequest();
Hi David, I created a jira issue related to this bug.
https://issues.apache.org/jira/browse/TAP5-1875
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Server-Side-Validation-with-ajax-form-loop-tp5120576p5565297.html
Sent from the Tapestry - User mailing list archive at Na
Sure, not a problem. I'll file a bug in the morning.
On Thu, Mar 8, 2012 at 2:58 PM, David Canteros [via Tapestry] <
ml-node+s1045711n5548672...@n5.nabble.com> wrote:
> Could you please do it? My english is not good (my natural language is
> spanish) and you already have the code with the issue
Could you please do it? My english is not good (my natural language is
spanish) and you already have the code with the issue.
Tell me if you can't.
Thanks!
David
--
David Germán Canteros
2012/3/6 George Christman
> Sounds go
Sounds good to me. Do you want to file the jira issue, or would you like me
to?
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Server-Side-Validation-with-ajax-form-loop-tp5120576p5540927.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
-
Hi George, I still have the problem. I don't understand the underlying code
of the frameworks so i can't find the code that is working wrong, so the
clientside validation is the only way to "solve" it.
We would file a JIRA to get help (i dont saw any similar issue registered
), what do you think?
David have you figured out how to get around this issue? I'm using clientside
validation to over come it for the short term, but it would be nice to get
server side working properly.
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Server-Side-Validation-with-ajax-form-loop-
I have the same problem with AjaxFormLoop, the values typed on new added
row are lost when server side validations record any error on the form.
--
David Germán Canteros
2012/2/2 George Christman
> Hi Geoff, just curious if you
Hi Geoff, just curious if you ever had a chance to look at this issue again?
Thanks
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Server-Side-Validation-with-ajax-form-loop-tp5120576p5451139.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
-
Hi Geoff, Implemented your suggestion with the same set of results. My pr
object seems to be returned null resulting in the loss of data.
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Server-Side-Validation-with-ajax-form-loop-tp5120576p5125845.html
Sent from the Tapestry
Hi George,
I've recreated the problem, but I can't spend more time on it until next week.
In the meantime, this may solve all or part of it:
- Add a zone around the form.
- Add the zone parameter to the form.
- Modify the OnValidateFromYourForm method to return an Object.
- Change the final retu
19 matches
Mail list logo
