Mailing-List: contact axis-user-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-user@xml.apache.org
Importance: Normal
Sensitivity: 
Subject: Re: Incorporate the AXIS into my web app.
To: axis-user@xml.apache.org
Message-ID: <OFA510AA47.B002766C-ON85256C85.006AC28C@us.ibm.com>
From: Doug Davis <dug@us.ibm.com>
Date: Wed, 4 Dec 2002 14:26:20 -0500
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII


Axis supports a "java" binding natively so no http will be involved.
-Dug


"Steve Parker" <steve@naweb.com> on 12/04/2002 02:23:52 PM

Please respond to axis-user@xml.apache.org

To:    axis-user@xml.apache.org, axis-user@xml.apache.org
cc:
Subject:    Re: Incorporate the AXIS into my web app.


Look at also using WSIF (Web Services Invocation Framework).  It will allow
a
dynamic binding to occur - so your calls will go over SOAP (Axis) when
needed, and locally when that is all that is needed.

On Wed, 4 Dec 2002 19:19:14 +0100, Alex Dovlecel wrote
> hello all,
>
> I know this subject was debated some days ago. I have tried to
> follow the thread and was pretty interesting. But I haven't found
> anything about this:
>
> My web app (that will incorporate the axis), when calling an axis
> server, should not encode the call in an axis envelope and send it
> to localhost but just to call the method. Or somehow to invoke the
> chain that leads to the required method. How can I achieve this?
>
> REason: will be quite a performance drawback to marshall the params
> in xml format, then unmarshall them on the same application!!! It is
> senseless!!! Like calling a local method using RMI !!!
>
> So could I get any hints on this one?
>
> Tx
> dovle