Sad Direction MS Indigo moving away from WS Standards

[Jules]

So with MS looking towards Longhorn Indigo messaging, for Service
based Applications Integration, its brief dalience with adoption of
industry wide Web Service standards is over. This is a major
dissapointment we were looking towards a more positive attitude
towards interoperation with third party products. Is it not possible
for MS to ensure that Indigo has some compliance with emerging
Asynchronous/Message based Web Service open standards ? It is looking
very much as though MS believes that our servers only have to
interoperate with MS Windows platforms. This is a pretty stupid
assumption, even if a lot of would love to redevelop everying on MS
Windows and .NET. It just isn't going to happen.

So it looks as though Longhorn is going to drive us back to making a
hard choice between J2EE and MS System Development. From where we sit
today I can only recommend that our product development team return to
the standards based J2EE community, because we can not afford to none
interoperable with third party systems and products.

Very sad, Very sad, I was hoping MS had a direction with .NET and
Webservices.

[Jeffrey Wynn]

Jules,

I'm not sure where you got your information. Could you post a link to
whatever your source is if possible? From all that I've read, and based on
what I've used of the preview of Whidbey, Indigo is going to support at
least the standards that the WSE supports today. Perhaps you'd be
interested in reading the following FAQ, particularly the last two questions
in the Migration section.

http://msdn.microsoft.com/library/en...asp?frame=true

--
Jeffrey Wynn
so********@nospam.net
Replace nospam with "op-t-onl-ine" without the dashes
"Jules" <Ro********@hotmail.com> wrote in message
news:80**************************@posting.google.c om...

So with MS looking towards Longhorn Indigo messaging, for Service
based Applications Integration, its brief dalience with adoption of
industry wide Web Service standards is over. This is a major
dissapointment we were looking towards a more positive attitude
towards interoperation with third party products. Is it not possible
for MS to ensure that Indigo has some compliance with emerging
Asynchronous/Message based Web Service open standards ? It is looking
very much as though MS believes that our servers only have to
interoperate with MS Windows platforms. This is a pretty stupid
assumption, even if a lot of would love to redevelop everying on MS
Windows and .NET. It just isn't going to happen.

So it looks as though Longhorn is going to drive us back to making a
hard choice between J2EE and MS System Development. From where we sit
today I can only recommend that our product development team return to
the standards based J2EE community, because we can not afford to none
interoperable with third party systems and products.

Very sad, Very sad, I was hoping MS had a direction with .NET and
Webservices.

[Klaus H. Probst]

Indigo will produce and consume transport messages using SOAP. How much more
"compliant" would you like it to get?

I'd suggest you read the specs and articles (at least what's out there now)
to get a better idea of how the thing is supposed to work.

And as far as having a "hard choice" between J2EE and Indigo... well,
Microsoft is not about to give you J2EE on Windows just because you think
it's cool. They'll give you whatever they want and if you don't like it then
use something else. Most J2EE implementations run fine on Windows. In any
case, as long as you can speak XML/SOAP and TCP you'll be able to talk to
Indigo.

--
____________________
Klaus H. Probst, MVP
http://www.vbbox.com/

"Jules" <Ro********@hotmail.com> wrote in message
news:80**************************@posting.google.c om...

So with MS looking towards Longhorn Indigo messaging, for Service
based Applications Integration, its brief dalience with adoption of
industry wide Web Service standards is over. This is a major
dissapointment we were looking towards a more positive attitude
towards interoperation with third party products. Is it not possible
for MS to ensure that Indigo has some compliance with emerging
Asynchronous/Message based Web Service open standards ? It is looking
very much as though MS believes that our servers only have to
interoperate with MS Windows platforms. This is a pretty stupid
assumption, even if a lot of would love to redevelop everying on MS
Windows and .NET. It just isn't going to happen.

So it looks as though Longhorn is going to drive us back to making a
hard choice between J2EE and MS System Development. From where we sit
today I can only recommend that our product development team return to
the standards based J2EE community, because we can not afford to none
interoperable with third party systems and products.

Very sad, Very sad, I was hoping MS had a direction with .NET and
Webservices.

[Jules]

Hello,

Your link is only partially reassuring. It is no means clear that
Indigo will be message based interoperable with J2EE (JMS) and BEA adn
Websphere etc, only that it will be compliant with todays Web Services
(Synchronous) standards. Without any clear open standards on message
based web services I am probably being too harsh on MS.

However my pessimistic view has been provoked by the following rather
stark quote:

"Microsoft is saying, 'All this open standards with Web services has
gone far enough,'" said the executive, who requested anonymity. "It's
back to the movie as we know it."

Which lies within a ZDNEt article

http://zdnet.com.com/2100-1104_2-5061198.html

So I remain rather sceptical until MS make it clearer their intent wrt
to opne standards.

Jules

"Jeffrey Wynn" <so********@optonline.net> wrote in message news:<O6**************@TK2MSFTNGP09.phx.gbl>...

Jules,

I'm not sure where you got your information. Could you post a link to
whatever your source is if possible? From all that I've read, and based on
what I've used of the preview of Whidbey, Indigo is going to support at
least the standards that the WSE supports today. Perhaps you'd be
interested in reading the following FAQ, particularly the last two questions
in the Migration section.

http://msdn.microsoft.com/library/en...asp?frame=true

--
Jeffrey Wynn
so********@nospam.net
Replace nospam with "op-t-onl-ine" without the dashes