-
Type:
Bug
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution: Done
-
Affects Version/s: EAP 5.0.0.CR4 (FCS and BETA2), EAP 5.0.0.CR5, EAP 5.0.0
-
Fix Version/s: TBD EAP 5
-
Component/s: EJB
-
Labels:None
-
Affects:Release Notes, Compatibility/Configuration
-
Workaround:Workaround Exists
-
Workaround Description:
-
Affects Testing:Regression
-
Release Notes Text:
-
Release Notes Docs Status:Not Required
I have verified that cglib proxies can be returned to and processed by a webapp client used in EAP 4.3 using JPA by setting: hibernate.bytecode.provider=cglib in jboss-as/server/production/deploy/ejb3.deployer/META-INF/persistence.properties.
For EAP 5, is the correct place to configure cglib in jboss-as/server/default/deployers/ejb3.deployer/META-INF/jpa-deployers-jboss-beans.xml?
If so, it is not working properly. Javassist was used even after configuring cglib in that file and adding asm.jar and cglib.jar to jboss-as/common/lib.
After adding -Dhibernate.bytecode.provider=cglib to $JAVA_OPTS in jboss-as/bin/run.sh or jboss-as/bin/run.conf, cglib was used properly.
If we are using the correct config file, then this is a bug.
Will adding -Dhibernate.bytecode.provider=cglib to $JAVA_OPTS in jboss-as/bin/run.conf cause cglib to be used for all server types?
Would this be an acceptable workaround?
- is related to
-
JBPAPP-2915 CLONE -Setting hibernate.bytecode.provider system property in persistence.properties is unreliable
-
- Closed
-