Hi Deepal,
For our project, we need an option allowing the set the classloader to look
for the libs in the aar files first rather than in web-inf/lib.
Currently, if a WS in the AAR needs a lib and this one is in WEB-INF/lib AND
in the AAR, the one in WEB-INF/lib is picked up, so this lib can't fin
Hi all,
Is this bug already fixed in the latest nightly or is it still applicable?
Thanks in advance,
Pierre
Deepal Jayasinghe-2 wrote:
>
> [EMAIL PROTECTED] wrote:
>>
>> Hi all Axis2 users,
>> I have a question about classloading in Axis2:
>> If I have a JAR in WEB-INF/lib folder of the WAR
Hello,
I've created JIRA 3274 : https://issues.apache.org/jira/browse/AXIS2-3274 on
the logging issue
Thanks for the reply
Pierre
Sanka Samaranayke wrote:
>
> FFF7878 wrote:
>> Hello everybody,
>> I had two problems with Axis2 1.3:
>> 1) commons-logging and w
Hello everybody,
I had two problems with Axis2 1.3:
1) commons-logging and websphere 6.1
I ran into an issue with Axis2 1.3 when deploying it under websphere 6.1
(delegation mode set to PARENT_LAST of course) because websphere 6 runtime
embedded an older version of commons logging:
When deploying
header is set by
> commonsHTTPTransportSender and this is a basic use case. So I dont think
> that its broken.
> Do you see the following header in the response?
>
> Transfer-Encoding: chunked
>
> Thanks,
> Keith.
>
> On 10/3/07, FFF7878 <[EMAIL PROTECTED]> wrote:
>>
&
I've disabled chunking in the service and the content-length is still not
included by Axis2 in the HTTP header.
Could it be an Axis2 1.3 bug?
Thanks,
Pierre
keith chapman wrote:
>
> yes it would.
>
> Thanks,
> Keith.
>
> On 10/3/07, FFF7878 <[EMAIL PROTECTED]>
SSAGE_LABEL_OUT_VALUE );
>
> msgContext.setProperty(HTTPConstants.CHUNKED,"false");
>
> Thanks,
> Keith.
>
> On 10/3/07, FFF7878 <[EMAIL PROTECTED]> wrote:
>>
>>
>> Hello Axis users,
>> I have a web service integrated with Axis2 that communicates with client
Hello Axis users,
I have a web service integrated with Axis2 that communicates with clients
using gSOAP. The problem is that the client don't receive the complete XML
response (sent in three TCP packets) when the WS is using Axis2 while it is
working when using Axis1.
HTTP 1.1 is used. In axis2.xm
