[jira] Assigned: (AXIS2C-1338) make install overly eager

[ https://issues.apache.org/jira/browse/AXIS2C-1338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjaya Ratnaweera reassigned AXIS2C-1338: -- Assignee: Sanjaya Ratnaweera make install overly eager

Operation and message level policies in client side

Hi devs, In order to fix https://issues.apache.org/jira/browse/AXIS2C-619 we need to change the following function signature in the svc_client API. AXIS2_EXTERN axis2_status_t AXIS2_CALL axis2_svc_client_set_policy( axis2_svc_client_t * svc_client, const axutil_env_t * env,

Re: Axis2- Hi can i use axis2/c for developing webservices which are deployed to embedded systems.

Yes we encourage you to use it in embedded systems. If you have problems send them to the list, so we can share your experience. Thanks, -Manjula. On Thu, 2009-01-29 at 10:29 +0500, Supun Kamburugamuva wrote: As Axis2/C development community, we haven't herd of Axis2/C used in embedded

Re: Operation and message level policies in client side

How about adding another method with a name like axis2_svc_client_set_policy_with_type. We can have a default value for axis2_policy_types in the first method. Supun. On Thu, Jan 29, 2009 at 2:49 PM, Manjula Peiris manj...@wso2.com wrote: Hi devs, In order to fix

[jira] Commented: (AXIS2C-1337) Fails to compile if chdir and/or fread declared with warn_unused_result

[ https://issues.apache.org/jira/browse/AXIS2C-1337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12668471#action_12668471 ] Soren Hansen commented on AXIS2C-1337: -- You should use perror instead of

Re: Axis2- Hi can i use axis2/c for developing webservices which are deployed to embedded systems.

hi You'll need some optimization in axiom level to get it working on an embeded environment. -Rajika On Wed, Jan 28, 2009 at 11:12 PM, koteswara Bellamkonda bbellamko...@gmail.com wrote: Hi, I am looking to deploy WebServices developed using apache axis2/c to embedded systems. is it works

guththila_next_char clarification needed

Hi In the 'guththila_next_char' method, whenever a character is being retrieved from Guththila's internal char buffers, a check is being made to see if it has a positive value: e.g. 'return c = 0 ? c : -1;' (guththila_xml_parser.c, lines 1522, 1537, 1616, 1632) -1 is interpreted as an

Re: Operation and message level policies in client side

On Thu, Jan 29, 2009 at 11:23 PM, Manjula Peiris manj...@wso2.com wrote: On Thu, 2009-01-29 at 15:45 +0500, Supun Kamburugamuva wrote: How about adding another method with a name like axis2_svc_client_set_policy_with_type. We can have a default value for axis2_policy_types in the first

Re: guththila_next_char clarification needed

Guthtila is written assuming ASCHII characters. So it is not possible to get negative characters. If Guththila gets negative charactes, it means the XML stream has ended or contains invalid characters. Anyway what do you mean by non-ASCII characters? Do you mean binary? Supun. On Thu, Jan 29,

Re: guththila_next_char clarification needed

Hi By non-ASCII I meant characters with a value greater than 127. The response that Guththila couldn't parse completely had the french small letter e with acute accent; when retrieved from Guththila's internal buffers (and stored in an 'int'), it would yield a negative value. While googling