Hi,

thanks for the fast reply. I'm now using 

  <scan>
     <exclude name="my.package.**"/>
   </scan>  

in my beans.xml, it's a lot faster. I'm also using 
openejb.deployments.classpath.include and openejb.deployments.classpath.exclude 
and I try to limit the packages by using a scan.xml (in META-INF) with only 
specific packages.

Older Hibernate Validator Versions (5.0.0) did not help. I still see warnings 
about some packages like java.util.HashMap.java.util.HashMap$TreeNode<K, V>, 
but maybe it's because those are used in beans? Is there any other trick to 
limit the scanning I might try? I could not find a nice documentation about how 
to configure such things. OpenEjb still mentions " 
openejb.deployments.package.exclude".

Regards Volker

-----Original Message-----
From: Romain Manni-Bucau [mailto:[email protected]] 
Sent: Mittwoch, 24. Februar 2016 18:26
To: [email protected]
Subject: Re: Hibernate Validator class scanning in OpenEjb 7.0.0-M1

Hi

if you can share some jstack dump in the "slow" period it could help to tackle 
that. Also maybe try previous releases - know they fixed some inheritance bugs 
so maybe they added some overhead by side effect. Bean validation scanning 
should be limited to CDI during startup so same tricks as for CDI should work.



Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog 
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | 
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber 
<http://www.tomitribe.com>

2016-02-24 18:11 GMT+01:00 Gropp Volker <[email protected]>:

> Hi,
>
> we are upgrading our openejb-based unit-tests of a fairly large 
> JEE-app to OpenEjb 7.0.0-M1 and I noticed a very slow startup while 
> scanning all classes for Bean Validation with Hibernate Validator 5 
> 5.2.2.Final. Is there any way to limit classes/packages which are 
> scanned by Hibernate Validator or to disable it completely (in our 
> tests)? Maybe this is not a problem solely in 7.0.0-M1, but I noticed 
> it because of lot of warnings/errors while starting up the container.
>
> Regards,
>
> Volker Gropp
>

Reply via email to