Re: [Axis2C] Client with xml declaration
Hi Samisa, Atanacio, I see a valid point here in including the xml declaration in the soap_envelope_serialize() method. However, after querying various developers it was decided that the addition of the xml declaration was the responsibility of the authority who does the soap_envelope_serialize() and therefore has been added at transport sender level. Another reason to why we took this approach is the ability for the user to specify in the axis2.xml whether or whether not the xml declaration has to be sent with the SOAP message. I think it is much cleaner. One more reason was the flexibility we gain in interop scenarios which meets the WS-I specification that the xml declaration is optional, when it comes to sending. Regards, Senaka On Thu, 2008-01-17 at 06:09 +0530, Samisa Abeysinghe wrote: > Senaka Fernando wrote: > > Hi Antonio, > > This might work. But, I don't believe that writing the XML declaration is > > necessarily a part of axiom_soap_envelope_serialize(). This is because, > > logically speaking, the XML declaration is not a part of the SOAP > > envelope. > > Logically speaking, a SOAP envelope is an XML document. > > > By doing this tweak, you are violating the concept of a SOAP > > envelope. And, therefore this is not correct according to my personal > > belief. Devs, please correct me if I've made any mistake. > > > > It is nt possible to include this in OM layer, as we cannot afford to > keep state of the start point of serialization. That would restrict our > ability to serioalize a given node as we wish when we wish. > > Hence for me, the solution by Atanacio looks fine. > > Samisa... > > Regards, > > Senaka > > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Strange REST Parsing
One question about Senaka's test is that are you using the same echo sample without modification ? If so I think the behaviour is not strange, since the echo sample only takes one parameter and parameters are internally kept in a hash table. I guess the hash table ordering is done in a way such that the keys with least hash values come first when you query all the keys (or the first key). So when the echo sample requests the first parameter (because it takes only one param) the parameter name which has the least hash value comes first as the output and hence the three outputs. One side-note is that the client-side or the server-side *should not* depend on the order of the parameters as they can be different for different client or server sitting in the other end. AFAIK rest (or HTTP specs) does not impose strict ordering on parameters in the url. The proper way to get parameter values is use the parameter name as the key and query for that key to get relevant value. Thanks -sahan On 1/16/08, Samisa Abeysinghe <[EMAIL PROTECTED]> wrote: > This happens because we are using a hash to store the request params, > and then use a for loop to retrieve the params. The order in which the > params are retrieved depends on the hashing function in use. > If we are to solve this, we have to get rid of the has and go for > another container where the original ordering could be preserved. > > Samisa... > > Senaka Fernando wrote: > > Hi Brian, > > I think this is a bug somewhere or the other. I tried it and was amazed to > > get another result. > > > > try1: > > http://localhost:8080/axis2/services/echo/echoString?qid=qid1\&hostname=hostname1\&bbpl_id=d6ge5gyrgj4 > > > > result1: > > > > d6ge5gyrgj4 > > > > > > try2: > > http://localhost:8080/axis2/services/echo/echoString?qid=qid1\&hostname=hostname1\&bepl_id=d6ge5gyrgj4 > > > > result2: > > > > qid1\ > > > > > > try3: > > http://localhost:8080/axis2/services/echo/echoString?bid=qid1\&bastname=hostname1\&bipl_id=d6ge5gyrgj4 > > > > result3: > > > > d6ge5gyrgj4 > > > > > > I have no idea on what logic takes place. There is no alphabetic sort or > > node grouping here. It is something I can't logically explain. But, I will > > look in to this and raise appropriate JIRAs. > > > > Regards, > > Senaka > > > > N.B.: I tried this using Mozilla Firefox. > > > > > > > > > >> Great - this will be a perfect example I do this one: > >> > >> curl > >> http://localhost:9090/axis2/services/echo/echoString?qid=qid1\&hostname=hostname1\&repl_id=d6ge5gyrgj4 > >> > >> I get: > >> > >> >> xmlns:ns1="http://ws.apache.org/axis2/c/samples";>qid1 > >> > >> It echoed the first parameter. > >> > >> When I change the last parameter to be alphabetically first: > >> > >> curl > >> http://localhost:9090/axis2/services/echo/echoString?qid=qid1\&hostname=hostname1\&b=d6ge5gyrgj4 > >> > >> Now the last parameter is echoed: > >> > >> >> xmlns:ns1="http://ws.apache.org/axis2/c/samples";>d6ge5gyrgj4 > >> > >> Its apparently not a simple an alphabetical sort, but its something > >> odd. Why would the name of the parameter effect the ordering of the > >> nodes as constructed within the server? I think the server is > >> converting the REST input into a sequence of nodes somehow, and it is > >> imposing and order of its own on the nodes. > >> > >> Brian > >> > >> On Jan 16, 2008 12:56 AM, Dinesh Premalal <[EMAIL PROTECTED]> wrote: > >> > >>> Hi Brain, > >>> > >>> "Brian McQueen" <[EMAIL PROTECTED]> writes: > >>> > > >>> xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope";> > >>> > > > > >>> xmlns:ns1="http://ws.apache.org/axis2/services/replicate";> > >>> > qid1 > hostname1 > d6ge5gyrgj4 > > > > > >>> I modified echo sample to echo back the node it receives. I used > >>> following commands > >>> > >>> curl > >>> http://localhost:9090/axis2/services/echo/echoString?qid=qid1\&hostname=hostname1\&repl_id=d6ge5gyrgj4 > >>> > >>> I got this as the response > >>> > >>> qid1hostname1d6ge5gyrgj4 > >>> > >>> > >>> then I used following command > >>> > >>> curl > >>> http://localhost:9090/axis2/services/echo/echoString?qid=qid1\&repl_id=d6ge5gyrgj4\&hostname=hostname1 > >>> > >>> and response is > >>> > >>> qid1d6ge5gyrgj4hostname1 > >>> > >>> as far as I can see , there is a no such an alphabetical ordering in > >>> REST parsing or did I miss something here? > >>> > >>> thanks, > >>> Dinesh > >>> > >>> -- > >>> http://nethu.org > >>> > >>> > >>> - > >>> To unsubscribe, e-mail: [EMAIL PROTECTED] > >>> For additional commands, e-mail: [EMAIL PROTECTED] > >>> > >>> > >>> > >> - > >> To unsubscribe, e-mail: [EMAIL PROTECTED] > >> For additional commands, e-mail: [EMAIL PROTECTED] > >> > >> > >> > > > > > > --
Re: Strange REST Parsing
This happens because we are using a hash to store the request params, and then use a for loop to retrieve the params. The order in which the params are retrieved depends on the hashing function in use. If we are to solve this, we have to get rid of the has and go for another container where the original ordering could be preserved. Samisa... Senaka Fernando wrote: Hi Brian, I think this is a bug somewhere or the other. I tried it and was amazed to get another result. try1: http://localhost:8080/axis2/services/echo/echoString?qid=qid1\&hostname=hostname1\&bbpl_id=d6ge5gyrgj4 result1: d6ge5gyrgj4 try2: http://localhost:8080/axis2/services/echo/echoString?qid=qid1\&hostname=hostname1\&bepl_id=d6ge5gyrgj4 result2: qid1\ try3: http://localhost:8080/axis2/services/echo/echoString?bid=qid1\&bastname=hostname1\&bipl_id=d6ge5gyrgj4 result3: d6ge5gyrgj4 I have no idea on what logic takes place. There is no alphabetic sort or node grouping here. It is something I can't logically explain. But, I will look in to this and raise appropriate JIRAs. Regards, Senaka N.B.: I tried this using Mozilla Firefox. Great - this will be a perfect example I do this one: curl http://localhost:9090/axis2/services/echo/echoString?qid=qid1\&hostname=hostname1\&repl_id=d6ge5gyrgj4 I get: http://ws.apache.org/axis2/c/samples";>qid1 It echoed the first parameter. When I change the last parameter to be alphabetically first: curl http://localhost:9090/axis2/services/echo/echoString?qid=qid1\&hostname=hostname1\&b=d6ge5gyrgj4 Now the last parameter is echoed: http://ws.apache.org/axis2/c/samples";>d6ge5gyrgj4 Its apparently not a simple an alphabetical sort, but its something odd. Why would the name of the parameter effect the ordering of the nodes as constructed within the server? I think the server is converting the REST input into a sequence of nodes somehow, and it is imposing and order of its own on the nodes. Brian On Jan 16, 2008 12:56 AM, Dinesh Premalal <[EMAIL PROTECTED]> wrote: Hi Brain, "Brian McQueen" <[EMAIL PROTECTED]> writes: xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope";> xmlns:ns1="http://ws.apache.org/axis2/services/replicate";> qid1 hostname1 d6ge5gyrgj4 I modified echo sample to echo back the node it receives. I used following commands curl http://localhost:9090/axis2/services/echo/echoString?qid=qid1\&hostname=hostname1\&repl_id=d6ge5gyrgj4 I got this as the response qid1hostname1d6ge5gyrgj4 then I used following command curl http://localhost:9090/axis2/services/echo/echoString?qid=qid1\&repl_id=d6ge5gyrgj4\&hostname=hostname1 and response is qid1d6ge5gyrgj4hostname1 as far as I can see , there is a no such an alphabetical ordering in REST parsing or did I miss something here? thanks, Dinesh -- http://nethu.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2C] Client with xml declaration
Senaka Fernando wrote: Hi Antonio, This might work. But, I don't believe that writing the XML declaration is necessarily a part of axiom_soap_envelope_serialize(). This is because, logically speaking, the XML declaration is not a part of the SOAP envelope. Logically speaking, a SOAP envelope is an XML document. By doing this tweak, you are violating the concept of a SOAP envelope. And, therefore this is not correct according to my personal belief. Devs, please correct me if I've made any mistake. It is nt possible to include this in OM layer, as we cannot afford to keep state of the start point of serialization. That would restrict our ability to serioalize a given node as we wish when we wish. Hence for me, the solution by Atanacio looks fine. Samisa... Regards, Senaka in file /axiom/src/soap/soap_envelope.c I only add the line axiom_output_write_xml_version_encoding(om_output, env); to the function axiom_soap_envelope_serialize() /* write the xml version and encoding These should be set to om output before calling the serialize function Otherwise default values will be written */ ->axiom_output_write_xml_version_encoding(om_output, env); It work for me but I don't know if it is rigth. - Original Message From: Sébastien Mougey <[EMAIL PROTECTED]> To: Apache AXIS C User List Sent: Wednesday, January 16, 2008 5:16:41 AM Subject: Re: [Axis2C] Client with xml declaration Hi Senaka Thank you ! I'll try it today. Yours De : Senaka Fernando <[EMAIL PROTECTED]> Répondre à : Apache AXIS C User List Date : Wed, 16 Jan 2008 06:50:44 -0500 (EST) À : Objet : Re: [Axis2C] Client with xml declaration Hi Sébastien, This is now available on the head. Set name="xml-declaration" insert="true"/> for the respective transport and run your server/client. Please note that you have to obtain an svn checkout from [1]. Regards, Senaka [1] http://svn.apache.org/repos/asf/webservices/axis2/trunk/c Hi AFAIK, There is a JIRA issue raised against this at [1]. The patch is not yet applied. This feature will be available on the head as soon as the patch is applied. Then, You'll merely have to change a setting in axis2.xml. Please take a look at [1], once it is resolved this feature will be available on the head. [1] https://issues.apache.org/jira/browse/AXIS2C-666 Regards, Senaka Hello I can't find how I could tell Axis2/C in client mode to add a xml declaration to the request. I only want my request to start with : Thank you for your help Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2C] Client with xml declaration
Hi Atanacio, Sorry for spelling your name wrong. Regards, Senaka > Hi Antonio, > This might work. But, I don't believe that writing the XML declaration is > necessarily a part of axiom_soap_envelope_serialize(). This is because, > logically speaking, the XML declaration is not a part of the SOAP > envelope. By doing this tweak, you are violating the concept of a SOAP > envelope. And, therefore this is not correct according to my personal > belief. Devs, please correct me if I've made any mistake. > > Regards, > Senaka > >> in file /axiom/src/soap/soap_envelope.c >> I only add the line >> axiom_output_write_xml_version_encoding(om_output, env); >> to the function axiom_soap_envelope_serialize() >> >> /* write the xml version and encoding >>These should be set to om output before calling the serialize >> function >>Otherwise default values will be written >> */ >> ->axiom_output_write_xml_version_encoding(om_output, env); >> >> It work for me but I don't know if it is rigth. >> >> - Original Message >> From: Sébastien Mougey <[EMAIL PROTECTED]> >> To: Apache AXIS C User List >> Sent: Wednesday, January 16, 2008 5:16:41 AM >> Subject: Re: [Axis2C] Client with xml declaration >> >> >> Hi Senaka >> >> Thank you ! I'll try it today. >> >> Yours >> >> >>> De : Senaka Fernando <[EMAIL PROTECTED]> >>> Répondre à : Apache AXIS C User List >>> Date : Wed, 16 Jan 2008 06:50:44 -0500 (EST) >>> À : >>> Objet : Re: [Axis2C] Client with xml declaration >>> >>> Hi Sébastien, >>> >>> This is now available on the head. Set > name="xml-declaration" >>> insert="true"/> for the respective transport and run your >> server/client. >>> Please note that you have to obtain an svn checkout from [1]. >>> >>> Regards, >>> Senaka >>> >>> [1] http://svn.apache.org/repos/asf/webservices/axis2/trunk/c >>> Hi AFAIK, There is a JIRA issue raised against this at [1]. The >> patch is not yet applied. This feature will be available on the head as soon >> as the patch is applied. Then, You'll merely have to change a setting in axis2.xml. Please take a look at [1], once it is resolved this feature will be available on the head. [1] https://issues.apache.org/jira/browse/AXIS2C-666 Regards, Senaka > Hello > > I can't find how I could tell Axis2/C in client mode to add a xml > declaration to the request. > > I only want my request to start with : > > > Thank you for your help >> >> >> >> >> >> >> >> >> Be a better friend, newshound, and >> know-it-all with Yahoo! Mobile. Try it now. >> http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ >> >> >> - >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2C] Client with xml declaration
Hi Antonio, This might work. But, I don't believe that writing the XML declaration is necessarily a part of axiom_soap_envelope_serialize(). This is because, logically speaking, the XML declaration is not a part of the SOAP envelope. By doing this tweak, you are violating the concept of a SOAP envelope. And, therefore this is not correct according to my personal belief. Devs, please correct me if I've made any mistake. Regards, Senaka > in file /axiom/src/soap/soap_envelope.c > I only add the line > axiom_output_write_xml_version_encoding(om_output, env); > to the function axiom_soap_envelope_serialize() > > /* write the xml version and encoding >These should be set to om output before calling the serialize > function >Otherwise default values will be written > */ > ->axiom_output_write_xml_version_encoding(om_output, env); > > It work for me but I don't know if it is rigth. > > - Original Message > From: Sébastien Mougey <[EMAIL PROTECTED]> > To: Apache AXIS C User List > Sent: Wednesday, January 16, 2008 5:16:41 AM > Subject: Re: [Axis2C] Client with xml declaration > > > Hi Senaka > > Thank you ! I'll try it today. > > Yours > > >> De : Senaka Fernando <[EMAIL PROTECTED]> >> Répondre à : Apache AXIS C User List >> Date : Wed, 16 Jan 2008 06:50:44 -0500 (EST) >> À : >> Objet : Re: [Axis2C] Client with xml declaration >> >> Hi Sébastien, >> >> This is now available on the head. Set name="xml-declaration" >> insert="true"/> for the respective transport and run your > server/client. >> Please note that you have to obtain an svn checkout from [1]. >> >> Regards, >> Senaka >> >> [1] http://svn.apache.org/repos/asf/webservices/axis2/trunk/c >> >>> Hi AFAIK, There is a JIRA issue raised against this at [1]. The > patch is >>> not yet applied. This feature will be available on the head as soon > as the >>> patch is applied. Then, You'll merely have to change a setting in >>> axis2.xml. >>> Please take a look at [1], once it is resolved this feature will be >>> available on the head. >>> >>> [1] https://issues.apache.org/jira/browse/AXIS2C-666 >>> >>> Regards, >>> Senaka >>> Hello I can't find how I could tell Axis2/C in client mode to add a xml declaration to the request. I only want my request to start with : Thank you for your help > > > > > > > > > Be a better friend, newshound, and > know-it-all with Yahoo! Mobile. Try it now. > http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2C] Client with xml declaration
in file /axiom/src/soap/soap_envelope.c I only add the line axiom_output_write_xml_version_encoding(om_output, env); to the function axiom_soap_envelope_serialize() /* write the xml version and encoding These should be set to om output before calling the serialize function Otherwise default values will be written */ ->axiom_output_write_xml_version_encoding(om_output, env); It work for me but I don't know if it is rigth. - Original Message From: Sébastien Mougey <[EMAIL PROTECTED]> To: Apache AXIS C User List Sent: Wednesday, January 16, 2008 5:16:41 AM Subject: Re: [Axis2C] Client with xml declaration Hi Senaka Thank you ! I'll try it today. Yours > De : Senaka Fernando <[EMAIL PROTECTED]> > Répondre à : Apache AXIS C User List > Date : Wed, 16 Jan 2008 06:50:44 -0500 (EST) > À : > Objet : Re: [Axis2C] Client with xml declaration > > Hi Sébastien, > > This is now available on the head. Set insert="true"/> for the respective transport and run your server/client. > Please note that you have to obtain an svn checkout from [1]. > > Regards, > Senaka > > [1] http://svn.apache.org/repos/asf/webservices/axis2/trunk/c > >> Hi AFAIK, There is a JIRA issue raised against this at [1]. The patch is >> not yet applied. This feature will be available on the head as soon as the >> patch is applied. Then, You'll merely have to change a setting in >> axis2.xml. >> Please take a look at [1], once it is resolved this feature will be >> available on the head. >> >> [1] https://issues.apache.org/jira/browse/AXIS2C-666 >> >> Regards, >> Senaka >> >>> Hello >>> >>> I can't find how I could tell Axis2/C in client mode to add a xml >>> declaration to the request. >>> >>> I only want my request to start with : >>> >>> >>> Thank you for your help Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Strange REST Parsing
Hi Brian, I think this is a bug somewhere or the other. I tried it and was amazed to get another result. try1: http://localhost:8080/axis2/services/echo/echoString?qid=qid1\&hostname=hostname1\&bbpl_id=d6ge5gyrgj4 result1: d6ge5gyrgj4 try2: http://localhost:8080/axis2/services/echo/echoString?qid=qid1\&hostname=hostname1\&bepl_id=d6ge5gyrgj4 result2: qid1\ try3: http://localhost:8080/axis2/services/echo/echoString?bid=qid1\&bastname=hostname1\&bipl_id=d6ge5gyrgj4 result3: d6ge5gyrgj4 I have no idea on what logic takes place. There is no alphabetic sort or node grouping here. It is something I can't logically explain. But, I will look in to this and raise appropriate JIRAs. Regards, Senaka N.B.: I tried this using Mozilla Firefox. > Great - this will be a perfect example I do this one: > > curl > http://localhost:9090/axis2/services/echo/echoString?qid=qid1\&hostname=hostname1\&repl_id=d6ge5gyrgj4 > > I get: > > xmlns:ns1="http://ws.apache.org/axis2/c/samples";>qid1 > > It echoed the first parameter. > > When I change the last parameter to be alphabetically first: > > curl > http://localhost:9090/axis2/services/echo/echoString?qid=qid1\&hostname=hostname1\&b=d6ge5gyrgj4 > > Now the last parameter is echoed: > > xmlns:ns1="http://ws.apache.org/axis2/c/samples";>d6ge5gyrgj4 > > Its apparently not a simple an alphabetical sort, but its something > odd. Why would the name of the parameter effect the ordering of the > nodes as constructed within the server? I think the server is > converting the REST input into a sequence of nodes somehow, and it is > imposing and order of its own on the nodes. > > Brian > > On Jan 16, 2008 12:56 AM, Dinesh Premalal <[EMAIL PROTECTED]> wrote: >> Hi Brain, >> >> "Brian McQueen" <[EMAIL PROTECTED]> writes: >> > > xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope";> >> > >> > >> > > xmlns:ns1="http://ws.apache.org/axis2/services/replicate";> >> > qid1 >> > hostname1 >> > d6ge5gyrgj4 >> > >> > >> > >> >> I modified echo sample to echo back the node it receives. I used >> following commands >> >> curl >> http://localhost:9090/axis2/services/echo/echoString?qid=qid1\&hostname=hostname1\&repl_id=d6ge5gyrgj4 >> >> I got this as the response >> >> qid1hostname1d6ge5gyrgj4 >> >> >> then I used following command >> >> curl >> http://localhost:9090/axis2/services/echo/echoString?qid=qid1\&repl_id=d6ge5gyrgj4\&hostname=hostname1 >> >> and response is >> >> qid1d6ge5gyrgj4hostname1 >> >> as far as I can see , there is a no such an alphabetical ordering in >> REST parsing or did I miss something here? >> >> thanks, >> Dinesh >> >> -- >> http://nethu.org >> >> >> - >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Strange REST Parsing
Great - this will be a perfect example I do this one: curl http://localhost:9090/axis2/services/echo/echoString?qid=qid1\&hostname=hostname1\&repl_id=d6ge5gyrgj4 I get: http://ws.apache.org/axis2/c/samples";>qid1 It echoed the first parameter. When I change the last parameter to be alphabetically first: curl http://localhost:9090/axis2/services/echo/echoString?qid=qid1\&hostname=hostname1\&b=d6ge5gyrgj4 Now the last parameter is echoed: http://ws.apache.org/axis2/c/samples";>d6ge5gyrgj4 Its apparently not a simple an alphabetical sort, but its something odd. Why would the name of the parameter effect the ordering of the nodes as constructed within the server? I think the server is converting the REST input into a sequence of nodes somehow, and it is imposing and order of its own on the nodes. Brian On Jan 16, 2008 12:56 AM, Dinesh Premalal <[EMAIL PROTECTED]> wrote: > Hi Brain, > > "Brian McQueen" <[EMAIL PROTECTED]> writes: > > http://www.w3.org/2003/05/soap-envelope";> > > > > > > > xmlns:ns1="http://ws.apache.org/axis2/services/replicate";> > > qid1 > > hostname1 > > d6ge5gyrgj4 > > > > > > > > I modified echo sample to echo back the node it receives. I used > following commands > > curl > http://localhost:9090/axis2/services/echo/echoString?qid=qid1\&hostname=hostname1\&repl_id=d6ge5gyrgj4 > > I got this as the response > > qid1hostname1d6ge5gyrgj4 > > > then I used following command > > curl > http://localhost:9090/axis2/services/echo/echoString?qid=qid1\&repl_id=d6ge5gyrgj4\&hostname=hostname1 > > and response is > > qid1d6ge5gyrgj4hostname1 > > as far as I can see , there is a no such an alphabetical ordering in > REST parsing or did I miss something here? > > thanks, > Dinesh > > -- > http://nethu.org > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Rampart/C] [ANN] Apache Rampart/C 1.1.0 Released
Hi All, Apache Rampart/C team is pleased to announce the release of Apache Rampart/C 1.1 You may download the release from http://ws.apache.org/rampart/c/download.cgi Key features of the release --- 1. Ability to send and verify UsernameTokens with - Username and PlainText password - Username and Digested password 2. Ability to send Timestamp tokens 3. SOAP message encryption - With derived key support for improved security - Symmetric and Asymmetric modes of operations - Support for AES and Tripple DES encryption - Signature encryption - Keys encryption 4. SOAP message signature - XML signature with RSA-SHA1 - Message authentication with HMAC-SHA1 - Signature confirmation support - SOAP Header signing 5. WS-Security Policy (spec 1.1) based configurations - Support for both Symmetric as well as Asymmetric policy bindings - Support for different modes of key identifiers - Support for different algorithm suites [Basic128, Basic 192, Basic256, TrippleDES, Basic128Rsa15, Basic192Rsa15,Basic256Rsa15, TripleDesRsa15] 6. Replay detection support - Easy to use built-in replay detection module - Ability to deploy a customized replay detection module 7. Different protection orders - Encrypt before signing - Sign before encrypting 8. Extensible modules - Password callback module - Authentication module - Credentials module 9. Keys management - Support for X509 token profile - Support for Key identifiers, Thumb prints, Issuer/Serial pairs, Embedded and Direct references 10. Other - Easy to use deployment scripts - A comprehensive set of samples Major Changes Since Last Release 1. MAC support with HMAC-SHA1 2. Derrived key encryption 3. Derived key signing 4. Symmetric policy bindings 5. New security header processor based on SOAP header layout 6. Security policy validator 7. Extensible Replay detection module 8. Signature confirmation support 9. Support for X509 thumb prints 10. Easy to use deployment scripts 11. Memory leak fixes 12. Many bug fixes Issues can be reported here. http://issues.apache.org/jira/browse/RAMPARTC We welcome your early feedback. Thank you for your interest in Rampart/C. --Apache Rampart/C Team-- http://ws.apache.org/rampart/c/ -- http://blog.kaushalye.org/ http://wso2.org/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2C] Client with xml declaration
Hi Senaka Thank you ! I'll try it today. Yours > De : Senaka Fernando <[EMAIL PROTECTED]> > Répondre à : Apache AXIS C User List > Date : Wed, 16 Jan 2008 06:50:44 -0500 (EST) > À : > Objet : Re: [Axis2C] Client with xml declaration > > Hi Sébastien, > > This is now available on the head. Set insert="true"/> for the respective transport and run your server/client. > Please note that you have to obtain an svn checkout from [1]. > > Regards, > Senaka > > [1] http://svn.apache.org/repos/asf/webservices/axis2/trunk/c > >> Hi AFAIK, There is a JIRA issue raised against this at [1]. The patch is >> not yet applied. This feature will be available on the head as soon as the >> patch is applied. Then, You'll merely have to change a setting in >> axis2.xml. >> Please take a look at [1], once it is resolved this feature will be >> available on the head. >> >> [1] https://issues.apache.org/jira/browse/AXIS2C-666 >> >> Regards, >> Senaka >> >>> Hello >>> >>> I can't find how I could tell Axis2/C in client mode to add a xml >>> declaration to the request. >>> >>> I only want my request to start with : >>> >>> >>> Thank you for your help >>> >>> >>> >>> - >>> To unsubscribe, e-mail: [EMAIL PROTECTED] >>> For additional commands, e-mail: [EMAIL PROTECTED] >>> >>> >> >> >> - >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
AW: AW: [AXIS2C] how to set logging to stderr?
Hi all, and thank you all, you answered my question, axis_log = axutil_log_create(allocator, NULL, stdout); does the trick for me on a Windows 2000 system with VS2005. Without sdtout in the parameter list, but NULL, the log would be axis2.log, but with stdout instead of NULL, the log goes to the screen. Dont know why but it works. I just enterd stdout as 3th parameter, and was expecting that I get a compiler error message, something like sdtout is not declared .. but sttdout is defined as #define stdout (&__iob_func()[1]) in stdio.h So to my surprise VC2005 was happy and when I run my code I get all the log records on a standard screen like any prinf() statement does. But anyway, thank for your help. I got a lot very helpfull stuff now and will consider it when I do the final designe step for myserver. Regards Josef.Stadelmann@ axa-winterthur.ch -Ursprüngliche Nachricht- Von: Senaka Fernando [mailto:[EMAIL PROTECTED] Gesendet: Mittwoch, 16. Januar 2008 11:43 An: Apache AXIS C User List Betreff: Re: AW: [AXIS2C] how to set logging to stderr? Hi Dinesh, and Josef Hi this is a cheap solution, to set permissions etc. The better way is this. As you see, in Linux, the std-streams are mapped to files. If you write to those files they will be written to the respective streams irrespective of what and how you write. You can't prioritize redirects to specific locations. That means it is impossible to write error messages to one and debug messages to another according to the current implementation. However, you should be able to write to several locations with priorities if you build yourself a little extension. This is the process. 1. You'll have to figure out how to write to stdout. That means you have to write to that file that maps to the stdout stream. 2. You will run your axis_based_executable inside another. 3. Read more on how you could use fork and exec to create background processes so that you can run one application inside another. 4. You outer application will barely listen to the stdout stream. 5. Then it is upto your outer application to do the logging. 6. Identification of error/debug etc messages can be done using a regular expression parsing mechanism. Startup Workflow: A - outer_client B - inner_axis_based_client 1. run A 2. A runs B (background) 3. B writes logs to stdout 4. A listens to stdout 5. A writes to log_file, stderror etc. Exit Workflow: A - outer_client B - inner_axis_based_client 1. A catches Ctrl+C 2. A kills B 3. A exits I know that this is so complicated but I don't see any better way. Regards, Senaka > Hi, > > "Stadelmann Josef" <[EMAIL PROTECTED]> writes: > >> Thanks, but as I do not use axis2 simple server ... >> I am jsut using the axiom libs and libs forming the base >> such as axutil and libxml2 etc. >> >> What do I use to redirect output in code? >> axis_log = axutil_log_create(allocator, NULL, NULL); >> this creates an axis2.log under . directory > > AFAIK , there is a no such a way to redirect out put to stdout or > stderr. However I could say you a small workaround for this. Try to > assign a log file which doesn't have write permission. > > For example, if your logs written into echo.log, set it's file > permission to 333 (or 000). > > $chmod 000 axis2.log (this is not recommended though) > > It will redirect output to stderr then, and please raise a jira issue > for this. > > thanks, > Dinesh > -- > http://nethu.org > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2C] Client with xml declaration
Hi Sébastien, This is now available on the head. Set for the respective transport and run your server/client. Please note that you have to obtain an svn checkout from [1]. Regards, Senaka [1] http://svn.apache.org/repos/asf/webservices/axis2/trunk/c > Hi AFAIK, There is a JIRA issue raised against this at [1]. The patch is > not yet applied. This feature will be available on the head as soon as the > patch is applied. Then, You'll merely have to change a setting in > axis2.xml. > Please take a look at [1], once it is resolved this feature will be > available on the head. > > [1] https://issues.apache.org/jira/browse/AXIS2C-666 > > Regards, > Senaka > >> Hello >> >> I can't find how I could tell Axis2/C in client mode to add a xml >> declaration to the request. >> >> I only want my request to start with : >> >> >> Thank you for your help >> >> >> >> - >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2C] Client with xml declaration
Hi AFAIK, There is a JIRA issue raised against this at [1]. The patch is not yet applied. This feature will be available on the head as soon as the patch is applied. Then, You'll merely have to change a setting in axis2.xml. Please take a look at [1], once it is resolved this feature will be available on the head. [1] https://issues.apache.org/jira/browse/AXIS2C-666 Regards, Senaka > Hello > > I can't find how I could tell Axis2/C in client mode to add a xml > declaration to the request. > > I only want my request to start with : > > > Thank you for your help > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Axis2C] Client with xml declaration
Hello I can't find how I could tell Axis2/C in client mode to add a xml declaration to the request. I only want my request to start with : Thank you for your help - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: AW: [AXIS2C] how to set logging to stderr?
Hi Dinesh, and Josef Hi this is a cheap solution, to set permissions etc. The better way is this. As you see, in Linux, the std-streams are mapped to files. If you write to those files they will be written to the respective streams irrespective of what and how you write. You can't prioritize redirects to specific locations. That means it is impossible to write error messages to one and debug messages to another according to the current implementation. However, you should be able to write to several locations with priorities if you build yourself a little extension. This is the process. 1. You'll have to figure out how to write to stdout. That means you have to write to that file that maps to the stdout stream. 2. You will run your axis_based_executable inside another. 3. Read more on how you could use fork and exec to create background processes so that you can run one application inside another. 4. You outer application will barely listen to the stdout stream. 5. Then it is upto your outer application to do the logging. 6. Identification of error/debug etc messages can be done using a regular expression parsing mechanism. Startup Workflow: A - outer_client B - inner_axis_based_client 1. run A 2. A runs B (background) 3. B writes logs to stdout 4. A listens to stdout 5. A writes to log_file, stderror etc. Exit Workflow: A - outer_client B - inner_axis_based_client 1. A catches Ctrl+C 2. A kills B 3. A exits I know that this is so complicated but I don't see any better way. Regards, Senaka > Hi, > > "Stadelmann Josef" <[EMAIL PROTECTED]> writes: > >> Thanks, but as I do not use axis2 simple server ... >> I am jsut using the axiom libs and libs forming the base >> such as axutil and libxml2 etc. >> >> What do I use to redirect output in code? >> axis_log = axutil_log_create(allocator, NULL, NULL); >> this creates an axis2.log under . directory > > AFAIK , there is a no such a way to redirect out put to stdout or > stderr. However I could say you a small workaround for this. Try to > assign a log file which doesn't have write permission. > > For example, if your logs written into echo.log, set it's file > permission to 333 (or 000). > > $chmod 000 axis2.log (this is not recommended though) > > It will redirect output to stderr then, and please raise a jira issue > for this. > > thanks, > Dinesh > -- > http://nethu.org > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: AW: [AXIS2C] how to set logging to stderr?
Hi, "Stadelmann Josef" <[EMAIL PROTECTED]> writes: > Thanks, but as I do not use axis2 simple server ... > I am jsut using the axiom libs and libs forming the base > such as axutil and libxml2 etc. > > What do I use to redirect output in code? > axis_log = axutil_log_create(allocator, NULL, NULL); > this creates an axis2.log under . directory AFAIK , there is a no such a way to redirect out put to stdout or stderr. However I could say you a small workaround for this. Try to assign a log file which doesn't have write permission. For example, if your logs written into echo.log, set it's file permission to 333 (or 000). $chmod 000 axis2.log (this is not recommended though) It will redirect output to stderr then, and please raise a jira issue for this. thanks, Dinesh -- http://nethu.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
AW: [AXIS2C] how to set logging to stderr?
Thanks, but as I do not use axis2 simple server ... I am jsut using the axiom libs and libs forming the base such as axutil and libxml2 etc. What do I use to redirect output in code? axis_log = axutil_log_create(allocator, NULL, NULL); this creates an axis2.log under . directory But to help me debug/trace axis_log = axutil_log_create(allocator, NULL, stdout); sends all my debug and above output to the screen. Now what do I have to use to reconfigure / profile the destination once the code has been built. When recompile and linke is a no go. Question is: is there a way to profile and have more then one destination using this axis2c logger capability? that is to say, during debugging I want to see down to traces level all on screen. so I use stdout and log level trace and during operation I'd like to raise the log level to log error and see error and events above that log level in a axis2.log file Also I'd like to see traces in special cases when enabled by code at run time. in very specific log files. Can I profile this somehow? Thanks and regards Josef.Stadelmann@ axa-winterthur.ch -Ursprüngliche Nachricht- Von: Kaushalye Kapuruge [mailto:[EMAIL PROTECTED] Gesendet: Mittwoch, 16. Januar 2008 10:19 An: Apache AXIS C User List Betreff: Re: [AXIS2C] how to set logging to stderr? Stadelmann Josef wrote: > > I am a newbee regarding the correct use of loggin, > > My question is: what do I have to do to get logging redirected to > sdterr or stdout > instead to a log file such as axis2.log? This as I am not a unix > expert and somehow > on war.path with streams in general :-) > Try to start the simple axis server as follows (if that's your requirement)... ./axis2_http_server -f /dev/stderr -Kau > > Is tere a way to profile this with Axis2C as with the log4j system? > > Josef.Stadelmann@ > axa-winterthur.ch > -- http://blog.kaushalye.org/ http://wso2.org/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [AXIS2C] how to set logging to stderr?
Hi, "Stadelmann Josef" <[EMAIL PROTECTED]> writes: > I am a newbee regarding the correct use of loggin, > > My question is: what do I have to do to get logging redirected to sdterr or > stdout > instead to a log file such as axis2.log? This as I am not a unix expert and > somehow > on war.path with streams in general :-) > > Is tere a way to profile this with Axis2C as with the log4j system? Please follow this tutorial http://wso2.org/library/3041 thanks, Dinesh -- http://nethu.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [AXIS2C] how to set logging to stderr?
Stadelmann Josef wrote: I am a newbee regarding the correct use of loggin, My question is: what do I have to do to get logging redirected to sdterr or stdout instead to a log file such as axis2.log? This as I am not a unix expert and somehow on war.path with streams in general :-) Try to start the simple axis server as follows (if that's your requirement)... ./axis2_http_server -f /dev/stderr -Kau Is tere a way to profile this with Axis2C as with the log4j system? Josef.Stadelmann@ axa-winterthur.ch -- http://blog.kaushalye.org/ http://wso2.org/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[AXIS2C] how to set logging to stderr?
I am a newbee regarding the correct use of loggin, My question is: what do I have to do to get logging redirected to sdterr or stdout instead to a log file such as axis2.log? This as I am not a unix expert and somehow on war.path with streams in general :-) Is tere a way to profile this with Axis2C as with the log4j system? Josef.Stadelmann@ axa-winterthur.ch
AW: AW: execute axiom_document_free(om_document, env); // and my hash_table key/val pairs are gone
-Ursprüngliche Nachricht-
Von: Senaka Fernando [mailto:[EMAIL PROTECTED]
Gesendet: Dienstag, 15. Januar 2008 18:59
An: Apache AXIS C User List
Cc: [EMAIL PROTECTED]
Betreff: Re: AW: execute axiom_document_free(om_document, env); // and
my hash_table key/val pairs are gone
Hi Josef,
The builder & document logic is as follows. The document will always have
a builder and the builder is responsible for creating the document. That
is why it doesn't make sense to free only the document. Reconstructing a
document would involve reconstructing a builder.
It would be better if you could attach the stack trace from your debugger
to diagnose the exact problem, but as far as I know, when you create a
copy of your hash table, the values inside it are simply passed as shallow
copies. That means, your duplicated string resides on the heap and the
hash will have a reference. When you copy your hash, the old as well as
the new one will have the same reference. Then, when you free one, the
other would rather be having a dangling pointer.
The workaround is to change the way you duplicate your hash and get onto
safe grounds. You'd create your hash copy from scratch and iterate through
your original hash and add element by element to the new hash. You can
then do the duplication of strings and create deep copies. This can be
sort of a tedious process. You can get help by reading through the hash.c
source file and see how the hash is copied.
There might not be a bug in the existing implementation in terms of the
way the hashes are copied, because we can't force a user to always
allocate objects on the heap because shallow copies are much faster. Thus,
if a user wishes to do heap allocations and at the same time to duplicate
hashes, he will rather have to override the default behavior.
I believe this might solve your issue. But, I can't guarantee as I have
not seen the exact stack trace or the point at which it breaks.
++> Hi Fernando,
you'r absolut correct, I went into axutil_hash code and it is as you say;
copy a hash table is not a deep copy but a shalow copy and dangling is very
likely to occure with multiple hash tables;
maybe we have some day axutil_hash_copy_deep() to overcome such problems.
It is also nonsens from a OO point of view, given a hash_table is beeing
seen as an instance of an class in which case freeing one hash obj
should/would not touche the other's hash obj's strings (key/val's)
Thanks for the fine answer, I have my problem under control now, and it
is as it is, if you are aware about something (say if it is documented)
best by example code which did not just run throug an editor, then your
most of the time fine. But thanks again.
Josef
Hi Devs,
Please correct me if this should not be the desired behavior. And, if it
is not, this is invariably a bug in the way we copy hashes. Also, please
note that it is documented that axutil_hash_copy() creates a shallow copy.
And, I have assumed that the documentation justifies the logic I speak of.
However, I believe that even if this logic is justifiable it is strongly
recommended that we should introduce another method
axutil_hash_copy_deep() that does a deep copy instead of a shallow copy.
What do you say?
Regards,
Senaka
> Your call correct, it works now but shows a new problem, that of
> freeing two of the 4 hash tables later.
>
> freeing the om_document with
> axiom_stax_builder_free(om_builder,env);
> seams to work,
>
>
> But freeing a builder when you think you have to free the om_document
> is not so obvious; but you are righth the creator of my om_document
> is the axiom_stax_builder with its get_document.
>
> However this allone does not solve the problem. They still exists.
>
> Until one really does a
>
> fldval = (a *) AXIS2_MALLOC(env->allocator, sizeof(a));
> fldval->value = axutil_strdup(env,getFLDVAL(ele, env));
> fldnam =axutil_strdup(env,getFLDNAM(ele, env));
>
> and used the axutil_strdup function; fldval and fldnam are then
> added to the hash tables and I just hope that freeing the hash
> tables deallocates this string space too;
>
> Here I have my doubts because when I do
>
> axutil_hash_free(htwsinp,env);
> axutil_hash_free(htwsold,env);
> //axutil_hash_free(htGWKSP,env);
> //axutil_hash_free(htwsout,env);
>
>
> only htwsinp and htwsold can bee freed, while htGWKSP and htwsout
> result in a exception asking me to break or continue in VS 2005
>
> So please here is the code used to make htGWKSP
>
> /**
> puts htwsinp hash table into htGWKSP, does like obbput in CORBA world
> the ponter to the golbal hash table htGWKSP is updated
> **/
> axis2_bool_t AXIS2_CALL
> axawl_put(const axutil_hash_t *htwsinp,
> const axutil_env_t *env,
> const axutil_hash_t **pphtGWKSP) //!< load Spin
> elements into global
> workspace
> {
> axutil_hash_t *htGWKSP = NULL;
> axutil_hash_index_t *hi;
>
> const void *key
Re: Strange REST Parsing
Hi Brain, "Brian McQueen" <[EMAIL PROTECTED]> writes: > http://www.w3.org/2003/05/soap-envelope";> > > > http://ws.apache.org/axis2/services/replicate";> > qid1 > hostname1 > d6ge5gyrgj4 > > > I modified echo sample to echo back the node it receives. I used following commands curl http://localhost:9090/axis2/services/echo/echoString?qid=qid1\&hostname=hostname1\&repl_id=d6ge5gyrgj4 I got this as the response qid1hostname1d6ge5gyrgj4 then I used following command curl http://localhost:9090/axis2/services/echo/echoString?qid=qid1\&repl_id=d6ge5gyrgj4\&hostname=hostname1 and response is qid1d6ge5gyrgj4hostname1 as far as I can see , there is a no such an alphabetical ordering in REST parsing or did I miss something here? thanks, Dinesh -- http://nethu.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
