Ok, I've finally found out what was wrong. First of all, the tutorial is correct and everything should work fine even without the @Policy annotation (provided of course you embed your WS-Policy in the WSDL file). Strange thing though: When using "wsdLocation" in @WebService, JBoss reads the WSDL file you provided and does the following: 1) if the <soap:address> tag in the WSDL file has a "file://..." URL in it, it does NOT replace it with the actual address where your web service endpoint was bound. 2) if the <soap:address> tag in the WSDL file has an "http://..." URL in it, it replaces it with the actual address where your web service endpoint was bound. I had the bad luck of having specified file://path/to/my/contract.wsdl causing the weird behavior. I know this is totally unrelated to the topic of this thread by now, but I wanted not to leave any lingering doubt regarding the approach without @Policy (which I prefer by the way). In any case, before I go running to JIRA, can someone explain if there's some reason why JBoss won't touch the file:// address bindings and therefore this is proper behavior, or would you consider this a bug? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4169836#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...