Willem,
I've created a small test case using ServiceMix bundles for JSR-303 and for
hibernate validator.
It's a maven based project with a parent project containing two projects:
bundleOne and itest.
"bundleOne" contains a simple class (EntityOne) and a service with the
method "createEntityOne".
Willem,
With two bundles I mean that I have two bundles who utilize hibernate
validator. I run integration tests using Pax-Exam. My first integration test
deploys one bundle which uses hibernate validator to validate my entity
objects before persisting them - it works without a problem.
My second
What do you mean about two bundles?
Are they two camel context, or others.
ServiceMix's repacked bundle should supports to be used across the OSGi
platform, so I need more information about how do you use these validator.
Please create a small test case to show the whole story.
On 9/27/10 3:
I'm now using ServiceMix packaging of hibernate validator and the
javax.validation api. It works when I only have one bundle using the
validation api but when I have two bundles I get the following exception:
javax.validation.ValidationException: Unable to find a default provider
at
> javax.valid
Willem,
Sorry if I appear a bit ignorant but, as I wrote before, I haven't done any
OSGi wrapping before - I've always found what I needed. Often from
ServiceMix, sometimes from Geronimo (specs) and from SpringSource. I'm
trying to get the hang of this...
I don't think I need to try the validator
On 9/16/10 3:16 PM, Bengt Rodehav wrote:
Willem,
Not sure what you mean. I solved the problem by exporting the META-INF and
the META-INF.services "packages". That's all it took.
If you just have one bundle exports META-INF.services, that could be OK.
But if you have tens of bundles export that
Willem,
Not sure what you mean. I solved the problem by exporting the META-INF and
the META-INF.services "packages". That's all it took.
However, your version does not seem to work since no default provider can be
found
...Aha now I see what you wrote in your mail... You mean you need to hack
th
Oh, you need to make sure the bean validator API can find the
implementor jars in OSGi container.
ServiceMix did some work by introducing the service locator to search
the service from META-INF/services, and you may also need to hack the
validator API by using the locator to find the service fro
Willem,
I ended up using my own wrapped version mostly for learning reasons.
However, I had some problems with my wrapped version. I deployed it in the
container but in runtime I got error messages saying that no default
provider could be found. I then noticed that I hadn't exported the
META-INF/s
Thanks, I'll have a look,
/Bengt
2010/9/13 Willem Jiang
> On 9/13/10 3:58 AM, Bengt Rodehav wrote:
>
>> Thanks Cristian,
>>
>> I kind of suspected that Servicemix had bundled this. Actually I ended up
>> doing my own bundling anyway since I wanted to use the 4.1.0.Final
>> version.
>> Also want
On 9/13/10 3:58 AM, Bengt Rodehav wrote:
Thanks Cristian,
I kind of suspected that Servicemix had bundled this. Actually I ended up
doing my own bundling anyway since I wanted to use the 4.1.0.Final version.
Also wanted to see how easy/hard it was to accomplish.
/Bengt
I just created a patch[
Thanks Cristian,
I kind of suspected that Servicemix had bundled this. Actually I ended up
doing my own bundling anyway since I wanted to use the 4.1.0.Final version.
Also wanted to see how easy/hard it was to accomplish.
/Bengt
2010/9/11 Christian Müller
> Hello Bengt!
>
> Sorry, I overlooked
Hello Bengt!
Sorry, I overlooked it.
Apache Servicemix provides the OSGI-fied version for us. You can find the
released version 4.0.2 here [1]
[1]
http://repo2.maven.org/maven2/org/apache/servicemix/bundles/org.apache.servicemix.bundles.hibernate-validator/4.0.2.GA_2/
Cheers,
Christian
On Sat,
Thanks for your reply Christian.
However, the JAR you refer to isn't an OSGi bundle either. In fact I think
its the publicly released jar from JBoss which I had problems with. I tried
to use the OSGi wrapped version they use in Glassfish:
http://download.java.net/maven/2/org/glassfish/bean-valida
Hello Bengt,
we use the following on [1]. I think we could also update to 4.1.0. I opened
a JIRA for it [2].
Hope this helps,
Christian
[1]
http://repository.jboss.org/nexus/content/groups/public/org/hibernate/hibernate-validator/4.0.2.GA/hibernate-validator-4.0.2.GA.jar
[2] https://issues.apach
15 matches
Mail list logo
