There are two problems with this. 1. The LoginConfigInterceptor is not considering operation in an aggregate deployment like an ear that can have multiple login-config.xml descriptors. It would just work if very login-config.xml was distinct, but it will fail if there are overlapping application-policy definitions. One possible mode of operation in the aggregate case would be to merge all login-config.xml descriptors with any conflicts being resolved by taking the application-policy first defined in a breadth-first traversal of the deployment heirarchy.
2. There is no support for a global specification of inteceptor(s) which should be applied to all deployers. This is an aspect of the more general configuration issue raised here: http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3864275#3864275 View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3864276#3864276 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3864276 ------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
