login      my ps      about      contact  



home instructor-led training online training blogs


XML Nation » Indigo, WS-* and the WS-I Basic Profile

Indigo, WS-* and the WS-I Basic Profile

The Indigo bindings that support the WS-* protocols use SOAP 1.2, not SOAP 1.1. That makes them incompatible with the WS-I Basic Profile, a standard that many companies require services to comply with. The WS-I Basic Profile was specifically designed to be not restrict either message header or body content, specifically because we knew that WS-* was going to be a big deal. So what should happen here? Should Indigo support using WS-* with SOAP 1.1, or is there a reason it has to use SOAP 1.2? If the latter, should the WS-I BP be updated to support SOAP 1.2 or should companies move away from the BP? If the latter, does that open the door for the return of SOAP encoding? What's the right thing to do?
Posted May 05 2005, 10:07 PM by tim-ewald

Comments

Dion Hinchcliffe wrote re: Indigo, WS-* and the WS-I Basic Profile
on 05-06-2005 7:16 AM
Yes, a pretty difficult problem. WS-I Basic Profile needs to adapt with the industry or become a relic. Personally, I'm for bifurcating support in the Basic Profile between REST and SOAP to make them equal citizens in the Basic Profile, and upgrading it to SOAP\1.2. But that's probably a pipe dream and another story...

But IMHO the smartest thing for Indigo to do is to somehow support WS-I Basic Profile as it is today, or risk (at least on the back of the box) being labelled non-interoperabile with the rest of the web services world.
Tim wrote re: Indigo, WS-* and the WS-I Basic Profile
on 05-10-2005 7:10 AM
Dion,

Let me clarify that Indigo *does* support the WS-I Basic Profile, but only if you aren't using WS-* protocols.

Tim-
Kirill's notes wrote Another comment about WS-I BP and WS-*
on 05-11-2005 11:08 PM
Kirill's notes wrote Another comment about WS-I BP and WS-*
on 05-11-2005 11:16 PM
Kevin W. Hammond wrote re: Indigo, WS-* and the WS-I Basic Profile
on 05-28-2005 8:56 AM
Tim, I live the .NET/J2EE Web services interop story every single day. My #1 problem is J2EE implementations that do not support the latest versions of specifications and therefore do not interoperate well with .NET.

By Indigo only suporting SOAP 1.2 when using the WS-* protocols (the biggest right now being folks that want WS-Security), we run the risk of having a great communications stack that cannot interoperate with the "legacy" Java implementations out there.
John Arbuckle wrote re: Indigo, WS-* and the WS-I Basic Profile
on 11-09-2005 10:45 PM
can anybody tell me what is ws-i AND WS-* exactly?

Add a Comment

(required)  
(optional)
(required)  
Remember Me?


home instructor-led training online training blogs

781.749.9238 (East Coast) | 310.251.9901 (West Coast) | Pluralsight, LLC , 185 Lincoln St., Suite 305, Hingham, MA 02043-1741

Copyright © 2008 Pluralsight LLC. All rights reserved.

designed by nukeation