Re: changes to the axutil log functions
Hi, You can make axis to do logging the way you need w/o making changes in the axis code. Have a look at util/src/log.c. Function axutil_log_impl_write_to_file() is used to do logging. All you need to do is to make your own shared library with only one function: axutil_log_impl_write_to_file(). The function has to have the same signature as the one in util/src/log.c. Then use LD_PRELOAD to preload this new library when starting you application. That's it. The axis code will invoke you implementation of axutil_log_impl_write_to_file(). Your proposed fix to pass a FILE* instead of a filename has the same restrictions as the current code. It makes the client do logging the way library wants. The library already provides the interface to do logging the way the client needs. You can allocate an instance of axutil_log_t and set ops.free and ops.write to your own functions. The you can replace the log object in your env struct with your customized log object. Unfortunately, axis doesn't use ops.write. The correct fix would be to change util/src/log.c to use ops.write() and ops.free(). I considered providing a patch, but finally decided not to (because the library maintainers dont seem to be willing to apply patches) and used the LD_PRELOAD method described above. BR, Dmitry Haszlakiewicz, Eric wrote: I have a need to use axis within an existing system that has it's own ways of opening/closing/rotating logs and I've found the existing axis log interfaces to be a bit lacking. I have some patches, but before I submit a issue in jira I wanted to run the changes past some people to see if what I'm doing makes sense. There are two issues that I'm fixing: 1) the log functions don't keep track of whether the filedescriptor was opened by axis, so if you create a env using axutil_env_create() it ends up closing stderr when you try to set a new log file. 2) There's no way to tell axis to log to a filedescriptor rather than to a named file. I added two functions to axutil_log_default.h: One to create a axutil_log_t using an existing FILE * as returned from fopen: AXIS2_EXTERN axutil_log_t *AXIS2_CALL axutil_log_create_fp( axutil_allocator_t *allocator, axutil_log_ops_t *ops, void *stream, int close_stream); I also factored out a static axutil_log_create_common() function, which is used by both axutil_log_create_fp() and the original axutil_log_create(). And, one to switch the FILE pointer on an existing log structure: AXIS2_EXTERN void AXIS2_CALL axutil_log_set_stream( axutil_allocator_t *allocator, axutil_log_t *log, void *stream, int close_stream); In both of these, the close_stream flag indicates whether axis is allowed to close the stream when a new one is set or when the log structure is cleaned up. That is stored in a new field in the axutil_log_impl structure. Does this seem reasonable? Should I send the full patch to the list? eric (btw, I created a couple of other jira issues (AXIS2C-1271, AXIS2C-1280) w/ patches attached. About how long can I expect before they are applied?) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: changes to the axutil log functions
On Wed, 2008-11-05 at 11:27 +0300, Dmitry Goncharov wrote: I considered providing a patch, but finally decided not to (because the library maintainers dont seem to be willing to apply patches) and used the LD_PRELOAD method described above. We apply the patches immediately which solves critical issues. The patches you have sent may be critical fixes for you but may not be for the community. Actually these patches will be applied when developers get time to fix Jiras, most probably for a major release. So we always encourage community to send patches, because at some time they will be applied if they improve Axis2/C code base. BR, Dmitry Haszlakiewicz, Eric wrote: I have a need to use axis within an existing system that has it's own ways of opening/closing/rotating logs and I've found the existing axis log interfaces to be a bit lacking. I have some patches, but before I submit a issue in jira I wanted to run the changes past some people to see if what I'm doing makes sense. There are two issues that I'm fixing: 1) the log functions don't keep track of whether the filedescriptor was opened by axis, so if you create a env using axutil_env_create() it ends up closing stderr when you try to set a new log file. 2) There's no way to tell axis to log to a filedescriptor rather than to a named file. I added two functions to axutil_log_default.h: One to create a axutil_log_t using an existing FILE * as returned from fopen: AXIS2_EXTERN axutil_log_t *AXIS2_CALL axutil_log_create_fp( axutil_allocator_t *allocator, axutil_log_ops_t *ops, void *stream, int close_stream); I also factored out a static axutil_log_create_common() function, which is used by both axutil_log_create_fp() and the original axutil_log_create(). And, one to switch the FILE pointer on an existing log structure: AXIS2_EXTERN void AXIS2_CALL axutil_log_set_stream( axutil_allocator_t *allocator, axutil_log_t *log, void *stream, int close_stream); In both of these, the close_stream flag indicates whether axis is allowed to close the stream when a new one is set or when the log structure is cleaned up. That is stored in a new field in the axutil_log_impl structure. Does this seem reasonable? Should I send the full patch to the list? eric (btw, I created a couple of other jira issues (AXIS2C-1271, AXIS2C-1280) w/ patches attached. About how long can I expect before they are applied?) - 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]
[jira] Assigned: (AXIS2C-1285) axis2c doesn't build on NetBSD
[ https://issues.apache.org/jira/browse/AXIS2C-1285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjaya Ratnaweera reassigned AXIS2C-1285: -- Assignee: Sanjaya Ratnaweera axis2c doesn't build on NetBSD -- Key: AXIS2C-1285 URL: https://issues.apache.org/jira/browse/AXIS2C-1285 Project: Axis2-C Issue Type: Bug Components: build system (Unix/Linux) Affects Versions: Current (Nightly) Environment: NetBSD 4 Reporter: Eric Haszlakiewicz Assignee: Sanjaya Ratnaweera Attachments: axis_netbsd.diff Original Estimate: 2h Remaining Estimate: 2h Axis2/c doesn't build on NetBSD due to a variety of compile errors. The attached patch corrects this. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
printing parts of a node
Hello! I want to print the parameter names in a node and not the parameter values. For example: param11/param1param23/param2 I want to print or get the hold of: param1 param2 but not 1 and 3 Does anyone know how this can be done? /Indra - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (AXIS2C-1272) Axis2C 1.5.0 does not build in OS X
[ https://issues.apache.org/jira/browse/AXIS2C-1272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjaya Ratnaweera resolved AXIS2C-1272. Resolution: Fixed Fix Version/s: Current (Nightly) Committed fix to the SVN head. Thanks Peter for the solution. Axis2C 1.5.0 does not build in OS X --- Key: AXIS2C-1272 URL: https://issues.apache.org/jira/browse/AXIS2C-1272 Project: Axis2-C Issue Type: Bug Components: build system Affects Versions: 1.5.0 Environment: OS: OS X 10.5.5 compiler: i686-apple-darwin9-gcc-4.0.1 (GCC) 4.0.1 (Apple Inc. build 5484) Reporter: Stephan Zednik Assignee: Sanjaya Ratnaweera Fix For: Current (Nightly) Attachments: config.log, make.out followed the standard configured and compile commands of ./configure --prefix=$AXIS2C_HOME; make; make install; compile stage died compiling dir_handler with the following error. /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I../include-g -O2 -D_LARGEFILE64_SOURCE -ansi -Wal\ l -Werror -Wno-implicit-function-declaration -D_GNU_SOURCE -Wno-long-double -MT dir_handler.lo -MD -MP -MF .deps/dir_handler.Tpo\ -c -o dir_handler.lo dir_handler.c gcc -DHAVE_CONFIG_H -I. -I.. -I../include -g -O2 -D_LARGEFILE64_SOURCE -ansi -Wall -Werror -Wno-implicit-function-declaration -D\ _GNU_SOURCE -Wno-long-double -MT dir_handler.lo -MD -MP -MF .deps/dir_handler.Tpo -c dir_handler.c -fno-common -DPIC -o .libs/di\ r_handler.o dir_handler.c:326: error: conflicting types for 'file_select' dir_handler.c:38: error: previous declaration of 'file_select' was here make[5]: *** [dir_handler.lo] Error 1 make[4]: *** [all-recursive] Error 1 make[3]: *** [all-recursive] Error 1 make[2]: *** [all] Error 2 make[1]: *** [all-recursive] Error 1 make: *** [all] Error 2 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (AXIS2C-1285) axis2c doesn't build on NetBSD
[ https://issues.apache.org/jira/browse/AXIS2C-1285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjaya Ratnaweera resolved AXIS2C-1285. Resolution: Fixed Fix Version/s: Current (Nightly) Patch applied and tested. thanks Eric for the patch. axis2c doesn't build on NetBSD -- Key: AXIS2C-1285 URL: https://issues.apache.org/jira/browse/AXIS2C-1285 Project: Axis2-C Issue Type: Bug Components: build system (Unix/Linux) Affects Versions: Current (Nightly) Environment: NetBSD 4 Reporter: Eric Haszlakiewicz Assignee: Sanjaya Ratnaweera Fix For: Current (Nightly) Attachments: axis_netbsd.diff Original Estimate: 2h Remaining Estimate: 2h Axis2/c doesn't build on NetBSD due to a variety of compile errors. The attached patch corrects this. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: changes to the axutil log functions
Dmitry Goncharov wrote: I considered providing a patch, but finally decided not to (because the library maintainers dont seem to be willing to apply patches) and used the LD_PRELOAD method described above. This is an incorrect statement. When were you told that we are not willing to accept patches? Have you ever submitted Jiras with patches? Samisa... - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: changes to the axutil log functions
This is what i though when submitted a patch and it wasn't applied. Not intended to insult anybody. See jira issue 1258 BR, Dmitry Samisa Abeysinghe wrote: Dmitry Goncharov wrote: I considered providing a patch, but finally decided not to (because the library maintainers dont seem to be willing to apply patches) and used the LD_PRELOAD method described above. This is an incorrect statement. When were you told that we are not willing to accept patches? Have you ever submitted Jiras with patches? Samisa... - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: printing parts of a node
[EMAIL PROTECTED] wrote: Hello! I want to print the parameter names in a node and not the parameter values. For example: param11/param1param23/param2 I want to print or get the hold of: param1 param2 but not 1 and 3 Does anyone know how this can be done? This can be done using the serialize sub tree method. Please have a look at the node header file. Samisa... /Indra - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Internal Virus Database is out of date. Checked by AVG - http://www.avg.com Version: 8.0.175 / Virus Database: 270.8.5/1759 - Release Date: 10/31/2008 4:10 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]
RE: printing parts of a node
I tried to understand how I could use the serialize sub tree method but I don't... I know how to get the node values but I also need to get the node name, how can I do this? I'm very thankful for a reply Regards Indra -Original Message- From: Samisa Abeysinghe [mailto:[EMAIL PROTECTED] Sent: den 5 november 2008 15:57 To: Apache AXIS C Developers List Subject: Re: printing parts of a node [EMAIL PROTECTED] wrote: Hello! I want to print the parameter names in a node and not the parameter values. For example: param11/param1param23/param2 I want to print or get the hold of: param1 param2 but not 1 and 3 Does anyone know how this can be done? This can be done using the serialize sub tree method. Please have a look at the node header file. Samisa... /Indra - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Internal Virus Database is out of date. Checked by AVG - http://www.avg.com Version: 8.0.175 / Virus Database: 270.8.5/1759 - Release Date: 10/31/2008 4:10 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: What are the configurable ws-security parameters for incoming message
Thanks! But my question is really this: In WS-Policy, what parameters need to be or can be configured for incoming message (the response message from a client point of view)? I don't see much document in rampart/c site. From a user point of view, I would like to see something like soapUI in which the configurable parameters for WS-security are very clear. Is there anything like that in rampart/c in a configuration file? Thanks again! Vivian --- On Tue, 11/4/08, Samisa Abeysinghe [EMAIL PROTECTED] wrote: From: Samisa Abeysinghe [EMAIL PROTECTED] Subject: Re: What are the configurable ws-security parameters for incoming message To: Apache AXIS C Developers List axis-c-dev@ws.apache.org Cc: [EMAIL PROTECTED], [EMAIL PROTECTED] Date: Tuesday, November 4, 2008, 10:59 PM Rampart/C makes use of WS-Policy for configuring how it behaves. Samisa... Vivian Wang wrote: Hi, I am trying to use rampart/c along with axis2/c to support WS-security. Just wonder, what are the configurable ws-security parameters for incoming message, especially from a web service client point of view, which means, as a web service client, what can be configured to decrypt/interpret the response message from the web server. I've read through the manuals and also gone through the examples, but still I am afraid I don't have a complete picture about what can be configured. Is there any detailed document for this? I was also looking at soapUI, a free tool for web service testing, which also supports WS-security. In their manual, they have the following statements: Incoming WSS configurations are used to process incoming messages (responses, MockRequest and monitor requests/response) and decrypt/validate their encrypted/signed content. Since the WS-Security headers of an incoming message contain most of the information required to decrypt or validate a message, the only configuration needed by soapUI is which keystores that contain referenced keys and certificates for decryption and signature validation. Is this statement also true to rampart/c? I mean, the only configuration one need to do is which keystores that contain referenced keys and certificates for decryption and signature validation? Thanks much in advance! Vivian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Internal Virus Database is out of date. Checked by AVG - http://www.avg.com Version: 8.0.175 / Virus Database: 270.8.5/1759 - Release Date: 10/31/2008 4:10 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: What are the configurable ws-security parameters for incoming message
On Wed, 2008-11-05 at 10:30 -0800, Vivian Wang wrote: Thanks! But my question is really this: In WS-Policy, what parameters need to be or can be configured for incoming message (the response message from a client point of view)? I don't see much document in rampart/c site. From a user point of view, I would like to see something like soapUI in which the configurable parameters for WS-security are very clear. Is there anything like that in rampart/c in a configuration file? https://wso2.org/library/2702 Thanks again! Vivian --- On Tue, 11/4/08, Samisa Abeysinghe [EMAIL PROTECTED] wrote: From: Samisa Abeysinghe [EMAIL PROTECTED] Subject: Re: What are the configurable ws-security parameters for incoming message To: Apache AXIS C Developers List axis-c-dev@ws.apache.org Cc: [EMAIL PROTECTED], [EMAIL PROTECTED] Date: Tuesday, November 4, 2008, 10:59 PM Rampart/C makes use of WS-Policy for configuring how it behaves. Samisa... Vivian Wang wrote: Hi, I am trying to use rampart/c along with axis2/c to support WS-security. Just wonder, what are the configurable ws-security parameters for incoming message, especially from a web service client point of view, which means, as a web service client, what can be configured to decrypt/interpret the response message from the web server. I've read through the manuals and also gone through the examples, but still I am afraid I don't have a complete picture about what can be configured. Is there any detailed document for this? I was also looking at soapUI, a free tool for web service testing, which also supports WS-security. In their manual, they have the following statements: Incoming WSS configurations are used to process incoming messages (responses, MockRequest and monitor requests/response) and decrypt/validate their encrypted/signed content. Since the WS-Security headers of an incoming message contain most of the information required to decrypt or validate a message, the only configuration needed by soapUI is which keystores that contain referenced keys and certificates for decryption and signature validation. Is this statement also true to rampart/c? I mean, the only configuration one need to do is which keystores that contain referenced keys and certificates for decryption and signature validation? Thanks much in advance! Vivian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Internal Virus Database is out of date. Checked by AVG - http://www.avg.com Version: 8.0.175 / Virus Database: 270.8.5/1759 - Release Date: 10/31/2008 4:10 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] - 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]
Help needed with Axiom Navigator
Hi, I have an issue where I need to use the Axiom Navigator class in Axis2/C. I have read the Axiom Tutorial but still am not very comfortable using the Navigator. I also found that the Axis2/C does not use the same anywhere in the project. So if someone could give me some sample code that may guide me in how to use this class to travesrse an Om node in a C program would really be useful. Thanks, Shivam.
