On Thu, Aug 4, 2011 at 7:32 PM, Deepal Jayasinghe wrote:
> >>
> >> I looked and the code segment you mentioned, but that is to process long
> >> running services. We had somewhat similar code to process request comes
> with
> >> replyTo header. If no one has removed then, we can fix the issue in
Hi Brett - with a bit more investigation I agree with you. I did find a
way to turn off the chunking, just in case
it helps anyone else but I will go ahead and deal with it in my apps.
Setting the ("Connection":"close") in
the response headers turns off persistent connectivity (as it is the
de
Have a look at the following:
http://wso2.org/library/259
Thanks,
Deepal
> Hi,
>
> I tries all combinations using the getResource in calssloader but it's
> not working.
> Can you point to a sample code example please?
>
> Many thanks
>
>
>
> On Tue, Aug 2, 2011 at 4:24 PM, Deepal Jayasinghe wrote
I have a client distribution that runs behind an API, and I need to get it to
be as small a distribution as possible. I am curious if there's a list
anywhere of the minimum list of JARs from the Axis2 1.5.1 binary distribution
that are required to execute a simple Web service client that uses X
A chunked response is typically a better option as eliminates the requirement
to know the full size of the response before sending any data. It also, as I
understand it, removes the limit on the size of the response.
Brett
-Original Message-
From: Demetris [mailto:demet...@ece.neu.edu]
Sagara,
Perhaps I am doing something wrong; ;however, whenever I try to use a List
(either as an attribute of a bean or separately) the list does get
created but its
elements are OMElements and are not deserialized. This happens even if I
declare the list as List. Also, while I can easily dec
Hi all,
is there a way to configure the server not to returned chunked data? Or
dealing with the
chunked data (may be reading the returned response using InputStreams)
is more efficient
than eliminating it?
Thanks
-
To unsu
On Thu, Aug 4, 2011 at 8:07 PM, Barry Hathaway wrote:
> This is good news! I am actually using the snapshot.
> Do you have any pointers to documentation that describes how to use these
> new features?
At the moment there is no such proper documentation exists but I'm
planning to write a tutorial
This is good news! I am actually using the snapshot.
Do you have any pointers to documentation that describes how to use
these new features?
Thanks.
Barry
On 8/4/2011 10:14 AM, Sagara Gunathunga wrote:
On Thu, Aug 4, 2011 at 7:15 AM, Narendra Kadali
wrote:
Hi Barry Hathaway,
As far as I k
On Thu, Aug 4, 2011 at 7:15 AM, Narendra Kadali
wrote:
> Hi Barry Hathaway,
>
> As far as I know Axis2 aximo data model does not support java collection
> framework. However one webservice input argument can be declared as List.
Java Collection and Map support has been implemented on Axis2 trunk
I would have thought the deserialization process would have gone deeper
into the bean.
Anyway, how do you iterate through the list and deserialize each OMElement?
I tried using BeanUtil.deserialize, but just got null back.
Thanks.
Barry
On 8/3/2011 7:29 PM, Deepal Jayasinghe wrote:
Hi Barry,
N
>>
>> I looked and the code segment you mentioned, but that is to process long
>> running services. We had somewhat similar code to process request comes with
>> replyTo header. If no one has removed then, we can fix the issue in AMR.
>
> This is for processing addressing headers with replyTo heade
On Thu, Aug 4, 2011 at 5:12 PM, Deepal Jayasinghe wrote:
> Amila,
>
> I looked and the code segment you mentioned, but that is to process long
> running services. We had somewhat similar code to process request comes with
> replyTo header. If no one has removed then, we can fix the issue in AMR.
On Thu, Aug 4, 2011 at 9:36 AM, Sagara Gunathunga
wrote:
> On Thu, Aug 4, 2011 at 5:12 PM, Deepal Jayasinghe
> wrote:
>> Amila,
>>
>> I looked and the code segment you mentioned, but that is to process long
>> running services. We had somewhat similar code to process request comes with
>> replyT
On Thu, Aug 4, 2011 at 5:12 PM, Deepal Jayasinghe wrote:
> Amila,
>
> I looked and the code segment you mentioned, but that is to process long
> running services. We had somewhat similar code to process request comes with
> replyTo header. If no one has removed then, we can fix the issue in AMR.
Hi,
I tries all combinations using the getResource in calssloader but it's
not working.
Can you point to a sample code example please?
Many thanks
On Tue, Aug 2, 2011 at 4:24 PM, Deepal Jayasinghe wrote:
> You can get the class loader and read the file using getResource as
> stream. Once you
If the response come before the timeout then it works. I am working on
the trunk.
Thanks.,
Deepal
On 8/4/2011 3:20 AM, Afkham Azeez wrote:
> I ran this scenario last week during a demo and it worked. But that
> was in WSO2 AS 4.1.0, which is based on Axis2 trunk. Perhaps this is
> an issue in the
Amila,
I looked and the code segment you mentioned, but that is to process long
running services. We had somewhat similar code to process request comes
with replyTo header. If no one has removed then, we can fix the issue in
AMR.
Thanks,
Deepal
> Do you mean this code
>
> if (messageCtx.isProper
Do you mean this code
if (messageCtx.isPropertyTrue(DO_ASYNC)
|| ((messageCtx.getParameter(DO_ASYNC) != null) &&
JavaUtils.isTrueExplicitly(messageCtx.getParameter(DO_ASYNC).getValue( {
String mep = messageCtx.getAxisOperation()
.getMessageExch
I ran this scenario last week during a demo and it worked. But that was in
WSO2 AS 4.1.0, which is based on Axis2 trunk. Perhaps this is an issue in
the 1.5 branch?
On Thu, Aug 4, 2011 at 6:13 AM, Deepal jayasinghe wrote:
> Guys,
> A user called "Todd" recently observed [1] that we have issues
20 matches
Mail list logo
