Community
Participate
Working Groups
Build Identifier: 20100218-1602 I would like to request supporting static weaving by the Dali Plug-In in the build process. I think this would fundamentally ease static weaving, since current methods (e.g., ant task) are quite cumbersome to install - especially in a distributed development environment (or when using a development configuration as described in the forum post referred below). A similar feature exists for example in the Google Eclipse plug-in for App Engine, where the DataNucleus Enhancer is automatically run after each build. This RFE refers to the following discussion in the EL forum http://www.eclipse.org/forums/index.php?t=msg&th=168938&start=0& Reproducible: Always
I'm interested in gauging the level of interest for this feature. Please comment/vote if you are interested in seeing this feature in Dali.
It would make developing in Eclipse a bit easier, since you don't need to specify the javaagent in every run config. When I build the BM jar for distribution I have it statically weaved anyhow.
I would appreciate this feature since we use SAP NetWeaver 7.20 which unforunately does not support dynamic weaving. The ant task sometimes is errorprone because of locked files.
I am also curious if we could simplify the use of the dynamic weaving agent in Java SE where JUnit tests are typically run. If the target environment for the deployed app is Java EE (EJB 3.,0) where dynamic weaving happens by default then the real issue is simplifying the dynamic weaving outside of the container.
Will look at this for the 3.0 (Indigo) release.
Targeting to Juno release.
Implemented in 3.2 M5 Automatic Static Weaving can be added and configured in a JPA project via the project's properties page in JPA > EclipseLink. For additional enhancement open a new bug as needed.
Release in 3.2 M5