|
You know the saying... "when Pigs Fly..."? Well, Clemen's Latest note starts: A flock of pigs has been doing aerobatics high up over Microsoft Campus in Redmond What he is referring is that he just checked in GlassFish and Metro into the latest Biztalk SDK! Neat! And he has some very nice words for the Metro team, as Arun highlights. |
On the other side of the Atlantic, Alexis highlights another Microsofter, Stéphane, on another aspect of the same relationship: GF and NetBeans being available at Microsoft Technology Centers.
I think we may have a new mascot - the flying pig!
|
The latest stable version of Metro (which ships as part of GlassFish v2) has been extensively tested with Microsoft's WCF (Windows Communication Foundation) version 3.0. The next version of .Net 3.5 is already out and the team is working hard to achieve the best possible interoperability with this new set of WS-* implementations. |
Harold and Rama report on the most recent "plugfest" with Microsoft engineers. The work involves moving from some non-standard technologies (such as WS-ReliableMessaging 1.0 which is "just" a specification, not an open standard) to the OASIS version (OASIS WS-RM 1.1, dated July 2007) for better interoperability. The set of test scenarios is comprehensive and results very promising.
Check out Metro's roadmap here for an idea of when to expect stable releases. In the mean time, you can get the nightly builds.
|
One of the components in GlassFish v2 getting great attention from both developers and architects is the Metro Web Services stack and the Microsoft interoperability it enables, specifically with .Net's 3.0 WCF. With Microsoft moving ahead to .Net 3.5, Metro is also evolving to make sure the interoperability remains first class. Harold is reporting from the recent plugfest with Microsoft engineers testing the interop level of standard versions of existing Web Services specifications. One such new standard is OASIS WS-ReliableMessaging 1.1 (vs. version 1.0 included in Metro 1.0). Obviously, there are also several security-related standards implementations being tested as explained by Jiandong. |
The results are quite encouraging and the Metro version interoperable with .Net 3.5 is scheduled for 2008.
Update: Geertjan has an interview with Harold on this very same topic.
|
One of the key benefits of Metro, the Web services stack in GlassFish, is basic Web services interoperability provided by JAX-WS RI and .NET 3.0 interoperability by Project Tango. Greek School Network is using it successfully with NuSOAP as well. Metro was chosen over Apache Axis and several other candidates. For the Java WS framework there were several candidates like Apache Axis and JAX-RPC but we choose JAX-WS 2.1, both because of its elegant programming model and the fact that in the newly published Java EE 6 proposal JAX-RPC will be proposed for future deprecation. |
And the NetBeans Web services wizard is found to be very useful as well:
Our development platform was NetBeans 5.5 which provided a powerful wizard that starting from the WSDL that NuSOAP published, created the necessary Java stub code for our operations.
A variety of screencasts showing develop/deploy/invoke cycle of Web services using Metro and NetBeans are available here.
|
Metro, the Web services stack in GlassFish V2, participated in the fourth Microsoft Interoperability Plugfest. Read Harold's report for more details. Metro is already interoperable with .NET 3.0 and Microsoft is working on .NET 3.5 framework. This plugfest participation was to ensure that there are no regressions when a Metro 1.0 client try to invoke a .NET 3.0 endpoint deployed using .NET 3.5 runtime and vice versa. |
We have already done extensive testing between Metro 1.0 and .NET 3.0. The next version of Metro will align with the specifications used in .NET 3.5.
You may also want to read about our participation in first, second, and third plugfest.
|
Next Tuesday, July 17th, there will be a Sun Expert Exchange on Sun - Microsoft Interoperability. Topics will cover our own Project Tango but also topics like running Windows on Sun servers, thin clients, and storage. Expert Exchange events are free online sessions with a panel of experts. Sometimes there are also short video Net Talks. Transcriptions and slides of past events are available. |
Thanks to Marina for the tip.
GlassFish: del.icio.us/tag/glassfish
Java
opensource
webservices
glassfish
interoperability
system:has:for
|
Microsoft has announced a new Web Services Interoperability Plugfest, and Sun will participate using Project Tango, a key component of Metro - the Web services stack in GlassFish V2. Project Tango's focus is interoperability with .NET 3.0 and that will be unchanged until GlassFish V2 is released later this year. This plugfest will give us an opportunity for regression testing with Microsoft's upcoming .NET 3.5 framework as well. Relationship building will continue to be a key part of this visit. The interop scenarios from the plugfest are run regularly and the results with Tango Milestone 5 (integrated in GlassFish V2 b50) demonstrate that. |
GlassFish: del.icio.us/tag/glassfish
webservices
glassfish
transactions
interoperability
WSIT
_done
The WSIT group in the GlassFish community recently released Milestone 3 of WSIT (nee Tango). WSIT builds on the core JAX-WS RI implementation and you can Download and Install them manually, but you can also wait until Monday for GF v2 beta, which will include these technologies directly. Relevant blogs from the team include:
|
• Harold provides the
Announcement.
|
|
Rima and Arun both have recently published nice overview blogs on how to do Web Services Interoperability between GlassFish and Vista (MS home, Wikipedia) using the WSIT technologies. These technologies are developed in the GlassFish community and build on the new WebServices stack. The stack is included in GlassFish v2 although it can be used (with some limitations) in other containers. |
Rima's blog starts by describing exactly what versions to download, then she provides simple Java and C# programs that do simple interoperability; check her blog. Arun's blog follows a similar approach, except that he has been building up a series of Screencasts and blogs where he is trying to cover quite extensively all the functionality.
The next WSIT milestone should be out within the next couple of days; I know the WSIT team is working on a number of blogs covering all the the new functionality. We will report more then.
Added: WSIT M3 is out now; I'll put together a master index for the blogs in a future entry.
|
The WSIT technologies (bundled in GlassFish and also available separately) support Web Services interoperation between the Java and the Windows Communication Framework. The practical interoperability depends on the features and limitations of the platform-specific XML Schema data binding mechanisms and the new WSIT tutorial (PDF) provides specific guidelines for best practices. Check them out and provide feedback to Sekhar and the team. Shown at left is the front cover of my favorite set of guidelines for english writers: The Elements of Style (aka Strunk and White). Easy to summarize 'Omit needless words', but very hard to follow. |
webservices
xsd
glassfish
jax-ws
Guidelines
interoperability
WSIT
GlassFish: del.icio.us/tag/glassfish
webservices
glassfish
Tango
interoperability
ws-trust
_notpublished
GlassFish: del.icio.us/tag/glassfish
Windows
webservices
JaxB
xsd
glassfish
Tango
interoperability
|
The SD Times has a very complimentary article about the WSIT technologies (codenamed Project Tango) that are in GlassFish and provide interoperability with the Web Services features from Microsoft, including those in Microsoft's Vista. The article quotes from an interview with Nick |
|
|
Alexis has been working on Sun's submision to PRESTO, a Web Services interoperability profile defined by the French goverment. The submision was based on GlassFish v2 using the WSIT technology; an overview is here. |
Overall, the effort is similar to the recent PlugFests we have been attending. Both Sun and Microsoft participated, as well as some additional projects. The effort was very succesful; check out Alexis' blog entry for plenty of details.