framework icon indicating copy to clipboard operation
framework copied to clipboard

OSGi documentation: Validation API

Open elmot opened this issue 7 years ago • 4 comments

Validation API seems to be non-compatible with OSGi, we need an example how to make it working.

elmot avatar May 19 '17 13:05 elmot

I could not make it working after about a day of experiments. The very last variant of testing project is here https://github.com/elmot/vaadin-karaf/tree/osgi-validation

elmot avatar Jun 07 '17 10:06 elmot

Some blog post related to the topic: https://floriansblog.wordpress.com/2015/03/18/osgi-vaadin-and-apache-bean-validation-jsr303/

elmot avatar Jul 27 '17 08:07 elmot

If it help using Florian blog approach, I developed three classes : BeanUtil, BeanValidator and BeanValidationBinder copying the original Vaadin code. And of course a bundle Activator for Hibernate javax.validation . It works perfect for OSGi in Liferay 7

rlhLegoSoft avatar Jul 27 '17 16:07 rlhLegoSoft

Hello there!

It looks like this issue hasn't progressed lately. There are so many issues that we just can't deal them all within a reasonable timeframe.

There are a couple of things you could help to get things rolling on this issue (this is an automated message, so expect that some of these are already in use):

  • Check if the issue is still valid for the latest version. There are dozens of duplicates in our issue tracker, so it is possible that the issue is already tackled. If it appears to be fixed, close the issue, otherwise report to the issue that it is still valid.
  • Provide more details how to reproduce the issue.
  • Explain why it is important to get this issue fixed and politely draw others attention to it e.g. via the forum or social media.
  • Add a reduced test case about the issue, so it is easier for somebody to start working on a solution.
  • Try fixing the issue yourself and create a pull request that contains the test case and/or a fix for it. Handling the pull requests is the top priority for the core team.
  • If the issue is clearly a bug, use the Warranty in your Vaadin subscription to raise its priority.

Thanks again for your contributions! Even though we haven't been able to get this issue fixed, we hope you to report your findings and enhancement ideas in the future too!

stale[bot] avatar Mar 19 '18 14:03 stale[bot]