I am now checking the axiom_node_create_from_buffer function. On Thu, Mar 29, 2012 at 4:45 PM, Matan Cohen <matancohen...@gmail.com>wrote:
> Hi Josef, > thanks for your reply . > I'm writing a Client program , this Program is getting a full SOAP > envelop from a different application . > my experience with AXIS2\C is in writing a client programs but I used the > WSDL2C to produce the stub , and then used the function that was built > automatically for me . > the Originial question is: What actions can I perform in order to send it > forward to the Webservice provider the SOAP Envelop ? . > > On Thu, Mar 29, 2012 at 4:24 PM, Stadelmann Josef < > josef.stadelm...@axa-winterthur.ch> wrote: > >> Hi Matan,**** >> >> ** ** >> >> If I understand you correct, you are saying that you have mastered >> axiom/C to build a model and then use serialize() to write this xml string? >> While serializing from an OMElement is easy, the harder part is to write >> your parser and create this/your object model using axiom/C routines. I >> would also suggest, but I believe you did so already, to have a look at the >> examples delivered with the AXIS2/C binary installation. And another very >> good resource is the AXIS2/C source kit itself. There you will find test to >> test Axiom and finally the simple-server, and a lot is there to get known >> of it.**** >> >> ** ** >> >> Will serializing and de-serializing is one thing; the other thing is how >> to make up and deploy your server and your client; for that I suggest to >> start with the examples found in the AXIS2/C installation unless you >> understand all of it. Also, I personally found it very helpful to download >> the AXIS2/C sources and build my AXIS2/C distribution myself. It is not so >> hard if you use Visual Studio,; Later on you can much better debug your >> client server applications. If something does not work but raises >> exceptions or returns fault status or objects you get a much better idea >> why something fails. Even with good documents and user guides, debugging >> your code and the ability to deeply dive into axis2/axiom code is >> important when it comes to debugging in general, or debugging nasty >> problems. This from 6 years of learning in the open source community.**** >> >> ** ** >> >> Josef**** >> >> ** ** >> >> ** ** >> >> ** ** >> >> *Von:* Matan Cohen [mailto:matancohen...@gmail.com] >> *Gesendet:* Mittwoch, 28. März 2012 12:29 >> *An:* c-user@axis.apache.org >> *Betreff:* SOAP Message**** >> >> ** ** >> >> >> **** >> >> Hi , **** >> >> I using Axis2C sucessfully when I'm building the elements .**** >> >> I now need to wrrite a C program which is getting the URI and SOAP >> message , for example this message located in a string:**** >> >> soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" >> xmlns:q0="http://iproxies.soa.imex" xmlns:q1="http://mapper.soa.imex" >> xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi=" >> http://www.w3.org/2001/XMLSchema-instance">**** >> >> - <soapenv:Body>**** >> >> - <q0:>**** >> >> <q0:entity>001</q0:entity> **** >> >> - <q0:inputData>**** >> >> <q1:_LimitOutputRespons_lmrptReportData /> **** >> >> >> <q1:limitInputParameters_limitCustId>CUST1</q1:limitInputParameters_limitCustId> >> **** >> >> >> <q1:limitInputParameters_limitEntity>001</q1:limitInputParameters_limitEntity> >> **** >> >> <q1:limitOutputRespons_lmrptReturnCode /> **** >> >> </q0:inputData>**** >> >> </q0:executeGetLexecuteGetLimitInquiryimitInquiry>**** >> >> </soapenv:Body>**** >> >> </soapenv:Envelope>**** >> >> ** ** >> >> How can I send the this Messages forward to the service provider ?**** >> >> I tried searching for a written function to do so , but without any >> success .**** >> >> ** ** >> >> Any help will be highly appriciate .**** >> >> -- **** >> >> ______________________**** >> >> best regards, >> matan cohen >> MF System Administrator. **** >> >> ** ** >> > > > > -- > ______________________ > best regards, > matan cohen > MF System Administrator. > > -- ______________________ best regards, matan cohen MF System Administrator.