Hi Emmanuel,

These should normally respect the order of the beans that you used to
create the cart items. Can you use that? Another alternative is to
add a hidden form tag with the id of the bean.

Yes, I figured that the order is maintained and yes that works; i
guess what I am kinda wondering is how I to get validation/error
marking working with my current template.

What I would do (to prevent clashes with other bean class), is to give that bean a specific prefix for the validation. However, even if you don't do that, you should be able to just use FormBuilder.removeForm or ValidationBuilder.removeErrorMarkings/ ValidationBuilder.removeValidationErrors for that template and re-do the validation. After that, just append the block of your item and the values for the validation errors and marking will be 'fixed'.

Actually, what you can do if you really want to isolate and componentize the handling of these beans, you can use embedded elements and provide it with a data object during processEmbeddedElement (which will be each bean). This is only supported in 1.5 though.

that should give you what you're looking for

yup; perfect! thx

Well ... nested value tags would be perfeect :-p

Added support for nested value tags is planned but I sadly haven't
got enough time to get everything done. RIFE could really benefit
from some new framework developers ;-)


true.. it's been crazy busy around here (which is why even petstore is
still not up); but plans to add/improve bits of the framework have
alywas been right up there :)

Ok, kewl :-)

Best regards,

Geert

--
Geert Bevin
Uwyn "Use what you need" - http://uwyn.com
RIFE Java application framework - http://rifers.org
Music and words - http://gbevin.com


_______________________________________________
Rife-users mailing list
[email protected]
http://lists.uwyn.com/mailman/listinfo/rife-users

Reply via email to