wse3.0

All the geeks will say WSE is outdated.. Thats ok for me right now.. Just trying to find a solution for my problem Trying to consume a Java webservice using WSE. In the outgoing soap request has an security has additional time stamp node. My outgoing soap request looks like this <soap:Header> <wsa:Action wsu:Id="Id-6209d12b-20bf-407e-ac72-533d0f671a2c"></wsa:Action> <wsa:MessageID wsu:Id="Id-280fe225-2f80-4f37-b5d4-120146fc7dec">urn:uuid:a427b687-6f52-4689-9df2-c2e3c6d9ea1a</wsa:MessageID>< wsa:ReplyTo wsu:Id="Id-bc623f16-761c-4e03-a23e-aa70bd9b8d34"><wsa:Address>http://schemas.xmlsoap.org/ws

I have an ASMX web service which has a method - void DoSomething(List<string> list); I have implemented this service, compiled and hosted in IIS. I used wsewsdl3.exe to generate the proxy. In the generated proxy the method definition is changed to - DoSomething(string[] list) { .. Is it not possible to have List as a parameter to an ASMX web service? What should I do to fix the proxy? That's normal. Generics are a .NET specific artifact. There's no such notion in the generated WSDL. Imagine a client which doesn't support generics like PHP for example. That's the reason why your generic