Re: [seam-dev] Interceptor packaging convention
One possible alternative is to give interceptors aliases (@Named) so the
developer can activate the function ("seam.security") and not the class
("org.jboss.seam.intercept.SecurityInterceptor").
But that, of course, would require a spec change (or a non-portable
extension).
-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 — 937 bytes)