Thanks Guys for the alternate suggestions. I'll keep them in mind when I run
into this again. For now the app is just to small to make it worth it.
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Passing-form-component-into-service-tp5715894p5715910.html
Sent from the Ta
The Form component implements FormValidationControl. If this interface
provides what you need, there is no need for a domain object.
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Passing-form-component-into-service-tp5715894p5715909.html
Sent from the Tapestry - User ma
On Thu, 30 Aug 2012 10:33:45 -0300, George Christman
wrote:
Thanks Lance, management asked me to put all my validation's in a
service, however I figured there would be an issue passing the tapestry
form
component into the service. I think the domain object would be the best
option althoug
Thanks Lance, management asked me to put all my validation's in a service,
however I figured there would be an issue passing the tapestry form
component into the service. I think the domain object would be the best
option although I don't see any cost benefit in this extra layer of
abstraction.
No, this is not allowed and is generally considered bad practice. You will
need to pass a class (or interface) that is not in the
components/pages/mixins/base packages.
There are two main options:
1. Copy the data into a domain object and pass the domain object
2. Have your component implement an
