My guess would be that the service registry is not being released. Let me
look...
Brett, that makes me wonder if we ever properly deal with releasing the
OSGi classloader stuff...
http://lists.jboss.org/pipermail/wildfly-dev/2013-July/000466.html
contains the details about deployment level class
On Jul 16, 2013, at 12:33 AM, Steve Ebersole wrote:
> My gut reaction is that this is probably ok either way according to spec.
> Though I think it should certainly be an error if the xml is "complete" . Is
> there a hardship in supporting the existing "ignore it" behavior?
>
>
it is comp
The new FieldSettingsDescriptor [1] has a couple of methods meant for
Numeric fields:
/**
* @return the numeric precision step in case this field is indexed as
a numeric value. If the field is not numeric
* {@code null} is returned.
*/
Integer precisionStep();
/**
* @return {@code
http://lists.jboss.org/pipermail/wildfly-dev/2013-July/000466.html
contains the details about deployment level classes are leaking (CDI
beanmanager passed into deployment, bean validation factory, others...).
In WildFly 8, We do have a
META-INF/services/org.hibernate.engine.transaction.jta.plat
My gut reaction is that this is probably ok either way according to spec.
Though I think it should certainly be an error if the xml is "complete" .
Is there a hardship in supporting the existing "ignore it" behavior?
On Jul 15, 2013 1:39 AM, "Strong Liu" wrote:
>
> hibernate-core/src/test/resourc
