With the ws4ee implementation soap messages with optional complextypes and containing data were 'escaped' like this:

Code:

<ns1:RangeBasedCreateMapRequest xmlns:ns1="http://www.denhaag.nl/gbd/mapserver/v1.0">
<MapId>sprbuurtkaart</MapId>
<MapInResponse>false</MapInResponse>
<MapRange xsi:nil="1"/>
<DynamicProjectionItem xsi:nil="1"/>
</ns1:RangeBasedCreateMapRequest>

This means that the complex types do not have any value ( the java client code did not call the setters).
In the new JossWS stack the soap message looks like this:
Code:

<ns1:RangeBasedCreateMapRequest xmlns:ns1='http://www.denhaag.nl/gbd/mapserver/v1.0' xmlns:xsi='http:
//www.w3.org/2001/XMLSchema-instance'>
<MapId>StadsKaart</MapId>
<MapInResponse>false</MapInResponse>
<ns1:DynamicProjectionItem>
<ns1:Coordinate xmlns:ns1='http://www.denhaag.nl/gbd/mapserver/v1.0'><X>1.0</X><Y>2.0</Y>
</ns1:Coordinate>
<ToolTip>Dit is de tooltip</ToolTip>
</ns1:DynamicProjectionItem>
</ns1:RangeBasedCreateMapRequest>

In this soap request the DynamicProjectionItem element has a value.
However the maprange element not. This does not have to be a problem as the element is optional in the WSDL