login      my ps      about      contact  



home instructor-led training on-demand screencasts blogs


Service Station, by Aaron Skonnard » My WSE3 wish-list

My WSE3 wish-list

Service Station, by Aaron Skonnard

Pluralsight Blogs

Syndication

Recent Posts

Tags

View more

Resources

Archives

Last week in Redmond I had a chance to catch up with a friend on the WSE team. They're trying to finalize plans for WSE 3.0 as I write this - last chance for feature requests - so here's my list:
 
  1. ASMX integration with the WSE messaging API. I'm not sure how feasible this is but I'd really like to see SoapService, SoapClient, [SoapMethod] et. al. go away and standardize on the ASMX OM instead. It seems like they just duplicate and complicate. I'd like to be able to host an ASMX class in any process over any WSE transport. Realigning the two frameworks would make the current offering very compelling and attractive, giving people the power of WSE without the worries related to migration.
  2. Improved support for XML messaging scenarios. While #1 is important for the ASMX masses, I think keeping SoapReceiver and SoapSender around and enhancing them for pure messaging scenarios is also key. For example, adding better support for streaming scenarios is something to consider here.
  3. Addition transports. I'd like to see a few additional transports besides HTTP and TCP. SMTP and UDP are obvious choices, especially since there are already samples lying around. This would likely push along the standards work in these areas and make the whole SOAP thing worthwhile.
  4. WS-ReliableMessaging. Out of all the WS-* specs that WSE2 doesn't support, this seems like the next one to bite off. It becomes more compelling when building services over unreliable transports.
  5. MTOM. Simply because I'd like to see the binary attachment debate end. And I believe it will end once we have an interoperable solution across MS, IBM, and BEA.
 
I know feedback on these items will be helpful in determining what actually makes it. What do you think about this list? What's at the top of yours?
 
Posted Nov 10 2004, 05:11 PM by Aaron Skonnard

Comments

Ken Brubaker wrote re: My WSE3 wish-list
on 11-10-2004 1:39 PM
WSS bindings for SAML and Liberty would be at the top of my list.
Anil John wrote re: My WSE3 wish-list
on 11-10-2004 1:43 PM
Full support for SAML and XACML.
notgartner.com: Mitch Denny's Blog wrote WSE3: My Additions to the Feature List
on 11-11-2004 2:26 AM
JF wrote re: My WSE3 wish-list
on 11-11-2004 4:15 AM
I think you've hit the nail on the head with the MTOM request. Everyone has been waiting on a "consistent" answer to the attachment problem, so it would be a welcomed feature!
Erv Walter wrote re: My WSE3 wish-list
on 11-11-2004 9:27 AM
Top wish list item:

Interoperability between WSE 2 and WSE 3 and interoperability between WSE 3 and less-than cutting edge Java toolkits.

In the real world, it's often impracticle to require that all end points update their implementations of the various WS-* specs simultaneously. This is especially true with cross-organization collaborations.

See also:

http://ewal.net/PermaLink,guid,c0c80ce6-c2cb-48fa-a252-1646c76bb830.aspx

and:

http://staff.newtelligence.net/clemensv/PermaLink.aspx?guid=e666969b-c32c-45e3-b2bb-feb198e7eefa
Christian Weyer: Smells like service spirit wrote WSE3 - what do *you* want?
on 11-11-2004 11:04 AM
Roman Kiss, MVP wrote re: My WSE3 wish-list
on 11-11-2004 1:05 PM
WSE2 Messaging offers a technology making a connected system based on the WS-*. It's a lightweight infrastructure to understand a qualitative change of the connectivity a message driven architecture before coming the Indigo. We can ask to add more implementation of the WS-* such as WS-Enumeration, WS-Eventing, WS-Transfer, WS-ReliableMessaging,etc. also administratively configuration, better plumbing for filters, configuration of the services on the fly (useful for SingleCall registration), more transports, etc.
All these features are making better encapsulation of the business layer from the connectivity and transparencies between the business object and its consumer.

The WSE 3.0 Messaging should be having some features to support interoperability to the Indigo from the Windows 2k/98 applications. When Indigo beta 1 will be release, the new connectivity story will start it for Win2k3/XPSP2 + higher applications. There is no reason to wait for WSE3 beta with fewer features than Indigo will offer it. Of course, that’s depending from the release timeframe between the WSE3 and Indigo.

We know now, that Indigo will not support platform Win2k/98, so coming to my wish, the WSE3 team should be more focus on this issue and cooperate with the Indigo team instead of adding more features which they are included in the Indigo. That does extend life of the WSE usage.

On the other hand, if this version (WSE3) is focusing on support messaging on the Win2k/98 + higher platforms, it will be nice to have (based on the Indigo features) the following features: MTOM, ReliableMessaging and Configuration Manager (included hosting services).

Roman
paulb wrote re: My WSE3 wish-list
on 11-11-2004 2:41 PM
Easier access to the soapcontext when not hosting your webservice in IIS.
Miguel wrote re: My WSE3 wish-list
on 11-12-2004 6:14 AM
Just one: back to simplicity
Aaron Skonnard wrote re: My WSE3 wish-list
on 11-12-2004 7:16 AM
Mark adds "performance" to the top of the list - http://blogs.msdn.com/mfussell/archive/2004/11/11/256306.aspx
Simon Fell wrote re: My WSE3 wish-list
on 11-12-2004 7:19 AM
Fix the problems with sending WS-Adressing EPR's over the wire http://www.pocketsoap.com/weblog/2004/11/1498.html
JeffK wrote re: My WSE3 wish-list
on 11-12-2004 8:11 AM
Available for .Net 1.1
Don Box's Spoutlet wrote WSE 3 and Fussell
on 11-12-2004 11:01 PM
Rob Cannon wrote re: My WSE3 wish-list
on 11-13-2004 7:27 AM
I would like to see a proxy generator that can generate classes that use property accessors (ala .NET 2.0). I would actually like to see this in a SP for WSE 2.0!
Keith Rome wrote re: My WSE3 wish-list
on 11-13-2004 10:49 AM
1. Maybe add some form of WSDL generator support for SoapServer? Even a "hack" that you point to a compiled assembly that contains the SoapServer...

2. A proxy generator tool that can make a SoapClient with all the stub methods needed to bang against a SoapServer from my #1 above.

3. For [SoapMethod()], the ability to have WSE perform schema validation on the input and/or output messages automatically.

4. PLEASE DOCUMENT all supported protocols, not just "soap.tcp" and "soap.http"! I know (think?) there is "soap.inproc" and maybe others... but its torture trying to find information on these.
Faisal Waris wrote re: My WSE3 wish-list
on 11-14-2004 6:11 PM
Hi,

In a siginificant automotive vertical we are embarking on standardized B2B process integration using WS* specs.

The basics of WS* are in place in terms of specs and tooling (except for good schema support in some Web Service tools).

What is missing is WS-ReliableMessaging implementations. Lack of reliable messaging is a serious impediment in the B2B space; a veritable knock on WS* vis-a-vis the ebXML camp.

Please add WS-ReliableMessaging to WSE 3.
Kapil Sachdeva wrote re: My WSE3 wish-list
on 11-14-2004 8:22 PM
My wish list : SAML 2.0 & WS-Federation
Jes wrote WSE 3
on 11-14-2004 10:26 PM
amachin wrote re: My WSE3 wish-list
on 11-15-2004 1:03 AM
I would like to have the possibility of working with HTTP without asmx and IIS. It would be great to have a lightweight Http listener and use SoapService for every transport protocol using the same pattern.

I think that Http.sys, included with WinXP sp2, could be supported as this additional http listener.

I would also like to have WS-ReliableMessaging and WS-Eventing in the next version.

Regards
SOAP your mind wrote WSE wish list
on 11-15-2004 3:16 AM
Darren wrote re: My WSE3 wish-list
on 11-15-2004 5:07 AM
Better Deployment.
Requiring the WSE runtime deployment package for distribution is a deployment nightmare for us. We have been plugging the smart deployment story to our customers for over a year now as a huge selling feature, and now we have to make a decision if we can even use WSE because of its dependence on a deployment package. Let us use xcopy deployment!!!! Give us back smart deployment!!! Or put it up on Windows Update.
Dave Bettin on Services wrote My WSE 3.0 Wishlist
on 11-15-2004 9:54 AM
Andy Neilson wrote re: My WSE3 wish-list
on 11-15-2004 12:48 PM
MTOM

Ensure WSE 3.0 works with .NET Fx 2.0 sooner rather than later, even in an unsupported mode. I'd really like some current WSE to go with the Whidbey bits
Andru's WebLog wrote WSE 3.0 WishList
on 11-16-2004 5:35 AM
Erik Johnson wrote re: My WSE3 wish-list
on 11-16-2004 9:00 AM
I'm not sure if the spec is far enough along, but WS-Enumeration would actually be really helpful.
Ken Brubaker wrote Messaging teams are finally working on MTOM/XOP!
on 11-18-2004 11:34 AM
MTOM/XOP have moved to proposed recommendation status.
Martin Kulov wrote re: My WSE3 wish-list
on 11-23-2004 6:05 AM
- Easier debugging - Right now you are not able to debug the service from the client as it is was for existing web services.
- Merge modules
- Clearer error messages - now you have a generic message when something got wrong with policy enforcement
- Policy enforcement debugger (kind of)
Dennis Mulder wrote re: My WSE3 wish-list
on 12-08-2004 1:46 PM
Back to simplicity and better configuration validation (or at least better error messages).
Kirk Allen Evans' Blog wrote WSE Wish List
on 12-09-2004 8:07 AM
Paul wrote re: My WSE3 wish-list
on 01-20-2005 2:23 PM
The ability to Chunk large files in Dime Attachemnts across HTTP as well as TCP.
Jagdeep wrote re: My WSE3 wish-list
on 02-13-2005 7:38 PM
SAML 2.0 & WS-Federation.
Better exception/Fault handling.
Good policy file builder tools. Current addin cannot build complex policy files.


download wrote re: My WSE3 wish-list
on 04-06-2005 8:06 PM
Easier debugging - Right now you are not able to debug the service from the client as it is was for existing web services.
- Merge modules
- Clearer error messages - now you have a generic message when something got wrong with policy enforcement
- Policy enforcement debugger (kind of)
Pascal Mercier wrote re: My WSE3 wish-list
on 04-15-2005 11:03 PM
The native support of Secure Context Token in a web farm.
Cis wrote re: My WSE3 wish-list
on 05-02-2005 7:58 PM
AllowPartiallyTrustedCallers() ?? too much? :(
Ben wrote re: My WSE3 wish-list
on 10-13-2005 3:13 PM
SAML SAML and more SAML.
Service Station, by Aaron Skonnard wrote HTTP.SYS transport for WSE 3.0
on 10-14-2005 1:02 PM
Paul G Mazzola wrote re: My WSE3 wish-list
on 03-21-2006 3:32 PM
1 I wish my life was more easier.
2 I wish to have a girlfriend that would love me for what I'm and what I'm not.
And my therd wish is to help change people's life's.

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