Tracking change and innovation in the enterprise software development community
QCon London 2010!
March 10-12, 100
Speakers, 80 sessions,
"THE" team leads and,
architects conference.
Free Book Offer
SOA Demystified
$40 Value
Scaling Scrum
in the enterprise?
ScrumWorks Pro
can help.
Start a trial today
Posted by Stefan Tilkov on Mar 26, 2008
The latest interoperability event (a “plugfest”) at Microsoft’s Redmond campus showed impressive results for interoperability between future releases of Sun’s Metro Web Services and Windows Communication Foundation in .NET 3.5. InfoQ had a chance to talk to Harold Carr, the engineering lead for enterprise web services interoperability at Sun, about the interop results.
When asked what the relevance of this for Java and .NET developers would be, highlighted the role of interoperability in general:
Web services are about wire interoperability, not about the platform they are implemented in. Therefore, developers, whether using .NET or Java, expect their services to interoperate. It is relatively straightforward for platform developers to ensure interoperability for WS-I basic profiles. But when you add in WS-Policy, WS-Security, WS-Trust, WS-SecureConversation, WS-ReliableMessaging, etc., the bar for platform implementors gets way higher. The interop results give transparency into our current development stage to give people that are planning to use Metro with .NET 3.5 (reminder: Metro 1.0 already works with .NET 3.0) confidence that we will provide an interoperable platform (rather than a platform that has only been tested against itself).
With regards to the maturity of standards in the WS-* space, he noted:
There are two aspects to consider: the interop scenarios we test and the deployment of services based on these specs. The interop scenarios are very useful, but certainly not complete (particularly in reliable messaging). Real deployments will come up with combinations never tested (either by the interop scenarios tested at the plugfest or our more extensive in-house testing). Also, .NET 3.0 and Metro 1.0 (both released products) are based on the submission versions of the WS-* specifications (except for WS-Security, which is standard). .NET 3.5 (which is released) is based on the standard versions. Metro 1.x (which will ship later in 2008) will be based on the standard versions also. All this is a long-winded way to say the standard specs haven’t been used in many deployments based on shipping platforms from different vendors.
According to Harold, the hardest aspect to get working was security, especially using Kerberos, and including Trust:
There are so many ways to do security it takes a lot of testing. And when you have trust in the picture then you have a 3-way test: client, STS, service – so you have more combinations to test.
Check out the interop results in Harold’s blog post and take a closer look at Metro on Sun’s site.
Right Collaboration Architecture Drives Business Transformation
Understand and Align BPM, SOA, and Lean Six Sigma: 43 page IBM Redguide
Restful BPM, Pragmatic SOA, Mashups, Avoiding Failure: SOA track @ QCon London in March
Visit SOA Appliance Comparison Site
*Video Usage Model Tutorials
*Comparison to IBM DataPower X150
*Performance Benchmarks/Webinars
*Replace DataPower Program
FREE 1:1 Swap & Migration Services
I am writing a WCF & Java Interop tutorial series. The series covers different data types between Java & WCF, session management, WCF ASP.NET compatibility, SSL, Asynchronous Polling, data compression , MTOM and so on.
These articles are based on my real world development experience of SCM Anywhere (www.scmsoftwareconfigurationmanagement.com), a SCM tool with integrated version control, bug tracking and build automation.
The series has not been finished, but I am adding articles several times per week. Please check back for the latest articles.
The URL of the series is:
www.kevingao.net/wcf-java-interop
Thanks a lot.
-----------------------------------------------------------------
Kevin Gao, MCSD MCDBA
www.kevingao.net
www.dynamsoft.com
Brian Marick takes us through a quick tour of the most important values and challenges to adopting Agile successfully (they aren't the typical challenges and values we hear in the community).
The line between development and architecture is tricky. Does it exist at all? Is an ivory tower actually needed? There's a balance in the middle, but how do you move from developer to architect?
The word 'authority' sometimes produces an allergic response in hard-line agilists. Freedom and authority – both are bad if misused and both are good if used in right spirit for a noble cause.
"Getting Started with Grails" brings you up to speed on this modern web framework. Companies as varied as LinkedIn, Wired, and Taco Bell are all using Grails. Are you ready to get started as well?
Those familiar with only ITIL V2 often scoff at the thought that ITIL could serve as a governance framework for SOA. With ITIL V3, the focus of the framework shifted towards service-orientation.
SpringSource CTO Adrian Colyer discusses AspectJ, SpringSource's dm Server and tc Server products, OSGi and Scrum.
Heroku's Adam Wiggins talks about Rails, Background Jobs, Add-Ons, Ruby, and how Heroku manages to work around Ruby's inefficiencies using Erlang and other languages.
For Grady Booch the foundation of a good architecture is patterns, SOA being just one of many patterns. In this Second Life presentation, Booch attempts to bring more clarity on what architecture is.
1 comment
Watch Thread Reply