When using a Java ME Web Service Client to access a Windows .NET web service the jaxrpc Operations class throws an 
JAXRPCException due to a java.rmi.MarshalException with the text "Missing SOAP Body or Envelope" while debugging a 
phone application in the emulator. NetBeans was running on a Windows Vista platform.

The following request frame was captured by Microsoft Windows Network Monitor:

<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xmlns:xsd="http://www.w3.org/2001/XMLSchema"
	xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"
	xmlns:tns="http://sys.service.rmas.dk/">
<soap:Body>
<tns:User_Login>
<tns:UserName>test</tns:UserName>
<tns:Password>a41d1ca98f00b204e9807998ecf842fe</tns:Password>
</tns:User_Login>
</soap:Body>
</soap:Envelope>

This resulted in the following response frame:

<?xml version="1.0" encoding="utf-8"?><soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xmlns:xsd="http://www.w3.org/2001/XMLSchema"><soap:Header><SecurityHeader 
xmlns="http://sys.service.rmas.dk/"><o_user /><o_password /><o_result /></SecurityHeader></soap:Header><soap:Body><User
_LoginResponse 
xmlns="http://sys.service.rmas.dk/"><User_LoginResult><Status>None</Status></User_LoginResult></User_LoginResponse></so
ap:Body></soap:Envelope>

You can see that NetBeans is polite and inserts a linefeed after each tag sent, whereas the server is rude and returns 
everything on one single line. The server was a Microsoft-IIS/6.0 with ASP.NET 2.0.50724.

Both the Envelope and Body tags are present as required, but they are in the middle of the line.
I suspect that the NetBeans SOAP parser expects these tags to be on the start of a line, as they are in most examples.
Consequently the parser cannot find the tags and the exception is thrown.