RE: problems in deploying existing JAVA classes using JWS

[Michael Grob]

Hi, for me it worked like this (since I'm quite new to axis, there may be better solutions):   1. The Class with the methods you'll want to have published as a web service is converted to .jws 2. If your other classes (which are used by your web service) are just .class files, put them into WEBINF/classes. If they are a .jar library, put them into WEB-INF/lib 3. When your web service class needs then, they will be loaded by the class loader, and you can use them.   At least that's how it worked for me.   Michael -----Original Message----- From: ¿ÀÀ±Á¤ [mailto:[EMAIL PROTECTED]] Sent: Freitag, 11. Oktober 2002 03:56 To: [EMAIL PROTECTED] Subject: problems in deploying existing JAVA classes using JWS Hi, all   I have been deploying existing java classes into Web services by converting them into .jws file. Do i need to convert all classes into .jws? ( One main class uses serveral imported classes) I converted the main class into .jws file only. But when soap client invokes public method in the main class I got java exception message on java.lang.IllegalAccessError: try to access method xxx, which means, i think,  that access to the methods of subclasses from the published main class is not allowed.   What shoud I do?   Thanks for help!!