Announcement Announcement Module

Spring Modules forum decommissioned in favor of Spring Extensions

As the Spring Modules project has been replaced by the Spring Extensions ( project, this forum has been decommissioned in favour of Spring Extensions one at:

Please see the Spring Extensions home page for a complete list of current projects in Java, .NET and ActionScript. You can also propose one if you want.

Costin Leau
SpringSource - Spring Training, Consulting, and Support - "From the Source"
See more
See less
validation-valang production-ready? Page Title Module
Move Remove Collapse
Conversation Detail Module
  • Filter
  • Time
  • Show
Clear All
new posts

  • validation-valang production-ready?


    We're trying to choose between the validation options given in the validation module. Obviously, valang looks nicer, but what is your experience: can you rely on this in production?
    Or is it safer to go with good old commons-validator? Or any other option?

    (We prefer declarative validation, and we need both rocksolid serverside and clientside validation.)

  • #2
    validation-valang production-ready?

    I'm also interested in finding out whether people have had any success with putting Valang validators into production.
    Also, I'm curious to know whether there are any plans for moving the validation code in spring modules into the core spring distribution? Is there any timeline for this, or what is the process a component has to go through to go from spring modules into the core spring distribution.


    • #3
      I'd ALSO like to know if there is production-level experience.

      I am using it in a system that is intended to go into production sometime around June but I'd rather know NOW, if things are going to fall over!




      • #4
        Since I popped the original question, I got a little more experienced with it and it seems that valang is pretty nice when validating in the serverside, but the clientside stuffs are far from being bug-free.
        Anyway, it's just a "switch" to turn clientside validation on or off, so if it's an immediate requirement in your project, you can just disable it for a while...


        • #5
          I agree that the server-side functionality is pretty good.

          Haven't tested the client-side stuff (not really a requirement for me so far).

          My questions/worries are related to load/memory leaks, etc....all those little niggles that only arise AFTER the functionality of the system has been created.




          • #6

            1 ). In my company we are using Valang Validation throughout our application.
            It's all ready in production, and we never fill performance issues because of Valang code.

            2). I fill Valang is very cool stuffs to handle Server side and Client side validation.

            3). The validation which we registry for server site those same validation we can apply on client site without weighting single script.

            That's why I thing Valng is cool Stuffs to apply in the project.



            • #7
              VALANG works well

              I agree...

              I have just completed rolling out into production a system that uses VALANG and I saw no memory leaks, performance 'gotchas' etc. when I did performance testing.

              This makes me feel much more relaxed.

              The language is a little obscure sometimes but on the whole..."it just works."

              I wrote a bit more (including load info.) at: