If you were able to share the code then what I would commit to is taking
the best of what your code offers, the nested support that Simon's code
offers (we have lots of embedded objects and I'm not sure whether or not
your code drills down into them...)
I haven't looked at the other code
Mike McNally wrote:
If you were able to share the code then what I would commit to is
taking the best of what your code offers, the nested support that
Simon's code offers (we have lots of embedded objects and I'm not
sure whether or not your code drills down into them...)
What is the best way to separate variabls in a larger form the action? In
Struts 1 you have a separate action (for the logic) and form (to use for
fields). In Stripes have all this in action. Hope I explained well.
I thought to create a class NameModel with a variabls for a form and extend it
Hi,
what about creating a Pojo holding all the form variables und referencing it
in the actionBean and doing validation using @ValidateNestedProperties?
Regards,
Richard
On Fri, Sep 10, 2010 at 12:52 PM, andres ispanand...@yahoo.es wrote:
What is the best way to separate variabls in a larger
On 10-09-2010 at 10:52, andres wrote:
What is the best way to separate variabls in a larger form the action? In
Struts 1 you have a separate action (for the logic) and form (to use for
fields). In Stripes have all this in action. Hope I explained well.
I thought to create a class NameModel
Actually I feel that the basic Stripes mechanisms for annotating validation
information to be completely inadequate for an application of any serious
complexity. Inevitably, persisted objects will be manipulated by many
actions, and the consequent need to repeat the validation rules over and
over
Could you explain more detail how it work, and how to implement?
Thank you very much.
--- El vie, 10/9/10, Oscar Westra van Holthe - Kind os...@westravanholthe.nl
escribió:
De: Oscar Westra van Holthe - Kind os...@westravanholthe.nl
Asunto: Re: [Stripes-users] The best way to separate
On 10-09-2010 at 12:03, andres wrote:
Could you explain more detail how [binding into the domain model, using
Stripersist] work, and how to implement?
Stripersist is hosted at the StripesStuff project, and contains an example
as well:
StipesStuff:
Thanks I'll see.
Gracias :)
--- El vie, 10/9/10, Oscar Westra van Holthe - Kind os...@westravanholthe.nl
escribió:
De: Oscar Westra van Holthe - Kind os...@westravanholthe.nl
Asunto: Re: [Stripes-users] The best way to separate variabls in a larger form
from the action.
Para: Stripes Users
Mike,
I agree about pretty much everything you said and am afraid that I will
need to develop this as well as my app has lots of model objects.
Would you be willing to share the code you developed to extend the
validation?
Also it might be great to create a JIRA ticket and attach the code for
I am personally willing to share the code, but I'd have to clear it with my
employer. What I did was not super-complicated, and I can summarize it here:
*) I created my own ValidationMetadataProvider class, starting (of course)
with the default one.
*) I took the approach of mimicking the way
Mike,
Thanks for the summary. Much appreciated. I understand your needed to
clear a request like this with your employer.
I guess my point was that this is one area that Stripes could use some
improvement and although it isn't complicated everyone needs to build
their own solution /
12 matches
Mail list logo
