GeeCON Prague 2014*
The moose likes Web Services and the fly likes 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


JavaRanch » Java Forums » Java » Web Services
Bookmark "SOAP port uses a non-standard SOAP 1.2 binding." Watch "SOAP port uses a non-standard SOAP 1.2 binding." New topic
Author

SOAP port uses a non-standard SOAP 1.2 binding.

Neal Sharman
Greenhorn

Joined: Oct 24, 2007
Posts: 16
Any idea why a soap 1.2 binding produces this message whilst running apt and wsgen. Also I have to use the protocol Xsoap1.2 and extension attribute in order for this to work. Per metro web site documentation soap 1.2 is regarded as non standard? Why is soap 1.2 regarded as non standard.
Thanks
Ivan Krizsan
Ranch Hand

Joined: Oct 04, 2006
Posts: 2198
    
    1
Hi!
Perhaps because WS-I Basic Profile 1.1 and WSDL 1.1 only talks about SOAP 1.1 and not SOAP 1.2?
References:
http://www.w3.org/TR/wsdl#_soap-b
http://www.ws-i.org/Profiles/BasicProfile-1.1.html#WSDLSOAPBINDING
Best wishes!
Neal Sharman
Greenhorn

Joined: Oct 24, 2007
Posts: 16
Ivan Krizsan wrote:Hi!
Perhaps because WS-I Basic Profile 1.1 and WSDL 1.1 only talks about SOAP 1.1 and not SOAP 1.2?
References:
http://www.w3.org/TR/wsdl#_soap-b
http://www.ws-i.org/Profiles/BasicProfile-1.1.html#WSDLSOAPBINDING
Best wishes!


Hello

Thanks for the post. Does this mean that the protocol soap1.2 is being recognized however the service still issues a complaint?
Thanks
Ivan Krizsan
Ranch Hand

Joined: Oct 04, 2006
Posts: 2198
    
    1
Neal Sharman wrote:Thanks for the post. Does this mean that the protocol soap1.2 is being recognized however the service still issues a complaint?

Yes, to me it looks like this is the case.
Do the web service work as expected, apart from the abovementioned log message?
Best wishes!
Neal Sharman
Greenhorn

Joined: Oct 24, 2007
Posts: 16
Ivan Krizsan wrote:
Neal Sharman wrote:Thanks for the post. Does this mean that the protocol soap1.2 is being recognized however the service still issues a complaint?

Yes, to me it looks like this is the case.
Do the web service work as expected, apart from the abovementioned log message?
Best wishes!


Yes it does. Though the console keeps spitting out this message for every request. I was wondering why it would do that.
 
GeeCON Prague 2014
 
subject: SOAP port uses a non-standard SOAP 1.2 binding.