Adding something like Apache Axis2 to the mix would be better, yes, agreed Kirk.
However, there is merit to avoiding middleware functional duplication as well -- beyond avoiding the coding. There is maintenance burden involved with any software, whether in-house coded or not. How much burden? It depends, but it's non-zero. So if you've got the tool in the bag already, so to speak, it may be better to use that tool. Parsimony is often a good thing. Also, it's extremely likely that Web Services enablement will get used over and over again. It is important to take steps to make this capability available in common fashion and make it well known across the development teams. Anyway, the original poster may have something already up and running that provides Web Services enablement without necessarily being aware of it. CICS Transaction Server is one example in many shops, and there are other examples. I didn't want to jump to any particular conclusion right away, and hopefully the above illustrates some of the important considerations before reaching a particular decision. - - - - - Timothy Sipples IBM Consulting Enterprise Software Architect Based in Tokyo, Serving IBM Japan / Asia-Pacific E-Mail: timothy.sipp...@us.ibm.com ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
