aspose file tools*
The moose likes Web Services and the fly likes WebService Problem Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Java » Web Services
Bookmark "WebService Problem" Watch "WebService Problem" New topic
Author

WebService Problem

imran mansuri
Greenhorn

Joined: Oct 18, 2003
Posts: 5
Hi,


I have a webservice which is lying in one package in one application. It is using applications other classes which are lying in other package. Now I have created webservice by using only the package in which the webservice classes are stored.

After I have created the webservice when i call it from client it can not access the application (in which webservice created) classes used in Webservice untill I create a jar file of application's other classes and put it in AXIS folder(As I am using AXIS for Webservice deployment and access). I tried to put the applicatin in classpath of the AXIS but it does not work.

Can Any one help me in fixing this problem as I dont want to keep 2 copies of the application one in AXIS and other in Tomcat/webapps/.

Thank You.
Jim Yingst
Wanderer
Sheriff

Joined: Jan 30, 2000
Posts: 18671
I think this will fit better (and be more likely to get an answer) in our Web Services forum, so I'm moving it there.


"I'm not back." - Bill Harding, Twister
Ulf Dittmer
Marshal

Joined: Mar 22, 2005
Posts: 41524
    
  53
You could move the Axis servlet, and the jar files it needs, into your web app, instead of keeping it in a web app all by itself. That way you have only a single web app, and no need to duplicate classes.


Ping & DNS - my free Android networking tools app
raju parepally parepally
Greenhorn

Joined: Mar 01, 2006
Posts: 14
hai,
copy axis folder in tomcat/webapps and create jws file in axis and call that jws file from other application by placing related jar files in lib folder

regards
nagaraju
Ulf Dittmer
Marshal

Joined: Mar 22, 2005
Posts: 41524
    
  53
... keeping in mind that .jws-based web services have a number of drawbacks, which make them unsuitable for production-quality purposes.
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: WebService Problem