On 19 June 2015 at 16:13, Scott Marlow wrote:
> I'm not exactly sure how infinispan-commons finds the infinispan-core
> classloader with ORM 4.3, but clearly that is not working now with ORM 5.0.
>
> In WildFly, the infinispan-commons classloader doesn't have access to the
> infinispan-core classl
I'm not exactly sure how infinispan-commons finds the infinispan-core
classloader with ORM 4.3, but clearly that is not working now with ORM 5.0.
In WildFly, the infinispan-commons classloader doesn't have access to
the infinispan-core classloader.
This seems somewhat related to the CNFE on
or
Complete exception call stack is here http://pastebin.com/564BNWSF
On 06/19/2015 09:43 AM, Scott Marlow wrote:
> I'll see if I can capture a more complete exception call stack for the CNFE.
>
> On 06/19/2015 09:32 AM, Steve Ebersole wrote:
>> If Infinispan is not available to core/hem than I am no
I'll see if I can capture a more complete exception call stack for the CNFE.
On 06/19/2015 09:32 AM, Steve Ebersole wrote:
> If Infinispan is not available to core/hem than I am not sure how ORM
> not being able to find Infinispan classes is a problem with class
> loading in ORM. Seems to me this
If Infinispan is not available to core/hem than I am not sure how ORM not
being able to find Infinispan classes is a problem with class loading in
ORM. Seems to me this is simply a problem in the ClassLoader made
available to ORM.
On Fri, Jun 19, 2015 at 7:46 AM Scott Marlow wrote:
> To be a li
To be a little more specific, WildFly is now respecting the Hibernate
Search desire for Infinispan classes to *not* be available to Hibernate
core/entitymanager. This is important so that Hibernate Search can have
the flexibility to use a different version of Infinispan than WildFly is
using w
