[ https://hibernate.onjira.com/browse/HV-570?page=com.atlassian.jira.plugin... ] Hardy Ferentschik updated HV-570: --------------------------------- Description: 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, was: 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 Regards, Affects Version/s: 4.3.0.Alpha1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://hibernate.onjira.com/browse/HV-570?page=com.atlassian.jira.plugin... ] Kevin Pollet commented on HV-570: --------------------------------- Hi, I understand what you're doing! My thinking is that Spring is not necessary to expose the ValidatorFactory as an OSGI service. An other remark is that the user has no proper way to congigure the ValidatorFactory, am I right? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://hibernate.onjira.com/browse/HV-570?page=com.atlassian.jira.plugin... ] Hardy Ferentschik commented on HV-570: -------------------------------------- {quote} You're right, Spring is not mandatory, I just used it for convenience (is it totally banned from JBoss developments?). {quote} This has nothing with a ban to do ;-) However, as you say yourself Spring is needed for OSGi. If we want to address issues related to OSGi we should keep the solutions as generic as possible so that they fit many different usecases. I guess what I am trying to understand is how this relates to BVAL-251 and HV-523. What exactly does it mean that I publish the validator factory as an OSGi service and how does this relate to general Bean Validation bootstrapping. {quote} This script is easily upgradable, you just have to put the OsgiValidatorFactory in a fragment or publish as an OSGI service (you can name it SimpleOsgiValidatorFactory). {quote} Well, maybe you could provide a patch, because I am still not quite clear on this :-) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://hibernate.onjira.com/browse/HV-570?page=com.atlassian.jira.plugin... ] Hardy Ferentschik commented on HV-570: -------------------------------------- Thanks Charlie, that puts your stuff and request more into perspective. At least in my mind. If there were just someone out there which could tell me what you OSGi people want ;-) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ 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. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://hibernate.onjira.com/browse/HV-570?page=com.atlassian.jira.plugin... ] Hardy Ferentschik edited comment on HV-570 at 4/12/12 4:51 AM: --------------------------------------------------------------- {quote} Maybe we could provide a solution based on either OSGi Declarative Services or Blueprint Services. 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. {quote} Sounds reasonable. I like the idea of a standardized approach :-) {quote} 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. {quote} What's about custom message interpolator, traversable resolver, etc. Basically everything you can configure in _validation.xml_? Is this service (aka these OSGi xml files) really something which should be part of the Hibernate Validator jar file or is this not something a user has to create according to his needs? Does it make sense to just export a default factory? Is there a need for different validator factories for different bundles? Does OSGi services allow to qualify a service? I am thinking about multiple BV implementation all exporting the _ValidatorFactory_ - how would I select between them? {quote} If we decide to provide something independently from BVAL-251 we should mark it as experimental {quote} +1 In fact, before doing anything I would like to see in which direction BVAL-251 goes. was (Author: hardy.ferentschik): {quote} Maybe we could provide a solution based on either OSGi Declarative Services or Blueprint Services. 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. {quote} Sounds reasonable. I like the idea of a standardized approach :-) {quote} 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. {quote} What's about custom message interpolator, trversable resolver, etc. Basically everything you can configure in _validation.xml_? Is this service (aka these OSGi xml files) really something which should be part of the Hibernate Validator jar file or is this not something a user has to create according to his needs? Does it make sense to just export a default factory? {quote} If we decide to provide something independently from BVAL-251 we should mark it as experimental {quote} +1 In fact, before doing anything I would like to see in which direction BVAL-251 goes. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://hibernate.onjira.com/browse/HV-570?page=com.atlassian.jira.plugin... ] Hardy Ferentschik updated HV-570: --------------------------------- Fix Version/s: 5.x -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira