| Summary: | Static weaving - please improve processing speed and performance | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Igor Mukhin <iimuhin> |
| Component: | Eclipselink | Assignee: | Project Inbox <eclipselink.orm-inbox> |
| Status: | NEW --- | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | martin.grebac |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
|
Description
Igor Mukhin
I just found out that, it only happens if you weave to the same direcotry, where the original classes are. If you weave to somewhere else, it lasts just 5 seconds. I found out that the problem only occurs on Windows XP. My colleague has Windows 7 and the weaving lasts 5 seconds. So I coded the weaving for WinXP in this way: - rename /classes to /unweaved_<timestamp> - waave from /unweaved_<timestamp> to /weaved_<timestamp> - move from /weaved_<timestamp> to /classes Only that way it works fast on WinXP. The possible solution is may be to not use URLClassLoader in org.eclipse.persistence.tools.weaving.jpa.StaticWeaveProcessor in process().
The line is:
this.classLoader = new URLClassLoader(getURLs(), this.classLoader);
May be there is a classLoader that doesn't lock the files.
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink |