On 3/22/19 7:49 AM, Guillaume Smet wrote:
Do we have any idea of what this class is supposed to be:
This is a unit test class that is not an entity class, but instead it
happens to be an EJB stateless session bean. In the exception call
stack , the class that ByteBuddy complains about is a WildFly class
(not even a test class), you can see that in the exception message
Scott, any idea?
I was not really aware that classes like
SerializationProxyHackImplementation  , would also be handled by
but I guess that makes sense, as application classloaders versus
application module classloaders, are not distinguished internally in WF.
I'm also not sure of how Javassist handles ignoring the
SerializationProxyHackImplementation  class but Javassist does work
fine (as long as you work around the other issue, which is that
Javassist can only be selected via system property setting but not
persistence.xml setting, also mentioned in WFLY-11891 ).
Because it doesn't ring a bell on my side.
I suspect it's a class we shouldn't access or touch. And we should probably
add a condition somewhere to avoid doing so.
If you can give me the Hibernate call which initiates the error, that would
 shows the exception call stack (look for
And stupid question: we did not have any enhancement test in WildFly before
No, sadly, this is the first time we updated the WildFly unit tests to
try Javassist + ByteBuddy enhancement. Its a very light test with
little verification, basically we just modified some existing tests to
And one test was also modified to specify
hibernate.bytecode.provider=javassist, which is ignored (only the system
property works, via standalone.sh
-Dhibernate.bytecode.provider=javassist). The problem is also mentioned
in WFLY-11891 .
In WF, we also have a mock persistence provider test that ensures that
persistence providers can enhance classes as per the JPA container contract.
 java.lang.IllegalStateException: Cannot resolve type description for