Hi Samisa,
I apologize, it was my fault.
However,
0.95 behaves mush worse than 0.94 on the code i have sent you 3? days ago -
memory leak is more significant
1. 0.94 Windows - looks like
(1.1)
AXIS2_HTTP_CLIENT_SEND
(
http_client,
m_env,
Krankurs, Leonid wrote:
Hi Samisa,
I apologize, it was my fault.
However,
0.95 behaves mush worse than 0.94 on the code i have sent you 3? days ago -
memory leak is more significant
hmmm, 0.95 is supposed to be better - as far as I know, we did not touch
any areas that would expose more
Yes... We have an implementation on board.. Please check the savan
module in axis2. There is also a sample in the samples module..
We are not releasing it as part of Axis2 1.1... But I'm sure it'll be
released soon as a seperate module..
Thanks,
Thilina
On 10/29/06, Venkatesh Jayaraman
Hi Moiz,
I can see three issues...
1. You do not have MTOM enabled for your service.. You can do that
either by switching it on in the axis2.xml or in the service.xml for
a per service/operation based enabling..
2. It is not mandatory to have MTOM enabled. Response needs to decoded
well even
Can you post your WSDL?
I can have a look at it. Are you using wsdl 1.1 or 2.0
Matt
--- C. Brian Cox [EMAIL PROTECTED] wrote:
I have been working on a WSDL, and ran into a
problem when trying to make
use of simple types. So I tried to generate from
some of the sample wsdl's
included in the
OK I have the nightly snap shot jars in place.
I have tried a number of things.
renamed my wsdl to service.wsdl
(this lives in the META-INF in the aar)
Made sure the names matchup
service.wsdl:
wsdl:service name=AddressBook_v1_0_0.
services.xml:
service name=AddressBook_v1_0_0
Here are the standard Axis2 wsdl's which have the same problem as the new
one I am creating.
Thanks for the help.
Brian
-Original Message-
From: Matthew Hannay [mailto:[EMAIL PROTECTED]
Sent: Sunday, October 29, 2006 11:18 PM
To: axis-user@ws.apache.org
Subject: Re: Axis2 1.1 Code
Is there any configuration on this ?
how to handle long-duration service in Axis ?
-thanks
xu
Ok I figured this out.
It would seem that you cannot use a skeleton based server deploy if you
want to break down the service into individual operaitons within the server
and client config wsdd's.
I have got this to work with a server deploy however you have to set
skeletondeploy to false when
Brian,
there were problems with all 3 wsdl's. Somehow sneaked in. Fixed all 3
and added more locations where we throw informative exceptions. Please
get a nightly build in another couple of hours.
thanks,
dims
On 10/29/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Here are the standard Axis2
In your WSDL you have defined Document literal
services the way you have defined the messages is not
correct for document literal.
see:
http://www.w3.org/TR/wsdl#_messages
wsdl:message name=echoResponse
wsdl:part name=echoResponse
type=xsd:string/wsdl:part
/wsdl:message
Matt,
these are rpc/lit wsdl's :) not doc/lit.
-- dims
On 10/30/06, Matthew Hannay [EMAIL PROTECTED] wrote:
In your WSDL you have defined Document literal
services the way you have defined the messages is not
correct for document literal.
see:
http://www.w3.org/TR/wsdl#_messages
Hi,
Youc an try this out in MessageContext
MessageContext. setTimeout(1)
Thanks,
Srinivas N
From: xu cai
[mailto:[EMAIL PROTECTED]
Sent: Monday, October 30, 2006
12:44 PM
To: axis-user@ws.apache.org
Subject: Is there any way to
configure http timeout in Axis server
In the MTOM Example WSDL it says:
wsdl:typesxsd:schema
xsd:import
namespace=http://www.w3.org/2005/05/xmlmime;
schemaLocation=xmime.xsd /
is this correct ? Their seems to be some validation
errors?
Should it be something like:
xsd:import
there is a xmime.xsd in the same directory...
-- dims
On 10/30/06, Matthew Hannay [EMAIL PROTECTED] wrote:
In the MTOM Example WSDL it says:
wsdl:typesxsd:schema
xsd:import
namespace=http://www.w3.org/2005/05/xmlmime;
schemaLocation=xmime.xsd /
is this correct ? Their seems to
15 matches
Mail list logo