Arun Gupta, Miles to go ...

Another Web services stack comparison

Another Web services stack comparison at JBoss wiki and GlassFish is looking really good. Read more details about the feature support here.

Technorati: Web Services GlassFish WSIT JBoss J2EE

Posted by Arun Gupta in webservices  |  Comments[1]

Silicon Valley Marathon 2006 Training Calendar

I'm recovering well after the marathon. My complete training calendar is below. I'll be happy to take any advise on altering my schedule to accommodate a faster pace for the next race.

Technorati: Running Training Marathon svmarathon

Posted by Arun Gupta in Running  |  Comments[0]

Marathon and GlassFish Community

As I mentioned earlier, running a marathon is all about community. So I decided to show my support for GlassFish community by hand painting my running shirt on the day before marathon. My dad helped me trace it and then I painted it. Learn more about GlassFish and it's community. Get Started, Get Involved and participate in the Roadmap discussion. Read about community awards given for participation in GlassFish community. And you can read about some great testimonials, again from the community, here. Oracle, BEA, JBoss, SAP and Tmax Soft are partners fostering the community spirit. Also read about how GlassFish works with a host of application frameworks, applications, tools etc. available in the community. Check the complete flickr slideshow of me wearing this tee-shirt.

Posted by Arun Gupta in General  |  Comments[0]

Completed my first marathon

4 hours, 6 minutes, 57 seconds and a pace of 9:25/mile.

This is what it took me finish the Metro Silicon Valley marathon, my first one. Almost 7 minutes behind my targeted goal but a PR. A hamstring pull on mile 18 & 23 completely slowed me down.  The complete results are available here. I read somewhere "After running a marathon, the only thing that does not hurt is your pride" and I fully realized that yesterday. The fastest male was 2:42:40 and the female was 3:07:25.

This was not possible without all the wishes from family and friends. Especially Sanjay, Satish, Dhiru and kids Ankit, Shubhankar, Vaibhav, Varun and Prateek who all ran along the last mile with me and those who could not support me as front runners. And of course the faithful and constant support of my wife and son for the 5 months of practice. I'm here because of this support system and now it's time to payback morning time to family (which I've not been able to do recently because of early morning runs),  for at least next few weeks until I begin my training again for the next marathon.

Watch a 23 second video clip of run with them here. The kids were really enthusiastic and enjoyed running along. Check out the flickr slideshow.

Although there were volunteers scattered through out the trail but the race manifested into normal trail running at several places. At quite a few places there were more bikers and dogs and no spectators making you feel lonely on the track. I was also disappointed that there was no coverage in print edition San Jose Mercury News this morning but here is an online version.

I learnt the following lessons from the race:

• Practice more hill runs as the hillocks towards the end were hitting hard
• More cross-training to develop over-all body strength
• Not sure, but loose some more weight to keep chugging along towards the end

Over all, I'm happy with my performance and learned lessons to improve upon next time.

Posted by Arun Gupta in Running  |  Comments[2]

Marathon and Community

I got the first feel of fellow runners marathon this morning when I was at Stanford University School of Medicine Hospital helping Dr. Suzanne Miller in a study on "The Effect of Endurance Exercise on the Cardiac Function of Recreational versus Professional Athletes". Read more about the study here. In approx an hour at the hospital, the following tests were conducted:

• Spoonful blood sample
• Height/Weigth/BMI
• Electrocardiogram
• Heart rate variability
• Heart Echocardiogram

The results of the study will be published in a medical journal and the results of personal heart tests (claimed to be worth thousand of dollars) will be made available.

"It's all about Community" said the Director of marathon on the radio yesterday. 3500 registered runners from all over the country, 800 marathoners, The Health Trust, Hilton, NBC 11, ASHA, KLIV and a multitude of sponsors and charities shows community involvement. 

My next blog will be after the run and will talk more about community.

Posted by Arun Gupta in Running  |  Comments[1]

Why WS-Addressing ?

I've been asked this question multiple times and so finally decided to convert an internal presentation that into an external document.

Why WS-Addressing ? describes the different use cases served by WS-Addressing and explains the two commonly used versions.

JAX-WS 2.1 RI EA2 was recently released and supports W3C and Member Submission WS-Addressing. A more recent version of this RI is integrated in WSIT which is then integrated in GlassFish 2 days ago. Read about WS-Addressing support in JAX-WS 2.1 RI here.

Posted by Arun Gupta in webservices  |  Comments[0]

Running first marathon this weekend

• 21 weeks of training
• Approx 640 miles of practice runs
• Average pace of 8:35

After all this, I'm in the last week of taper down and now ready for my first marathon on the coming weekend (10/29 to be precise). Reading this article (Marathon Smarts on Runners World) has an all together different meaning now. This article gives race day tips from experienced marathoners. Most of the tips would seem natural but it's definitely worth reading again during the last days of training.

For family and friends, and anybody else interested in running along last miles:

The race course and the viewing map is here. The map gives the complete route and lookout areas.

The race starts at 7am PT. This is also the day when daylight saving ends, so the clocks move back by an hour. Going by the experience of my long practice runs, and if I don't hit a wall, I plan to cross mile 20 around 10am and hopefully the finish the marathon in less than 4 hours (9:10 pace). My longest practice run has been 22 miles with a 9:25 pace but I've done slightly shorter runs with better pace. So this seems like a stretch goal but I hope to meet this goal with your wishes.

If you plan to run last miles with me, as some of you have told, you are most welcome. I may offload my sweat shirt to you if I'm feeling hot or may ask for an additional sip of water, so be prepared The weekend weather looks reasonable and I hope it's an overcast for the first few miles.

You can read about my marathon practice and running related blogs here.

Posted by Arun Gupta in Running  |  Comments[8]

JAX-WS 2.1 EA2 and WS-Addressing

JAX-WS 2.1 EA2, with new features and better quality, is out. Read Vivek's message about the announcement and the list of features.

I'd like to highlight Users Guide that has been updated with an explanation for all the newly added features. I added a new section on WS-Addressing support in the RI. Rama published a blog on Support for WS-Addressing in JAX-WS 2.1 RI EA1 4 weeks ago. Based upon internal and external feedback, we've simplified the way WS-Addressing support is enabled starting from Java. This blog highlights those changes and provides a quick overview of the new WS-Addressing features.

1. Enabling WS-Addressing

The code to enable WS-Addressing in EA1 (given below):

@javax.jws.WebService
@BindingType(features={@Feature(AddressingFeature.ID)})
public class MyWebService { ... }

is now replaced with the following code in EA2:

@javax.jws.WebService
@javax.xml.ws.soap.Addressing
public class MyWebService { ... }

Similarly, specifying parameters to WS-Addressing feature is simplified. The code to enable WS-Addressing with required parameter true value in EA1 (given below):

@javax.jws.WebService
@BindingType(features={
                       @Feature(value=AddressingFeature.ID,
                                parameters={
                                            @FeatureParameter(name=AddressingFeature.IS_REQUIRED, value="true"
                                           }
                                )
                      }
             )
public class MyWebService { ... }

is now replaced with the following code in EA2:

@javax.jws.WebService
@javax.xml.ws.soap.Addressing(enabled=true, required=true)
public class MyWebService { ... }

2. Explicit enabling/disabling

WS-Addressing can be explicitly enabled or disabled on the client irrespective of what the service endpoint WSDL advertises. The use case is when the client does WS-Addressing processing in the Dispatch client or via handlers. Another use case is when the client need to perform non-anonymous ReplyTo/FaultTo processing.

3. Support for wsaw:Anonymous  

W3C WS-Addressing WSDL Binding defines wsaw:Anonymous element to define assertions regarding a requirement or a constraint in the use of anonymous URI in EPRs sent to the endpoint. The syntax and semantics defined by the spec are now supported from both the client- and server-side.

This JAX-WS 2.1 EA2 is tested with GlassFish v2 b22. A more recent build is already integrated in WSIT and will soon be integrated in GlassFish. 

Posted by Arun Gupta in webservices  |  Comments[1]

JAX-WS 2.1, WS-Addressing, WSIT and GlassFish

JAX-WS 2.1 RI replaced JAX-WS 2.0.1 and JAX-WSA 1.0 EA2 in WSIT approximately 2 weeks ago. This is where I've been spending most of my time during the past few weeks. With this change, WSIT is now using WS-Addressing functionality natively provided in JAX-WS 2.1 RI is used instead of relying upon a pluggable JAX-WSA 1.0 EA2. This approach has several benefits as outlined earlier. A complete description of JAX-WS roadmap will help you understand the difference between the different version numbers.

Starting with GlassFish b22, this version of WSIT is also integrated in GlassFish. So, if you download GlassFish you get WSIT, JAX-WS 2.1 and all other great stuff. This is the very first integration of JAX-WS 2.1 RI in GlassFish and most of the functionality is working. I encourage you to download GlassFish b22 and give us feedback on how we can make it better for you.

Technorati: Web Services GlassFish WSIT WS-Addressing JAX-WSA

Posted by Arun Gupta in webservices  |  Comments[0]

Interop Plugfest: Behind the curtains

Read Jorgen's interview on The Server Side about how the Interop plugfests at Microsoft are arranged. There is full section talking about WSIT and WCF interoperability towards the end of the interview. As mentioned in my previous plugfest reports (1, 2, 3), we have incrementally achieved a very good level of interoperability with Microsoft. And this is also evident (Green and Yellow is good) in the slide used at Microsoft tracking WS-* adoption in the industry.

WSIT technologies are available in GlassFish.

Technorati: Web Services GlassFish WSIT WCF

Posted by Arun Gupta in webservices  |  Comments[0]

Web Services Stack Comparison

Dims asked me to update the Web Services Stack matrix. I've worked in the Web services team at Sun since very beginning and have seen it growing to #1 toolkit and now supported natively in GlassFish. I was therefore tempted by the invitation and updated the matrix with GlassFish entries. Here are the key points I'd like to highlight:

1. Most of the functionality in this matrix (for example JAX-WS 2.0 and JAXB 2.0) is available as part of Java SE 6.
2. If you download the latest GlassFish v2 build, all the WS-* components, exception WS-Atomic Transaction and WS-Coordination (coming soon), are integrated. WSDL 1.1 has always been part of JAX-WS and WS-Addressing is now part of JAX-WS 2.1. All other supported WS-* components are developed on WSIT and very well tested to interoperate with Microsoft's .NET 3.0 runtime.
3. Read about JMS transport support at jms-ws-transport.dev.java.net and TCP support here.
4. Spring framework is supported in GlassFish as pointed out by Jerome. But the "Spring support" feature here means exposing Spring objects as Web services in GlassFish. Let me know if you are aware of any such effort and I'll be happy to update the matrix.

Posted by Arun Gupta in webservices  |  Comments[1]

Tapering down before the marathon

With a slow pace of 9:25 for 22 miles the weekend before, and a better pace of 8:51 for 21 miles last weekend, my final push for marathon training is over. Now I'm tapering down and waiting for the days to pass. I might do few tempo runs and uphill but other than that I can afford to be lazy in the mornings

Here are some good articles on why and how to taper.

• Tapering for Marathon
• Why should you taper for a marathon ?
• What is Tapering ?

Technorati: Running Marathon Fitness SiliconValleyMarathon

Posted by Arun Gupta in Running  |  Comments[0]

WSIT and WCF Plugfest

"I" in WSIT stands for Interoperability. To ensure WSIT is interoperable with .NET 3.0, WSIT engineers made a third visit to Microsoft headquarters in less than a year. Microsoft hosted the third plugfest at their campus and Sun Microsystems showed up to test WSIT and GlassFish interoperability with their upcoming .NET 3.0 stack.

Harold, Mike, Jiandong, Joe, Ken and myself (all from Sun) "wsited" Microsoft last week. We were just representations of the bigger team and effort scattered all over the globe (Santa Clara, Burlington, Salt Lake City, Portland, Prague, Germany, France, Bangalore). And then there were some engineers doing remote testing as well.

As mentioned earlier, WS-Addressing functionality in JAX-WSA is cleaned up and now an integral part of  JAX-WS 2.1 RI. That has been my focus for the past few weeks. So in this plug-fest, I took our JAX-WS 2.1 RI for interop on WS-Addressing test cases. Microsoft has caused a few interop problems with WS-Addressing in the past (Member Submission policy assertion namespace change, incorrect Action from WCF client, WS-Addressing WSDL namespace change). But this time everything worked, it just worked. And that's what is out-of-the-box interoperability.

Other than that, we had a good success rate doing interop on WS-Atomic Transactions, WS-Reliable Messaging, WS-Secure Conversation, WSS 1.0 and 1.1, WS-Trust. We achieved interop on composite scenarios like Secure Reliable Messaging and Secure MTOM. And this interop is two-way meaning that WCF client invoke WSIT endpoint and WSIT client invoke WCF endpoint.

We care about "I", the most, in WSIT. GlassFish v2 now integrates WSIT bits on a regular basis. When GlassFish v2 goes final, be assured it will be interoperable with .NET 3.0 framework shipping in Windows Vista and other platforms.

Read about our success stories from first and second plugfests.

Posted by Arun Gupta in webservices  |  Comments[3]

WS-Addressing Member Submission Policy Assertion Namespace Change in WCF

WCF RC1 (probably in Jul CTP as well) changed the policy assertion namespace URI to declare the usage of Member Submission WS-Addressing. The namespace was changed from:

http://schemas.xmlsoap.org/ws/2004/09/policy/addressing

to

http://schemas.xmlsoap.org/ws/2004/08/addressing/policy

Thus any WSDL published by a WCF-based service endpoint using Member Submission WS-Addressing cannot be imported by WSIT clients directly. We will provide a fix in the days to come.

But in order to fix the problem, in the meanwhile, when importing such a WSDL using wsimport, you need to localize the WCF-generated WSDL, change the namespace to the original namespace (ending in 2004/09/policy/addressing) and then import it using wsimport.

Similarly, any WSDL published by a WSIT-based endpoint cannot be imported by svcutil directly. The temporary fix involves localizing the WSIT-generated WSDL, changing the namespace as it is recognized by their tools (ending in 2004/08/addressing/policy) and then importing it using their tool.

Posted by Arun Gupta in webservices  |  Comments[1]