I think you're right about server-config.wsdd, but you don't need to
deploy the Axis webapp at all.  If you put server-config.wsdd in your
app's web-inf and the Axis libraries in the classpath, and map your
service url to Axis, this should be sufficient.


-----Original Message-----
From: James Carman [mailto:[EMAIL PROTECTED]] 
Sent: Friday, January 03, 2003 6:13 AM
To: [EMAIL PROTECTED]
Subject: Re: Packaging Axis...

I don't think the server-config.wsdd file goes across contexts.  From
what I
understand, it is used to initialize the webapp that it lives in.  For
example, I have the Axis webapp deployed in the same instance of Tomcat
that
I have my custom webapp.  But, the two different webapps show completely
different web services deployments.


----- Original Message -----
From: "Joe Hanink" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, January 02, 2003 4:42 PM
Subject: RE: Packaging Axis...


I just started using Axis and had some difficulty with
server-config.wsdd at first.

Being the server config file, there should be only one.  Chances are,
you packaged up the axis context, which has /WEB-INF/server-config.wsdd
that's pre-empting the one you want designated (see server.xml to see if
this is the case)

So, this might be a context-related problem.  If you're loading multiple
contexts, make sure the one with the wsdd you want to use is being
loaded first.

If you want to call the service from the axis context,
http://somehost/axis/services/MyService?wsdl, then you'll need to load
the axis context (see server.xml)

If you want to call the service from your custom web app context,
http://somehost/yourContextPattern/services/MyService?wsdl, don't load
the axis context.

Joe Hanink

-----Original Message-----
From: James Carman [mailto:[EMAIL PROTECTED]]
Sent: Thursday, January 02, 2003 11:08 AM
To: [EMAIL PROTECTED]
Subject: Packaging Axis...

I would like to package the AxisServlet in my webapp along with other
pieces
of my distributed application (Java WebStart servlet, etc.).  How do I
"war
up" my files so that when I place my WAR file in the webapps directory
of a
server, it will already have my service deployed?  I've tried supplying
my
own /WEB-INF/server-config.wsdd file containing only my service, but
that
didn't seem to work.  When I tried to view the WSDL file, it returned a
404
error.  I don't want to have to run the AdminClient.  I want this thing
to
work "out of the box."  Any thoughts/ideas?

James Carman, President
Carman Consulting, Inc.
1218 Bob White Ct.
Edgewood, KY 41018
(513) 325-7977



Reply via email to