Community
Participate
Working Groups
Byte code weaving is currently defaulted to false. To enable weaving (currently only available on Equinox), a persistence unit must set weaving=true, the weaving fragment must be co-located in the same folder as org.eclipse.osgi, and the weaving fragment must be identified as a framework extension. If the weaving fragment is co-located with org.eclipse.osgi and is identified as a framework extension then weaving should be enabled by default--essentially emulate the Java SE semantics.
Does this bug entry still reflect the current state? How could a test possibly find out if weaving is enabled? Thanks, -Juergen
Do people still think this is worth doing? I don't see how we could do it and preserve backward compatibility since an application that previously worked without weaving will suddenly start to be woven once upgraded to a more recent version of Gemini JPA (if they did not explicitly specify a false value in persistence.xml). Thoughts?
This would not be hard to do but I don't think there is a way to do it and preserve backward compatibility.
