Thanks Scott, Unfortunately, the server.log gives exactly the same error message. Something even stranger: when I comment out my new policy, the error still occurs, although the uncommented XML is the same than the original file. Some other test I did: duplicating an existing policy (and changing its name of course) leads to the same exception. Any suggestion?
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3863918#3863918 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3863918 ------------------------------------------------------- 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-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
