I investigated this a bit further... first of all, the reason why you don't get the parameter corresponding to the soap header is that the JAX-WS specs say that only the wsdl:part from the abstract portion of the contract (i.e. the wsdl:portType section) are mapped to Java method parameters. I see three possible solutions to this, unfortunately they're all not so easy / for beginners: - manually modify the wsdl before consuming it, in order to let wsconsume generate the soap header parameter too - create a SOAPHandler and mess with SAAJ to manually add the header when sending the message - leverage SunRI tool (wsimport), which starting from v. 2.1.3 has a new option -XadditionalHeaders that map additional headers in wsdl:binding section as method parameters. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4116960#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...