From Jason B:

I have an input msg to a SOAP BC SU operation defined as
   <xsd:complexType name="LocationInfo">
       <xsd:sequence>
           <xsd:element name="address" type="xsd:string"></xsd:element>
           <xsd:element name="city" type="xsd:string"></xsd:element>
           <xsd:element name="state" type="xsd:string"></xsd:element>
       </xsd:sequence>
   </xsd:complexType>
   <xsd:element name="location" type="tns:LocationInfo"></xsd:element> 

When I create a unit test from the below xsd snippet, the input msg appears as:

<soapenv:Envelope xsi:schemaLocation="http://schemas.xmlsoap.org/soap/envelope/ http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:loc="http://xml.netbeans.org/schema/locationInfo">
 <soapenv:Body>
   <loc:location>
     <loc:address>?string?</loc:address>
     <loc:city/>
     <loc:state/>
   </loc:location>
 </soapenv:Body>
</soapenv:Envelope> 

Notice that two of the tags were not generated correctly.

Its not a big issue but I'd like to know if its something specific about the way the input msg is defined or if something strange has been introduced in v2.2.