Franck, My initial reaction after reading the documentation is that this would be a great addition to the Flex framework.
If you don't mind, maybe you could address these concerns I have? 1. Can we make sure that this approach does not tie Flex to specific server side solution (Java in this case)? 2. Do you think this could go in the SDK itself or would it go into an ancilliary library, but still part of Flex. Can you suggest a package structure? 3. What happens to JSR 303 if/when you contribute the AS3 portion of the implementation? Obviously we can't guarantee that Apache Flex will follow that standard always. 4. What sort of performance implications can we expect with this approach? Also, would it help if we make changes to the Flex compiler for this to perform better? Thanks a lot for offering to contribute to Apache Flex! Regards, Om On Sep 24, 2012 7:40 AM, "Franck Wolff" <franck.wo...@graniteds.org> wrote: > Hi Carlos, > > 2012/9/24 Carlos Rovira <carlos.rov...@codeoscopic.com> > > > Hi Franck, > > > > I think it would be great. I was in the way to make some > > implementation some time ago since flex view validation is problematic > > when you try to use MVC but I never get to far. In flex the problem is > > that validation and view controls are dependent and it would be great > > to have bean validation in order to validate data and have real > > separation from the view. This brings the problem on how to show the > > errors in controls to let the user now about a failed validation. I > > suppose that is solved in GDS. > > > > Yes, we have a specific component called FormValidator which displays > errors in real-time, based on the user input. > > > > So I think bean validation would be a great improvement in flex SDK > > and annotations would make it more usable. > > > > For BigDecimal and others classes could be great as well, but I don't > > have clear how could be donate to sdk...maybe it could go to an > > extension package or something like that and get some externalization > > base implementation... > > > > An extension package is of course an option. > > Thanks for your quick feedback, > Franck. > > 2012/9/24 Franck Wolff <franck.wo...@graniteds.org>: > > > Hi All, > > > > > > We, at Granite Data Services <http://www.graniteds.org>, are > considering > > > contributing part of our Flex client code to this Apache project. Our > > first > > > thought is to contribute our Bean Validation (aka JSR-303) > implementation > > > in ActionScript3: this framework gives an easy and powerful way to > > validate > > > ActionScript beans based on constraint annotations (see documentation > > > here< > > > http://www.graniteds.org/public/docs/2.3.2/docs/reference/en-US/html/graniteds.validation.html > > >). > > > This framework can be used standalone, with no specific dependency to > > rest > > > of the GraniteDS platform, but is usually best used together with Gas3 > > (our > > > code generation tool) which replicates Java entities annotated with > > > constraint annotations in ActionScript3, with the same constraints. The > > > validation process can then be executed on the Flex, replicating what > > Java > > > is doing on its part, and can display error messages on the fly, while > > the > > > user is filling out a Flex form. > > > > > > What do you think about such contribution? We could also contribute > later > > > our Flex implementation of the BigDecimal, BigInteger and Long classes > > (see > > > documentation here< > > > http://www.graniteds.org/public/docs/2.3.2/docs/reference/en-US/html/graniteds.bignumbers.html > > >), > > > but this implementation has a dependency on some externalization > features > > > specific to GraniteDS. > > > > > > Regards, > > > -- > > > Franck Wolff / William Draï > > > Granite Data Services > > > > > > > > -- > > Carlos Rovira > > Director de Tecnología > > M: +34 607 22 60 05 > > F: +34 912 35 57 77 > > CODEOSCOPIC S.A. > > Avd. del General Perón, 32 > > Planta 10, Puertas P-Q > > 28020 Madrid > > > > > > -- > Franck Wolff > Granite Data Services Inc. > CEO & Founder >
