I'm curious about folks' experiences with Apache Axis.
I just created a small simple web service. One class, deployed as a .jws file, and the client just calls instance methods of the class. No session/persistence. No objects. Just remote function calls. Using Axis this way seems pretty simple.
Writing a client looks to be pretty simple too, but I haven't had to do that yet. It looks like you just:
- use the WSDL2Java program, and
- point it at your MyService.jws?wsdl
- then use the resulting classes/interfaces from your own short hand-written MyClient.java class.
(I outlined that procedure here: http://wiki.apache.org/ws/FrontPage/Axis/WritingYourClient
-- in fact, if there's any clarification you can add to that, please let me know; either here or by updating that wiki page)
Anyhow, I'm curious to hear other people's experiences with Axis. My guess is that as soon as you get off the beaten path, the trail gets rocky.
Folks on the ML talk about WSDL sometimes, but I don't understand why -- I thought the whole purpose of Axis was so that you didn't have to touch XML or WSDL anymore -- you could just do RPC and have Axis take care of the details.
No idea about UDDI. The client knows who it'll be talking to, and the web service only expects that one client to be contacting it.
At least, that's the way it is for my simple web service.
Any commentary is appreciated.
[ August 05, 2005: Message edited by: John M. Gabriele ]