Re: Why Axis2C ?
Hi Friends, Can any of you answer 1. Why should we use Axis2C when we have other tools like gSoap? The choice is yours. And the choice should be based on your requirements. You should look for the technical factor as well as other factors such as license. 2. What are the differentiating factors between Axis2C and gSoap? Architecture, design, implementation and the number of specs supported. 3. Isn't Axis2C heavier compared to gSoap, with its Axiom architectire? If no, why? If yes, what other advantages of Axiom is making us use it with Axis2C? [In terms of memory usage, efficiency, speed, etc.] There has been no formal evaluation on performance or memory footprint AFAIK. We believe AXIOM to be one of the key factors driving Axis2/C's performance. In addition to that, the number of specs supported too are empowered by the architecture that bulds on AXIOM. Thanks, Samisa... Eagerly waiting for your reply. vamsi krishna wrote: Hi Friends, Can any of you answer 1. Why should we use Axis2C when we have other tools like gSoap? 2. What are the differentiating factors between Axis2C and gSoap? 3. Isn't Axis2C heavier compared to gSoap, with its Axiom architectire? If no, why? If yes, what other advantages of Axiom is making us use it with Axis2C? [In terms of memory usage, efficiency, speed, etc.] Eagerly waiting for your reply. Vamsi, IIIT-Hyd. No virus found in this incoming message. Checked by AVG. Version: 8.0.101 / Virus Database: 270.4.3/1527 - Release Date: 6/30/2008 6:07 PM -- Samisa Abeysinghe Director, Engineering; WSO2 Inc. http://www.wso2.com/ - The Open Source SOA Company - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
rampart and message with no parameter
Dear, Rampart has been successfully used for messages with at least one parameter. To be precise, sec_echo has been used with scenario3. However, a problem arises when a message without parameter has to sent, indeed, in this case, the body is empty and rampart refuses to send the message because it complains that no node has to be encrypted. Does anyone know how to tackle this problem ? One ugly hack would be to add a fake parameter, but one has to modify the wsdl. Frederic __ --- NOTICE --- This email and any attachments are confidential and are intended for the addressee only. If you have received this message by mistake, please contact us immediately and then delete the message from your system. You must not copy, distribute, disclose or act upon the contents of this email. Personal and corporate data submitted will be used in a correct, transparent and lawful manner. The data collected will be processed in paper or computerized form for the performance of contractual and lawful obligations as well as for the effective management of business relationship. The data processor is Telsey S.p.A. The data subject may exercise all the rights set forth in art. 7 of Law by Decree 30.06.2003 n. 196 as reported in the following url http://www.telsey.com/privacy.asp. __ 798t8RfNa6Dl8Ilf - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: rampart and message with no parameter
Frederic Heem wrote: Dear, Rampart has been successfully used for messages with at least one parameter. To be precise, sec_echo has been used with scenario3. However, a problem arises when a message without parameter has to sent, indeed, in this case, the body is empty and rampart refuses to send the message because it complains that no node has to be encrypted. Does anyone know how to tackle this problem ? One ugly hack would be to add a fake parameter, but one has to modify the wsdl. I think this is not a Rampart problem, rather an Axis2/C feature. If the payload is empty, Axis2/C thinks that there is something wrong. The rationale for this design was that, if there is no payload to send, why send an empty message. What are the semantics of you sending this message? What does that message do? I am trying to understand the meaning of such an empty message. Samisa... Frederic __ --- NOTICE --- This email and any attachments are confidential and are intended for the addressee only. If you have received this message by mistake, please contact us immediately and then delete the message from your system. You must not copy, distribute, disclose or act upon the contents of this email. Personal and corporate data submitted will be used in a correct, transparent and lawful manner. The data collected will be processed in paper or computerized form for the performance of contractual and lawful obligations as well as for the effective management of business relationship. The data processor is Telsey S.p.A. The data subject may exercise all the rights set forth in art. 7 of Law by Decree 30.06.2003 n. 196 as reported in the following url http://www.telsey.com/privacy.asp. __ 798t8RfNa6Dl8Ilf - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] No virus found in this incoming message. Checked by AVG. Version: 8.0.101 / Virus Database: 270.4.3/1528 - Release Date: 7/1/2008 7:26 AM -- Samisa Abeysinghe Director, Engineering; WSO2 Inc. http://www.wso2.com/ - The Open Source SOA Company - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Why Axis2C ?
On Tue, Jul 1, 2008 at 11:37 AM, vamsi krishna [EMAIL PROTECTED] wrote: Hi Friends, Can any of you answer 1. Why should we use Axis2C when we have other tools like gSoap? 2. What are the differentiating factors between Axis2C and gSoap? There was a rough comparison between gSoap and Axis2/C some time back in the same list. -Rajika 3. Isn't Axis2C heavier compared to gSoap, with its Axiom architectire? If no, why? If yes, what other advantages of Axiom is making us use it with Axis2C? [In terms of memory usage, efficiency, speed, etc.] Eagerly waiting for your reply. Vamsi, IIIT-Hyd. -- comp.lang.c - http://groups.google.com/group/comp.lang.c/topics
Re: rampart and message with no parameter
Hi, If I'm right, most probably I'm. The problem is that in your policy you are saying to encrypt the message body i.e sp:EncryptedParts sp:Body/ /sp:EncryptedParts. But you don't have a message body. So it is perfectly normal to get this error. If this is the case please remove that part from the policy. Supun.. On Wed, Jul 2, 2008 at 6:55 AM, Samisa Abeysinghe [EMAIL PROTECTED] wrote: Frederic Heem wrote: Dear, Rampart has been successfully used for messages with at least one parameter. To be precise, sec_echo has been used with scenario3. However, a problem arises when a message without parameter has to sent, indeed, in this case, the body is empty and rampart refuses to send the message because it complains that no node has to be encrypted. Does anyone know how to tackle this problem ? One ugly hack would be to add a fake parameter, but one has to modify the wsdl. I think this is not a Rampart problem, rather an Axis2/C feature. If the payload is empty, Axis2/C thinks that there is something wrong. The rationale for this design was that, if there is no payload to send, why send an empty message. What are the semantics of you sending this message? What does that message do? I am trying to understand the meaning of such an empty message. Samisa... Frederic __ --- NOTICE --- This email and any attachments are confidential and are intended for the addressee only. If you have received this message by mistake, please contact us immediately and then delete the message from your system. You must not copy, distribute, disclose or act upon the contents of this email. Personal and corporate data submitted will be used in a correct, transparent and lawful manner. The data collected will be processed in paper or computerized form for the performance of contractual and lawful obligations as well as for the effective management of business relationship. The data processor is Telsey S.p.A. The data subject may exercise all the rights set forth in art. 7 of Law by Decree 30.06.2003 n. 196 as reported in the following url http://www.telsey.com/privacy.asp. __ 798t8RfNa6Dl8Ilf - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] No virus found in this incoming message. Checked by AVG. Version: 8.0.101 / Virus Database: 270.4.3/1528 - Release Date: 7/1/2008 7:26 AM -- Samisa Abeysinghe Director, Engineering; WSO2 Inc. http://www.wso2.com/ - The Open Source SOA Company - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Am I right?
i Friends, What I understood about AXIOM is this... please tell me if i am right... 1. Axiom is a linked list which is capable of holding the XML document more conveniently as it has members like attributes, namespaces, etc. Right. The linked list contains axiom_node_t structure. These nodes can contain data like axiom_element_t, axiom_text_t etc. 2. These members of the linked list are used to pin point the required node or required attribute of the node with out parsing the whole structure constructed, when ever needed. [This capability of pin pointing is called PULL PARSING technique] Right. After building this model or tree the pin pointing is more like in DOM. 3. We make use of libxml2 or guththilla parsers to construct the XML document [which is a DOM structure]. We call this Document oject model om. 4. This XML document acts as an input to construct the AXIOM tree which can be pull parsed. [AXIOM tree is a wrapper around libxml2's XML document, so that it can be pull parsed] I'm not sure what you are saying here. What happens is the XML document is pull parsed by guththila or libxml2 and the values returned by this pull parsing is used to construct the tree or the linked list. The main difference is that the XML document is parsed on demand with of the user. So the XML document can be parsed halfway and the model will be built halfway. In other parsing technologies we parse the whole XML document at once. Supun.. Am I right in understating the concepts of AXIOM and pull parsing? Please correct me if I am not correct. Vamsi, IIIT-Hyd.
