(Axis2C)Delete of node_sub_trees doesnt work in case of extra namespace declaration!

Hello everybody! I have the following problem. ns1 = axiom_namespace_create(...); ns2 = axiom_namespace_create(...); ns3 = axiom_namespace_create(...); axiom_node_t* elem_node = NULL; axiom_element_t* elem_ele = axiom_element_create(env, NULL, asdf, NULL, elem_node); // marked

Re: hot deployment and 'undeployment'

Yan, Hot update/undeployment can be enabled by adding the following line to your axis2.xml: parameter name=hotupdatetrue/parameter Regards, Andreas On Thu, Feb 12, 2009 at 05:25, Yan Liu cigi_yan...@yahoo.com wrote: Hi, Hot deployment feature in Axis2 1.4.1 is great. I'd like to create

Starting and stopping axis server.

Hi All, I am new to axis and also new to UNIX environment, I am stuck with one problem hope you guys could help me out. I need to setup axis2 1.3 standalone servers on various production sites. The setup should be such that axis2 can run unsupervised. What it means is if by any chance a

RE: SOA Help

Thanks a lot Keith. Thanks, Appasamy From: keith chapman [mailto:keithgchap...@gmail.com] Sent: Wednesday, February 11, 2009 14:37 To: axis-user@ws.apache.org Subject: Re: SOA Help This article [1] gives an overview of SOA. Thanks, Keith. [1]

RE: Starting and stopping axis server.

On unix, i think you play with /etc/rcX.d, which describes the way the system boots. On windows, you can place your batch in the startup folder or use some of the *.ini files windows looks at when it starts. Yves-Marie De : Salman A. Kagzi

Re: hot deployment and 'undeployment'

I know about hot update. My question was: is hot deployment + hot undeployment = hot update? Hot update is disabled by default because it might leave axis2 in uncertain state and ongoing service data might be lost. I guess the same thing happens when removing .aar manually. am i right? Thanks,

Re: hot deployment and 'undeployment'

Yes removing a service at runtime could put request coming to that service in a Zombie state. Thanks, Keith. On Thu, Feb 12, 2009 at 8:34 PM, Yan Liu cigi_yan...@yahoo.com wrote: I know about hot update. My question was: is hot deployment + hot undeployment = hot update? Hot update is

SOAP Headers in wsdl

Hi, I'm trying to make an authentication module that takes the username and password from a soap header in the input messages. For this I have defined de following schema in the wsdl: xs:schema attributeFormDefault=qualified elementFormDefault=qualified targetNamespace=http://myapp.com;

WS Client-dataHandler from Content-ID (using MTOM) : File upload Webservice

Hi, I have a web service that uploads the attachment so that it can be received by the client. The web service is working fine and is also updoading a file. And I see a success response on the client side. I can also obtain the ContentId from the Content Id List from the Attachment map (from

Re: WS Client-dataHandler from Content-ID (using MTOM) : File upload Webservice

Asmita, In Axis2, MTOM attachments are represented as OMText nodes in the object model of the message. You can retrieve the data handler by calling getDataHandler on the OMText instance and casting the result to DataHandler. Andreas On Thu, Feb 12, 2009 at 20:29, Attharkar, Asmita

RE: WS Client-dataHandler from Content-ID (using MTOM) : File upload Webservice

Thanks Andreas for the quick response, But I am adding the attachment in outMsgContext on the server side. There is no argument in the web service method that represents the attachment. Should I still retrieve the attachment from OMText node? If yes, do you have a sample to retrieve it from

MTOM file upload webservice

Hi, I am trying to write a web service which uploads a file so that it can be retrieved by the client. Most of the articles that I have read talks about file upload web service using SwA. My Web service is uploading the file with no issues and adding it to outMsgContext (like the eg shown for

Re: hot deployment and 'undeployment'

So what if we put a handler there to disable all requests for the service being removed (or already removed)? the handler could be triggered by a undeploy action. I think it is more complicated if we consider the inconsistency among axis2 listener, memory allocated, dynamically loaded