John Doe
    
  
  
    
      FOO
    
  

In this case, the node is within an node within the SOAP Header. This type of envelope can be created with Stubby code similar to this:

import StockInfoNamespace.*;
import lotus.domino.axis.client.Stub;
import lotus.domino.axis.message.SOAPHeaderElement;
import javax.xml.soap.SOAPElement;

StockInfoServiceLocator locator = new StockInfoServiceLocator();
StockInfoService service = locator.getDomino();
SOAPHeaderElement headerElement = new SOAPHeaderElement(
    "urn:thisNamespace", "AuthenticationInfo");
SOAPElement node = headerElement.addChildElement("UserName");
node.addTextNode("John Doe");
((Stub) service).setHeader(headerElement);
service.GetStockInfo("FOO"); 

Note that we're talking about SOAP Envelope Headers here, not HTTP headers. You can set HTTP headers too if you'd like. The normal reason is to set a session cookie or to use basic authentication. Here is some sample code for that situation:

import StockInfoNamespace.*;
import lotus.domino.axis.transport.http.HTTPConstants;
import lotus.domino.axis.client.Call;

StockInfoServiceLocator locator = new StockInfoServiceLocator();
StockInfoService service = locator.getDomino();
// to set a cookie:
service._setProperty(
    HTTPConstants.HEADER_COOKIE, "AuthToken=abc123");
// to use Basic HTTP Authentication:
service._setProperty(
    Call.USERNAME_PROPERTY, "user name");
service._setProperty(
    Call.PASSWORD_PROPERTY, "password");
service.GetStockInfo("FOO"); 

Speaking of HTTP headers, if a SOAPAction Header was specified in the WSDL file, it will be generated automatically by the client code. No need to worry about that.