[seam-dev] Interceptor packaging convention

[Nicklas Karlsson]

Tools might also be helpful in setting up interceptors based on what you
have available, I suppose. And the list of interceptors for a normal Seam 3
application is hopefully shorter than that from a Seam 2 app.

On Mon, Mar 29, 2010 at 7:30 PM, Gavin King <gavin.king at gmail.com> wrote:

> I think you guys have got this wrong. CDI was deliberately designed to
> require explicit declaration of interceptors. We thought VERY HARD
> about this, and realized that this was the best way to go. Any
> auto-registration of interceptors runs into all kinds of problems down
> the road:
>
> (1) When I use two frameworks together, or add my own interceptor to
> the interceptors defined by a framework, what is its ordering with
> respect to the interceptors that already exist?
>
> (2) How do I turn an interceptor off?
>
> Look, CDI is supposed to be an ecosystem for multiple portable
> extensions that play nicely together. Auto-enablement of interceptors
> gets you into the total clusterfuck of phase listeners in JSF.
>
> Don't go down this path.
>
> --
> Gavin King
> gavin.king at gmail.com
> http://in.relation.to/Bloggers/Gavin
> http://hibernate.org
> http://seamframework.org
> _______________________________________________
> seam-dev mailing list
> seam-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/seam-dev
>



-- 
---
Nik
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/seam-dev/attachments/20100329/f57ee5fa/attachment-0001.html