[
https://hibernate.onjira.com/browse/HV-570?page=com.atlassian.jira.plugin...
]
Gunnar Morling commented on HV-570:
-----------------------------------
Maybe we could provide a solution based on either OSGi [Declarative
Services|http://eclipsesource.com/blogs/2009/05/12/osgi-declarative-servi...] or
[Blueprint
Services|http://aries.apache.org/documentation/tutorials/blueprinthellowo...].
AFAIK both are standardized approaches for exporting (and consuming) OSGi services in a
declarative manner (I'm not sure though, which one is preferrable), and we would avoid
the dependency to Spring that way.
I think exposing the default {{Validator}} and {{ValidatorFactory}} as OSGi services that
way shouldn't be difficult. The other question is how to handle resources provided by
the user on the class path (message bundles, but also XML based constraint mapping files).
I'm not sure what the best/recommended way for that would be.
If we decide to provide something independently from BVAL-251 we should mark it as
experimental as recently discussed, as I guess BVAL-251 might change things later on.
Provide an hibernate validator OSGI service exporter
----------------------------------------------------
Key: HV-570
URL:
https://hibernate.onjira.com/browse/HV-570
Project: Hibernate Validator
Issue Type: New Feature
Components: engine
Affects Versions: 4.3.0.Alpha1
Reporter: Charlie Mordant
Priority: Minor
Hi,
I've created a hibernate validator OSGI service exporter.
Feel free to use it, publish it on central (it will be cool), modify...
You can find it in my github:
https://github.com/Tcharl/org.hibernate.validation.osgi.service/
Regards,
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira