It depends -- each module could have a number of interceptors. You'd turn the interceptors off by excluding the global enabler dependency that Dan described, or re-including it as <provided> - whichever you see fit.<br>
<br>Perhaps yet another option would be to separate auto-registered interceptors into their own maven sub-modules, if we REALLY need to be that specific. This way you could include to enable each interceptor manually:<br>
<br><ul><li>seam-faces</li><li>seam-faces-conversations</li><li>seam-faces-security</li></ul><br>But again, and I am going to stand by this vehemently: I want automatic registration of interceptors. Provide what users want 95% of the time, and allow them to become more granular ONLY if they are in that 5% case -- but don't require every user to understand the ugly, complicated 5%. That's how Java EE, JSF, EJB, SOAP, etc, all lost their reputations.<br>
<br>Developer experience is crucial when designing this kind of interaction in a framework. These things will be the difference between adoption and abandonment.<br><br>--Lincoln<br><br><div class="gmail_quote">On Mon, Mar 29, 2010 at 2:03 PM, Nicklas Karlsson <span dir="ltr"><<a href="mailto:nickarls@gmail.com">nickarls@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">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.<br>
<br><div class="gmail_quote"><div><div></div><div class="h5">
On Mon, Mar 29, 2010 at 7:30 PM, Gavin King <span dir="ltr"><<a href="mailto:gavin.king@gmail.com" target="_blank">gavin.king@gmail.com</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><div></div><div class="h5">
I think you guys have got this wrong. CDI was deliberately designed to<br>
require explicit declaration of interceptors. We thought VERY HARD<br>
about this, and realized that this was the best way to go. Any<br>
auto-registration of interceptors runs into all kinds of problems down<br>
the road:<br>
<br>
(1) When I use two frameworks together, or add my own interceptor to<br>
the interceptors defined by a framework, what is its ordering with<br>
respect to the interceptors that already exist?<br>
<br>
(2) How do I turn an interceptor off?<br>
<br>
Look, CDI is supposed to be an ecosystem for multiple portable<br>
extensions that play nicely together. Auto-enablement of interceptors<br>
gets you into the total clusterfuck of phase listeners in JSF.<br>
<br>
Don't go down this path.<br>
</div></div><div><div><div></div><div class="h5"><br>
--<br>
Gavin King<br>
<a href="mailto:gavin.king@gmail.com" target="_blank">gavin.king@gmail.com</a><br>
<a href="http://in.relation.to/Bloggers/Gavin" target="_blank">http://in.relation.to/Bloggers/Gavin</a><br>
<a href="http://hibernate.org" target="_blank">http://hibernate.org</a><br>
<a href="http://seamframework.org" target="_blank">http://seamframework.org</a><br></div></div>
_______________________________________________<br>
</div><div class="im"><div>seam-dev mailing list<br>
<a href="mailto:seam-dev@lists.jboss.org" target="_blank">seam-dev@lists.jboss.org</a><br>
</div></div><div class="im"><div><div></div><div><a href="https://lists.jboss.org/mailman/listinfo/seam-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/seam-dev</a><br>
</div></div></div></blockquote></div><font color="#888888"><br><br clear="all"><br>-- <br>---<br>Nik<br>
</font></blockquote></div><br><br clear="all"><br>-- <br>Lincoln Baxter, III<br><a href="http://ocpsoft.com">http://ocpsoft.com</a><br><a href="http://scrumshark.com">http://scrumshark.com</a><br>"Keep it Simple"<br>