Re: [seam-dev] Interceptor packaging convention
Dan's point was that they would want to have the same number of package
segments in all the interceptor definitions. I don't think that they will
ever achieve this, as they might pull in a third-party interceptor, or
define their own, which isn't in a place with the same number of package
segments.
Well, naturally, we can't control everything. I was just thinking for our
own sanity, within Seam, we could ensure some sort of consistency.
Arguably, it's not the number of package segments that matters, it's the
entire prefix (for readability).
Right, my interest is being able to quickly scan our list of interceptors
and be able to recognize when there is a typo...or to be able to recall
interceptors from memory (based on pattern). Typical things to consider when
you are defining an API I would reason.
-Dan
--
Dan Allen
Senior Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #231597
http://mojavelinux.com
http://mojavelinux.com/seaminaction
http://www.google.com/profiles/dan.j.allen
Attachments:
- attachment.html (text/html — 1.5 KB)