Re: [seam-dev] Interceptor packaging convention

> So I guess the real issue at hand is...the consistent packaging of interceptors is really about making the <interceptors> element as simple as possible by making all the interceptors classes have the same number of package segments. That need may or may not be contrived. I haven't stood in the shoes of the developer yet being required to list out a bunch of interceptor classes. It sounds contrived to me. Where does it come from? Given that a user might declare some interceptors, where does that leave them?