ssage-
From: Keith Hatton [mailto:[EMAIL PROTECTED]
Sent: Friday, July 09, 2004 5:00 AM
To: [EMAIL PROTECTED]
Subject: RE: Deployment Question
Hi,
Axis should only require the classes that an RMI client for your EJBs
would also require, i.e. the home and remote interfaces of your EJBs and
any
on servers (what
server are you using?)
Hope this helps,
Keith
-Original Message-
From: Sagar Pidaparthi [mailto:[EMAIL PROTECTED]
Sent: 08 July 2004 16:28
To: [EMAIL PROTECTED]
Subject: RE: Deployment Question
Hi,
I am not sure if the answer below solves the problem. Correct me if I
am
PROTECTED]
Sent: Wednesday, July 07, 2004 6:57 PM
To: [EMAIL PROTECTED]
Subject: RE: Deployment Question
You can include the axis jar files in your application and add the
sections
from the axis web.xml file to enable the bindings for the AxisServlet.
Then axis will have access to the classes
TECTED]
> Sent: Thursday, 8 July 2004 5:25 AM
> To: [EMAIL PROTECTED]
> Subject: Deployment Question
>
> Hi-
>
> It seems the standard way to install a web service with axis
> is to install
> my .jars into axis/WEB-INF/lib, and then deploy via the axis
> admin se
Hi-
It seems the standard way to install a web service with axis is to install
my .jars into axis/WEB-INF/lib, and then deploy via the axis admin servlet
and a custom wsdd file, with ant tasks.
But.. I have an application where the web service interface is only a small
part of the total functiona
In reading the samples that come with Axis, it isn't clear to me whether
I need a deploy.wsdd for an application, and if I didn't use one, how I
would structure an endpoint and OperationName.
Suppose I have:
WEB-INF
classes
myPackage
myClass
lib
(axis
