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 fro
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
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
bstraction.
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Passing-form-component-into-service-tp5715894p5715907.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
-
To unsubscribe, e-m
interface and pass by interface instead
of the concrete component type.
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Passing-form-component-into-service-tp5715894p5715896.html
Sent from the Tapestry - User mailing list archive at Nabble.com
ontext:
http://tapestry.1045711.n5.nabble.com/Passing-form-component-into-service-tp5715894.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For a
