You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-dev@axis.apache.org by Nadir Amra <am...@us.ibm.com> on 2005/02/15 11:30:44 UTC
Client build - which dlls/libraries are needed?
I downloaded the latest source and built the client piece, and I see the
following shared libraries:
libaxis_client.so
libaxis_clientC.so
libaxis_xml4c.so
libaxis2_transport.so
libhttp_channel.so
libhttp_transport.so
My question is whether libaxis2_transport.so is needed? And if not, why
is it being built?
Re: Client build - which dlls/libraries are needed?
Posted by Roshan Weerasuriya <ro...@opensource.lk>.
hi Nadir,
If you use:
- the Axis3 transport you need libhttp_transport.so and
libhttp_channel.so
- the Axis2 transport you need the libaxis2_transport.so
I think still it builds both Axis2 and Axis3 transports.
Roshan
On Tue, 2005-02-15 at 04:30 -0600, Nadir Amra wrote:
> I downloaded the latest source and built the client piece, and I see the
> following shared libraries:
>
> libaxis_client.so
> libaxis_clientC.so
> libaxis_xml4c.so
> libaxis2_transport.so
> libhttp_channel.so
> libhttp_transport.so
>
> My question is whether libaxis2_transport.so is needed? And if not, why
> is it being built?
>
>
>
Re: Client build - which dlls/libraries are needed?
Posted by Samisa Abeysinghe <sa...@gmail.com>.
+1 for moving axis2 as axis3 is quite stable.
Regards,
Samisa...
On Tue, 15 Feb 2005 10:45:40 +0000, John Hawkins <HA...@uk.ibm.com> wrote:
>
> You're right! They shouldn't be there - we said that axis3 was the default
> for 1.5 onwards.
>
> I think we should tidy up the build and move these old transports to
> graveyard - any one any objections?
>
>
>
>
> Nadir Amra <am...@us.ibm.com>
>
> 15/02/2005 10:30
> Please respond to
> "Apache AXIS C Developers List"
> To"Apache AXIS C Developers List" <ax...@ws.apache.org>
> cc
> SubjectClient build - which dlls/libraries are needed?
>
>
>
>
>
>
>
>
> I downloaded the latest source and built the client piece, and I see the
> following shared libraries:
>
> libaxis_client.so
> libaxis_clientC.so
> libaxis_xml4c.so
> libaxis2_transport.so
> libhttp_channel.so
> libhttp_transport.so
>
> My question is whether libaxis2_transport.so is needed? And if not, why
> is it being built?
>
>
>
>
Re: Client build - which dlls/libraries are needed?
Posted by John Hawkins <HA...@uk.ibm.com>.
You're right! They shouldn't be there - we said that axis3 was the default
for 1.5 onwards.
I think we should tidy up the build and move these old transports to
graveyard - any one any objections?
Nadir Amra <am...@us.ibm.com>
15/02/2005 10:30
Please respond to
"Apache AXIS C Developers List"
To
"Apache AXIS C Developers List" <ax...@ws.apache.org>
cc
Subject
Client build - which dlls/libraries are needed?
I downloaded the latest source and built the client piece, and I see the
following shared libraries:
libaxis_client.so
libaxis_clientC.so
libaxis_xml4c.so
libaxis2_transport.so
libhttp_channel.so
libhttp_transport.so
My question is whether libaxis2_transport.so is needed? And if not, why
is it being built?