How to create SOAP Header elements using SAAJ??

Question

I am facing a problem when adding header elements under SOAP Header
using SAAJ(api).
I want to create a structure as following:
I get a empty SOAP header obejct by writing code--> SOAPHeader header
= envelope.getHeader();
But not able to add SOAP header elements as specified in example
below. I tried but its giving me error as
"HeaderElements must be namespace qualified"
CAN ANYBODY TELL ME THAT HOW TO ADD HEADER ELEMENTS USING SAAJ??
<SOAP:Header>
<AccountNumber>123</AccountNumber>
<AuthorisationCode>test111</AuthorisationCode>
<Source>abc</Source>
<Market>01</Market>
</SOAP:Header>

Answer 1

I'm including this comment from some code I've just written after wrestling with this for hours (I've actually left it on another post as well). The upshot of it all is that you have to include a namespace URI when creating a header in SAAJ:
        NOTE: SOAP 1.1 requires that all header entries be namespace-qualified to
        namespace URI's.  The SAAJ 1.2 implementation requires a Name object with
        the namespace URI to make this happen even if the prefix used is already
        visible by being declared higher in the document (e.g. in the Envelope).
        However, the namespace URI is not present in the serialized header element
        as long as it was declared higher in the document.  In order to create a
        header element without a prefix (to conform to a web service definition
        that doesn't use a prefix in its headers, for example), leave the prefix
        null in the addHeaderElement() method. 
        For example, with a SOAPHeader 'hdr':
          //first create the name
          Name name = env.createName("my-local-name", null, "my-URI");
          //then create the header element
          SOAPHeaderElement he = hdr.addHeaderElement(name);
        This would result in an XML element that looked like this:
          <my-local-name xmlns="my-URI"/>
        This would allow SAAJ developers to create a header for a service that
        only expected a local name in its header elements (as many do!).  As long
        as the service doesn't choke on the attribute (validation!  evil!), this
        should work.
                                                    Rob Kemmer
                                                    01/12/2005