wood burning stoves 2.0*
The moose likes Web Services and the fly likes Java client and .NET 2.0 ASP.NET Web Service: SOAP port uses a non-standard SOAP 1.2 binding Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of OCM Java EE 6 Enterprise Architect Exam Guide this week in the OCMJEA forum!
JavaRanch » Java Forums » Java » Web Services
Bookmark "Java client and .NET 2.0 ASP.NET Web Service: SOAP port uses a non-standard SOAP 1.2 binding" Watch "Java client and .NET 2.0 ASP.NET Web Service: SOAP port uses a non-standard SOAP 1.2 binding" New topic
Author

Java client and .NET 2.0 ASP.NET Web Service: SOAP port uses a non-standard SOAP 1.2 binding

michael laanti
Greenhorn

Joined: Apr 29, 2009
Posts: 3
Hello!

I have created a ASP.NET Web Service using Visual Studio 2008 and given Application property which declares that Web Service is .NET Framework 2.0 combatile. I have used Internet Exporer to get wsdl file and I have saved it into file system.

When creating proxy classes in Java side (wsimport and JDK 6.0 or Netbean 6.5.1), java tool throws warning like: [WARNING] SOAP port uses a non-standard SOAP 1.2 binding.

That wsdl imports xmldsig-core-schema.xsd for XML Signature but when creating .NET client with wsdl generated proxy everything seems to work allright.

Because this is not a WCF Web Service I haven't got any exotic bindings etc.

So can anyone have ideas what could cause this warning?

Br Michael
Ivan Krizsan
Ranch Hand

Joined: Oct 04, 2006
Posts: 2198
    
    1
Hi!
I have tried the same thing, but with .NET 3.0 standard, which did work without warnings.
Note that you also should set the compatibility in NetBeans by right-clicking the web service and viewing its properties.
Best wishes!
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Java client and .NET 2.0 ASP.NET Web Service: SOAP port uses a non-standard SOAP 1.2 binding