Mailing-List: contact axis-user-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-user@ws.apache.org
Received-SPF: pass (asf.osuosl.org: domain of atmanes@gmail.com designates
 64.233.184.203 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=l17fJO360eSMigN28JqpnMNds4A2gUfoKYfMzzA6TS34x8ZSRp9mjfw3FrAgAkdtM0LRKbE8CTiw9Q5eiGXgPmg8te1XO9Cz9k5JKNJqdNigwPbG9e6HxRME/g1oARDhNDXIVhnfZPF2JW5cbdo0dGbdKhsw3cfJklrTzFFjIRA=
Message-ID: <bf414ee6050802043535ecbbcd@mail.gmail.com>
Date: Tue, 2 Aug 2005 07:35:58 -0400
From: Anne Thomas Manes <atmanes@gmail.com>
Reply-To: Anne Thomas Manes <atmanes@gmail.com>
To: axis-user@ws.apache.org
Subject: Re: Axis to handle already existing WS implementation
In-Reply-To: <70A3C44F47DE2E43886510679C4A29B71DC210@internal.sagadc.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <70A3C44F47DE2E43886510679C4A29B71DC210@internal.sagadc.de>

Please explain more about your situation.=20

What do you mean by "moving to Axis"? What would you like to use Axis for?

Axis performs=20
- WSDL generation
- SOAP request/response
- Document/literal style services

So does that mean you would like to replace you current WS features with Ax=
is?
If so, you'll need to make some changes to you current web app.

Axis supports WS generation from WSDL or from Java. As a best practice
to ensure better interoperability, it's better to generate the WS from
WSDL. Capture your dynamically generated WSDLs and use them to
generate your WSs. Then replace your current WS infrastructure with
Axis, and direct Axis to invoke the appropriate application code when
requests come.

If that isn't possible, then use your current application code to
generate the WS and the WSDL.

If you asking whether you can dynamically expose web services with
Axis, I don't know if it can do that.

Anne

On 8/2/05, Saqib Rasul <saqib.rasul@sagadc.de> wrote:
> Hello all,
>=20
> We have several WS features already implemented into out Web App:
> - WSDL generation
> - SOAP Request/Response
> - Document Literal style WS and WSDLs
>=20
> Our WS and WSDLs are WS-I compliant.
>=20
> And are now thinking of moving to AXIS. From axis documentation it seems
> that axis is helpful to create Client/Server Java stubs for handling
> WSDLs. The problem that we have is out WSDLs are generated dynamically
> for an "information Container", so its useless generate Cleint/Sever
> java-stubs.
>=20
> Can someone point out some documentation on how to work with AXIS if the
> WSDLs are unknown/dynamic. In other words how can we still hook into the
> AXIS system with dynamic WSDLs?
>=20
> Many thanks in advance,
>=20
> Regards,
>=20
> Saqib
>=20
> ------------------------------------------------------------------------
> SAGA D.C. GmbH                  Phone : +49 (0) 6731-9428-0
> Berliner Strasse 73             Fax : +49 (0) 6731-9428-26
> D-55232 Alzey
> mailto:saqib.rasul@sagadc.de    http://www.sagadc.de
>=20
>