Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 329703

Summary:	Default to weaving enabled when possible
Product:	[RT] Gemini.JPA	Reporter:	Shaun Smith <shaun.smith>
Component:	Core	Assignee:	Shaun Smith <shaun.smith>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3	CC:	eduard.bartsch, juergen.kissner, michael.keith
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:

Description Shaun Smith

2010-11-08 15:13:59 EST

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.

Comment 1 Juergen Kissner

2011-07-19 12:11:35 EDT

Does this bug entry still reflect the current state? How could a test possibly find out if weaving is enabled?

Thanks,
-Juergen

Comment 2 Michael Keith

2012-05-28 16:22:13 EDT

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?

Comment 3 Michael Keith

2012-09-13 17:07:27 EDT

This would not be hard to do but I don't think there is a way to do it and preserve backward compatibility.