You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by ax...@ws.apache.org on 2004/10/04 11:04:32 UTC

[jira] Commented: (AXIS-1581) NullPointerException - null reqMsg in Call.java

The following comment has been added to this issue:

     Author: Jayachandra Sekhara Rao Sunkara
    Created: Mon, 4 Oct 2004 2:04 AM
       Body:
Hi Peter!
Could you be more elaborate as to what you were doing on your side when you encountered this NPE. That would help us reproduce the bug. Were you just trying to run all the provided functional-tests or were you trying to set something up, in which case try to give a brief description of what you were trying to do (verbal description or code snippets etc).
We solicit your help in resolving this bug.

Thanks
Jayachandra
---------------------------------------------------------------------
View this comment:
  http://issues.apache.org/jira/browse/AXIS-1581?page=comments#action_53654

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/AXIS-1581

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: AXIS-1581
    Summary: NullPointerException - null reqMsg in Call.java
       Type: Bug

     Status: Unassigned
   Priority: Critical

    Project: Axis
 Components: 
             Basic Architecture
   Versions:
             1.2 Beta

   Assignee: 
   Reporter: Peter Smith

    Created: Thu, 30 Sep 2004 8:31 PM
    Updated: Mon, 4 Oct 2004 2:04 AM
Environment: Win2000 svr
Axis-1_2beta3

Description:
Running Junit functional-tests. 

WhiteMesaSoap12AddTestSvcTestCase part testXMLP2 gives NullPointerException in Call.java

Statement 
boolean isStream = ((SOAPPart)reqMsg.getSOAPPart()).isBodyStream();
references 'reqMsg' without testing for null.


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira