[seam-dev] Javassist limitation?

Dan Allen dan.j.allen at gmail.com
Mon May 19 13:26:07 EDT 2008


> Seam uses javassist, but we use it to generate proxies not to instrument the
> code.

Yep, exactly what I was about to write in response. So essentially we
are getting the same behavior as we would with a JDK proxy.

So the decision for the future is to whether this is just the way life
is going to be or whether we need to find a general approach to allow
more fine-grained interceptor calls. I doubt that JBoss AOP is the
only library that solves this problem. I have no doubt the Spring guys
will just love to kick us over this issue (given that AspectJ can
handle it). One response is that simplicity is better.

-Dan

-- 
Dan Allen
Software consultant | Author of Seam in Action

http://www.mojavelinux.com
http://manning.com/dallen

NOTE: While I make a strong effort to keep up with my email on a daily
basis, life and work come first and, at times, keep me away from my mail
for a while. If you contact me, then don't hear back for more than a week,
it is very likely that I am excessively backlogged or the message was
caught in the spam filters. Please don't hesitate to resend a message if
you feel that it did not reach my attention.



More information about the seam-dev mailing list