> At 11:20 AM 11/11/2002 +0100, niksa_os wrote: > >> 1) For what reason skeleton classes exist, I mean the ability to generate this >> classes? If I have java class I use axis and make wsdl and client stub. Why >> skeleton classes? > > You are suggesting a "dangerous" approach where you generate WSDL > from existing Java classes. Although most popular examples most
but that's exactely what tha Java2WSDL utility does. And I'm expecting it will use my original Java class as a service instead of the generated skeleton (that have the same methods...) BTW I'm using the Java2WSDL + WSDL2Java approach described in the User Guide. (do I just need to change the value of <parameter name="className" value="pkg.MyServiceSoapBindingImpl"/> in the generated wsdd file to point to my original class to bypass this problem?) > web service tools vendor gives following this pattern, this is not > the right approach. > The right approach is to start with WSDL first without worrying > about your legacy backend implementation. After that, you need an > adaptor to talk your legacy backend. The "skeleton class" serves > the role as the adaptor. -- mattia
