Since I cannot find a way to "inject/declare" annotations to fields, my original plan of dynamically create an "ApplicationConfigurationBean" to be validate is not feasible.
Maybe I should work in the other way around ? Define the "ApplicationConfigurationBean" as/via a service and contribute to it; and eventually use that object to configure the CLI parsing libraries, meaning that I need to be able to generate validation messages, "help/usage message", as well as decide on option formats and input arguments. -- Alessio On Sep 25, 2013, at 7:24 PM, Thiago H de Paula Figueiredo wrote: > On Wed, 25 Sep 2013 12:19:52 -0300, Alessio Gambi <alessioga...@gmail.com> > wrote: > >> It would be great also if I can add messages to the annotations as one >> expect. > > Bean Validations has its own way of dealing with validation messages and > their internationalization. See > http://docs.oracle.com/javaee/6/tutorial/doc/gkahi.html. In addition, all > validation annotations have a message attribute you can use to set the error > messages in a static way. > > -- > Thiago H. de Paula Figueiredo > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
