>>One of the UC for complex XML data types stems from the way AXXIS [main java tool for WS] fits java general usuage.
>>Usually Biz objects [for instance implemented as pojo] will be serialized into a complex XML type and re-used in other WSDL's.
>>
>>Strategy to work against I pick after talking to the developers of the WS I need to integrate.
>
>So, I will assume they use Java on the other end. Does this mean, I cannot consume it from a .NET environment?

That would be way too harsh... There CAN be some kinks in the WS if the developer sets certain options which .Net will not set automatically (esp. some cookie-similar identification settings) but you can identify these with a sniffer.
Is there a problem if you import the WSDL ? If so, there exisits some tool to create Dotnet "Dummy" apps from Axxis - Was told that from some Axxis devs which generate Dotnet example everytime they change something in their setup. Dunno how that works, though...

Worst case: String operations. Did that to consume Axxis in Vfp directly.

regards

thomas