Re: rampart and message with no parameter
Samisa Abeysinghe 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. The web service being developed has many messages, some of them doesn't have any parameters, e.g GetDeviceList() . In this case, the body is empty but the header is not empty and contains the action which is used by the server to dispatch this message. Therefore, it makes sense to send a message with an empty body. Without using rampart, axis2c doesn't complain about the empty body and send the message which is interpreted by the server correctly. Regards, 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 -- --- Frederic Heem - Innovation Hub Senior Engineer Telsey Telecommunications S.p.A. email: [EMAIL PROTECTED] Departement: Innovation Hub UK: Vanguard Centre, ATU II, Unit 8Sir William Lyons Road University of Warwick Science ParkCV4 7EZ Coventry Tel. direct phone (+39) 0422 377760 Central Bureau Viale dell'Industria, 1 31055 Quinto di Treviso (TV) - Italy Tel.: +39 0422470840 Fax: +39 0422470920 Web: www.telsey.com - 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]
WSDL2C and fault
Dear, Is it possible to generate a SOAP fault with the code generated by WSDL2C ? A fault can be generated for an In-Only message or only for In-Out message ? Best Regards, Frederic Heem __ --- 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]
valgrind and memory leaks
Hi folks, Valgrind 3.3 is being mainly used to track memory leak, unfortunately, it doesn't catch memory allocated by the macro AXIS2_MALLOC, probably due to the fact that it uses a function pointer. Modifying the three macro as follows solves this problem and memory leaks can be finally detected during development. #if 0 #define AXIS2_MALLOC(allocator, size) \ ((allocator)-malloc_fn(allocator, size)) #define AXIS2_REALLOC(allocator, ptr, size) \ ((allocator)-realloc(allocator, ptr, size)) #define AXIS2_FREE(allocator, ptr) \ ((allocator)-free_fn(allocator, ptr)) #else #include stdlib.h #define AXIS2_MALLOC(allocator, size) \ malloc(size) #define AXIS2_REALLOC(allocator, ptr, size) \ realloc(ptr, size) #define AXIS2_FREE(allocator, ptr) \ free(ptr) #endif Best Regards, Frederic Heem __ --- 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: valgrind and memory leaks
Dinesh Premalal wrote: Hi Frederic, Frederic Heem [EMAIL PROTECTED] writes: Hi folks, Valgrind 3.3 is being mainly used to track memory leak, unfortunately, it doesn't catch memory allocated by the macro AXIS2_MALLOC, probably due to the fact that it uses a function pointer. Modifying the three macro as follows solves this problem and memory leaks can be finally detected during development. If we remove the function pointers as you suggest, it eliminates our design goal with function pointers. We used those function pointers in order to use other memory handling mechanisms other than malloc. As an example we use apr_pools underneath in mod_axis2 memory handling. Other thing is malloc may not be portable across different platforms. Therefore I don't think it is a good idea to remove those function pointers. thanks, Dinesh The changes I propose must not be commit to subversion, it is just a kludge for this valgrind bug. However, this change can used only during development to catch memory leak. Frederic -- --- Frederic Heem - Innovation Hub Senior Engineer Telsey Telecommunications S.p.A. email: [EMAIL PROTECTED] Departement: Innovation Hub UK: Vanguard Centre, ATU II, Unit 8Sir William Lyons Road University of Warwick Science ParkCV4 7EZ Coventry Tel. direct phone (+39) 0422 377760 Central Bureau Viale dell'Industria, 1 31055 Quinto di Treviso (TV) - Italy Tel.: +39 0422470840 Fax: +39 0422470920 Web: www.telsey.com __ --- 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
