Header blocks in wrpc:signature

Several toolkits allow for the mapping of a SOAP header to a parameter,
this is not allowed by the current description of wrpc:signature in
section 4.1.1.

Would it be possible to clarify this to allow for root elements that are
out of message bounds as specified by the appropriate binding extension?
This would allow for both http and soap headers. 

Thanks,
-Jason

xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Jason T. Greene
Senior Software Engineer
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx