DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10091>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10091

Message with 3 headers causes NPE

           Summary: Message with 3 headers causes NPE
           Product: Axis
           Version: current (nightly)
          Platform: All
        OS/Version: Other
            Status: NEW
          Severity: Blocker
          Priority: Other
         Component: Basic Architecture
        AssignedTo: [EMAIL PROTECTED]
        ReportedBy: [EMAIL PROTECTED]


Given a simple client like (a.java):
import org.apache.axis.* ;
import org.apache.axis.client.* ;
import org.apache.axis.message.* ;
public class a {
  static void main(String[] args) throws Exception {
    Service service = new Service();
    Call    call    = (Call) service.createCall();
    SOAPHeaderElement  header = new SOAPHeaderElement("foo", "foo");

    call.setTargetEndpointAddress
("http://localhost:81/axis/services/AdminService";);
    call.addHeader( header );
    call.addHeader( header );
    call.addHeader( header );
    call.invoke( "foo", new Object[] {} );
  }
}

causes a NPE in DeserializationContextImpl.java line 879:
  curElement.setContentsIndex(recorder.getLength());
curElement is null.  
2 headers work just fine - 3 makes it blow.

Reply via email to