Hi, Was just trying things out with validation. The more I abuse OpenEJB deploy(which is actually using validation the right way if I want to learn EJB :)) , the more I end up using validation. There are so many things which could be done in validation itself. For example, a little framework could be created to give a more feature rich help (interactive help etc..) . However, to reach that level , lot of work would need to be done on this feature. It would not be possible to keep the changes made to validation with the release requirement dates of OpenEJB. So, I was thinking that could validation be its own separate module where we could release its jars separately, which could simply be dropped in into an existing OpenEJB install? An OpenEJB release will have a default validation jar , lets say 1.0 (for openejb 3.0). But we could independently update the validation module and its releases and ask users to download and install the latest jar to have the latest and greatest in validation. This way validation releases become independent of OpenEJB releases and we can release validation modules much more frequently. Since I do not know much about the release process, so I am not sure if the above is doable or not, or even a direction worth looking into. It would be nice to know the pros and cons of the above approach, would be good learning for me.
Thanks! -- Karan Singh Malhi
