/** * Specify the Spring LoadTimeWeaver to use for class instrumentation according * to the JPA class transformer contract. * <p>It is a not required to specify a LoadTimeWeaver: Most providers will be * able to provide a subset of their functionality without class instrumentation * as well, or operate with their VM agent specified on JVM startup. * <p>In terms of Spring-provided weaving options, the most important ones are * InstrumentationLoadTimeWeaver, which requires a Spring-specific (but very general) * VM agent specified on JVM startup, and ReflectiveLoadTimeWeaver, which interacts * with an underlying ClassLoader based on specific extended methods being available * on it. * <p><b>NOTE:</b> As of Spring 2.5, the context's default LoadTimeWeaver (defined * as bean with name "loadTimeWeaver") will be picked up automatically, if available, * removing the need for LoadTimeWeaver configuration on each affected target bean. * Consider using the {@code context:load-time-weaver} XML tag for creating * such a shared LoadTimeWeaver (autodetecting the environment by default). * <p><b>NOTE:</b> Only applied if no external PersistenceUnitManager specified. * Otherwise, the external {@link #setPersistenceUnitManager PersistenceUnitManager} * is responsible for the weaving configuration. * @see org.springframework.instrument.classloading.InstrumentationLoadTimeWeaver * @see org.springframework.instrument.classloading.ReflectiveLoadTimeWeaver */ @Override public void setLoadTimeWeaver(LoadTimeWeaver loadTimeWeaver) { this.internalPersistenceUnitManager.setLoadTimeWeaver(loadTimeWeaver); }
/** * Specify the Spring LoadTimeWeaver to use for class instrumentation according * to the JPA class transformer contract. * <p>It is a not required to specify a LoadTimeWeaver: Most providers will be * able to provide a subset of their functionality without class instrumentation * as well, or operate with their VM agent specified on JVM startup. * <p>In terms of Spring-provided weaving options, the most important ones are * InstrumentationLoadTimeWeaver, which requires a Spring-specific (but very general) * VM agent specified on JVM startup, and ReflectiveLoadTimeWeaver, which interacts * with an underlying ClassLoader based on specific extended methods being available * on it. * <p><b>NOTE:</b> As of Spring 2.5, the context's default LoadTimeWeaver (defined * as bean with name "loadTimeWeaver") will be picked up automatically, if available, * removing the need for LoadTimeWeaver configuration on each affected target bean. * Consider using the {@code context:load-time-weaver} XML tag for creating * such a shared LoadTimeWeaver (autodetecting the environment by default). * <p><b>NOTE:</b> Only applied if no external PersistenceUnitManager specified. * Otherwise, the external {@link #setPersistenceUnitManager PersistenceUnitManager} * is responsible for the weaving configuration. * @see org.springframework.instrument.classloading.InstrumentationLoadTimeWeaver * @see org.springframework.instrument.classloading.ReflectiveLoadTimeWeaver */ @Override public void setLoadTimeWeaver(LoadTimeWeaver loadTimeWeaver) { this.internalPersistenceUnitManager.setLoadTimeWeaver(loadTimeWeaver); }
/** * {@inheritDoc} */ @Override public void setLoadTimeWeaver(LoadTimeWeaver loadTimeWeaver) { persistenceUnitManager.setLoadTimeWeaver(loadTimeWeaver); }
/** * Specify the Spring LoadTimeWeaver to use for class instrumentation according * to the JPA class transformer contract. * <p>It is a not required to specify a LoadTimeWeaver: Most providers will be * able to provide a subset of their functionality without class instrumentation * as well, or operate with their VM agent specified on JVM startup. * <p>In terms of Spring-provided weaving options, the most important ones are * InstrumentationLoadTimeWeaver, which requires a Spring-specific (but very general) * VM agent specified on JVM startup, and ReflectiveLoadTimeWeaver, which interacts * with an underlying ClassLoader based on specific extended methods being available * on it. * <p><b>NOTE:</b> As of Spring 2.5, the context's default LoadTimeWeaver (defined * as bean with name "loadTimeWeaver") will be picked up automatically, if available, * removing the need for LoadTimeWeaver configuration on each affected target bean. * Consider using the {@code context:load-time-weaver} XML tag for creating * such a shared LoadTimeWeaver (autodetecting the environment by default). * <p><b>NOTE:</b> Only applied if no external PersistenceUnitManager specified. * Otherwise, the external {@link #setPersistenceUnitManager PersistenceUnitManager} * is responsible for the weaving configuration. * @see org.springframework.instrument.classloading.InstrumentationLoadTimeWeaver * @see org.springframework.instrument.classloading.ReflectiveLoadTimeWeaver */ @Override public void setLoadTimeWeaver(LoadTimeWeaver loadTimeWeaver) { this.internalPersistenceUnitManager.setLoadTimeWeaver(loadTimeWeaver); }