From 4a48f8cdb876becb88b43d26d4f586fbd3f61e7b Mon Sep 17 00:00:00 2001 From: wisberg Date: Fri, 3 Mar 2006 18:26:06 +0000 Subject: [PATCH] If aspects are required to compile, then weaving must be at compile-time. duh. --- docs/devGuideDB/ltw.xml | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/docs/devGuideDB/ltw.xml b/docs/devGuideDB/ltw.xml index 6408d634e..35f53afba 100644 --- a/docs/devGuideDB/ltw.xml +++ b/docs/devGuideDB/ltw.xml @@ -14,11 +14,16 @@ Compile-time weaving is the simplest approach. When you have the source code for an application, ajc will compile from source and produce woven class files as output. The invocation of the weaver is integral to the ajc compilation process. The - aspects themselves may be in source or binary form. + aspects themselves may be in source or binary form. + If the aspects are required for the affected classes to compile, then + you must weave at compile-time. Aspects are required, e.g., when they + add members to a class and other classes being compiled reference the + added members. + Post-compile weaving (also sometimes called binary weaving) is used to weave existing class files and JAR files. As with compile-time weaving, the aspects used for weaving may be in source or binary form, - and may themselves be woven by aspects. + and may themselves be woven by aspects. Load-time weaving (LTW) is simply binary weaving defered until the point that a class loader loads a class file and defines the class to the JVM. To support this, one or more "weaving class loaders", either provided explicitly by the run-time -- 2.39.5