This white paper takes an in-depth look at various open-source tools that can be used to get started on Web services development. It walks you through the development lifecycle of how an existing Java asset is exposed as a Web service interface using Eclipse for development, Apache Axis and Tomcat for creation of the WS, Ant for deployment and PushToTest for testing.
- Posted by: Nate Borg
- Posted on: June 23 2003 23:13 EDT
Read Leveraging Open Source for Web services development
- Pushtotest site (temporarily?) unavailable by charles arehart on June 24 2003 12:16 EDT
- White Paper: Leveraging Open Source for Web Services Development by Jason McKerr on June 24 2003 12:36 EDT
- The White Paper is the state of the art by Frank Cohen on June 25 2003 01:59 EDT
- Well done by Pieter Smit on June 26 2003 03:45 EDT
- URL still bad by null on June 30 2003 22:28 EDT
- Embedded screenshots unreadable by Grant Smith on July 01 2003 12:39 EDT
The article points the reader to http://www.pushtotest.com, yet when visiting just now, all it offered was this:
Welcome to fries.pushtotest.com. This domain is
supported by info at pushtotest dot com.
Must be a temporary problem. The site has existed before, and indeed a snapshot of its former appearance can be viewed via Google's cache at:
It's also responding ok to the slightly modified URL http://www.pushtotest.com/ptt/, as well as any others other than the default page.
I can download it.
So I'm feeling more than a little stupid right now. I was updating the PushToTest Web site this morning and replaced the index.html file that redirects from www.pushtotest.com into our publishing engine (Zope) at http://www.pushtotest.com/ptt. Nothing like eating some humble pie every once in a while. Anyway it's fixed and I'm sorry about that.
All I'm getting is a blank PDF file.
I've tested from a few different computers and they all work (the download).
I could download the PDF. it works okay.
Can't download either - running IE 6.0...
My hat is off to the great work by Chris Peltz and Claire Rogers at HP. As the principal maintainer for TestMaker, one of the open-source tools they mention in the white paper, I speak with dozens of software developers everyday. From my experience, Chris and Claire's white paper describes the state-of-the-art in Web Service development.
I owe further credit to Chris and Claire. Their white paper discusses implementing a Web Service that uses a complex data type. Chris and Claire asked me for help to configure TestMaker to work with complex data types. I wrote about my experience for IBM developerWorks. The complete artice and sample code are at: http://www-106.ibm.com/developerworks/webservices/library/ws-complex.html.
It will be interesting to see how Web Services mature in the coming year. There are big efforts underway to add security and orchestration to Web Services. And there are bound to be lots of articles for The Server Side to write to show J2EE developers why they should care. :-)
I have enjoyed reading this paper too but I have some comments on the state of the art whatever it means.
1. Eclipse now comes with an Ant editor that i believe is based on Planty, so you do not need to download Planty
2. Eclipse now comes with an Ant View to run turgets.
3. Axis now comes with SoapMonitor aplet that does not require you to change port and run tcpmon as a standalone program, the tradeoff is that you will see only Soap parts of HTTP messages and could not modify and resend messages; also you need to do some configuration.
4. With tcpmon you need to modify port and I believe that it is much easier to use property in ant build.xml then in .java file
The paper said that it was originally published in May and the real work probably has been done couple of month ago or maybe more, tools get better pretty fast.
I think both articles missed a couple of really important points when using Axis:
1) You didn't really discuss Serialization/Deserialization and the factories that can be used with Axis. They only briefly touch on this when they get an error. This stuff is critical to using Axis well, and can be VERY confusing. A white paper on this subject should really touch on this. I think it would be invaluable to future Axis users.
So while you covered it in brief, I think they missed a lot on this issue beacuse serialization/deserialization of more complete object graphs is both important and can be confusing.
2) You didn't discuss at all a more document centric approach to using Axis.
Also, question: Why did they use typeMapping instead of beanMapping for the first service? The typeMapping uses the same bean serializer/deserializer factories and encoding by default. Was it just to show how to register a serializer with the typeMapping in case people want to register their own?
These may sound like nit-picky things, but they aren't. These are big issues that I've found pop-up a lot in Web-Services, especially Axis.
Otherwise, I agree. Excellent paper! I will also have to try the PushToTest. I've been using JUnit/JUnitEE for testing web-services, which means I do a lot of hand-coding the SOAP/WS client calls. PushToTest looks cool.
Maybe you could add some info for the next revision on these two topics, and describe beanmappings/typemappings a bit more. I'd be happy to send you some good samples of moving Java paradigms to a more document centric approach and on using the serializers/deserializers effectively (I really found that to be THE most confusing construct in Axis, just because I didn't know the classes existed, and the documentation isn't very good).
Northwest Alliance for Computational Science and Engineering
I really enjoyed reading this article. There are so many technologies to choose from today that it is hard to evaluate all of them. This article gave me a glimpse of open source web services without a serious time commitment. It was technical enough without drilling too deep into unnecessary code. I would love more of this type of overviews in the open source arena.
I still _cannot_ download the PDF -- I get simply a blank page. Here's the URL:
-- Paul Bain
I was finally able to download the PDF, but only on the _third_ attempt.
Even though I found the article extremely useful and insightful, the screenshots were completely useless to me. When embedding screenshots into PDF files, make sure the resolution is such that the resulting image can be reproduced.