Interceptors in Weld

[asookazian]

Seam used lots of custom interceptors for bijection, bpm, conversations, etc.

What has changed in terms of interceptors in Weld and/or Seam 3?

[nickarls]

Weld doesn't use interceptors for any of the core functionality and Seam 3 won't need any bijection interceptors. The transactional interceptor will still be around and others, as needed.

[asookazian]

So I assume that @BypassInterceptors will still be available in Seam 3 as a performance optimization?

[gavin.king]

No, it's not needed. What Nick is trying to say is that there are no interceptors by default.

[nickarls]

One would assume that there is flexible control over interceptors, yes (although interceptor bindings/enabling is pretty flexible in CDI as it is). And since there is no bijection-interceptor, I don't think there will be that much of a performance hit OOTB.

[asookazian]

So Seam 3 will have some performance optimizations done to it in terms of removing any/all interceptors as a result of using Weld as the core?

If this is true, this will make Seam 3 more marketable and possibly more widely adopted (in addition to changes in JSF 2.0)...

[nickarls]

Yep.

Ha! Last word on forum, now I can go to sleep ;-)