Re: [aspectwerkz-user] NoClassDefFoundError on applicatoin init

the core jar is generic, the normal jar is specific ie implement
interfaces from the core jar

the core jar provides abstraction as regards "class instrumentation"
which allow us to have consistency no matter how you are using AW
(offline, java 1.3, java 1.5, jrockit APIs), as well as enabling
others to make use of this generic hook (CGlib has a dependancy on
core f.e. and AspectJ 5 may have one or sort of to have AJ 5 load time
weaving all the way down to Java 1.3)

Alex

On 5/17/05, Mattias J <[email protected]> wrote:
> At 2005-05-17 11:34, Alexandru Popescu wrote:
> >Maybe it is a problem loading the class and that CL is reporting the wrong
> >error. I see AspectWerkzPreProcessor is using
> >ClassPreProcessor that is included in the aspectwerkz-core. Are these 2
> >jar loaded from the same CL?
> 
> No, that's it. The core jar was missing altogether.
> As usual the NoClassDefFound error does not show the class not found, but
> the class referring classes not found...
> Thanks for helping me track this down.
> 
> Though this leads to another question: is the core jar actually needed?
>  From what I remember, the JARs needed at runtime with offline weaving are
> those found in setEnv (this is still in great need of better documenting!),
> and the core jar is not listed there. (As I said, everything works fine
> without it)
> If the core jar is in fact needed, why is it separate from the main jar?
> 
>    /Mattias J
> 
>