Why does everyone think jAdvise is interface-based? It instruments the bytecode, and yes, it is very fast. :)

That aside, JAC is definitely more encompassing.

Bob

On Sunday, January 12, 2003, at 03:43 PM, Laurent Martelli wrote:

"Bob" == Bob Lee <[EMAIL PROTECTED]> writes:
Bob> jAdvise does exactly what you need. http://crazybob.org/. Look
Bob> at jAdvise SEQUENCE for an example.

So does JAC (http://jac.aopsys.com/)

I have only briefly looked at jAdvise, and it looks like we are doing
roughly the same things. However, it must be faster since it uses
interfaces for aspect advices (JAC uses dynamic invocation of
methods). But the JAC framework is probably more featurefull (it has
a library of ready to use aspects, you can specify precisely which
methods are to be wrapped -- with jAdvise, it looks like all methods
are wrapped). The choice is up to you. You may also have a look at
AspectJ (http://www.aspectj.org/), which is another AOP framefork for
Java.

Regards,
Laurent

--
Laurent Martelli http://jac.aopsys.com/
[EMAIL PROTECTED] http://www.bearteam.org/~laurent/


--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to