[jira] Commented: (AXIS2C-1277) Must use empty header in request

[ https://issues.apache.org/jira/browse/AXIS2C-1277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12641736#action_12641736 ] Damitha Kumarage commented on AXIS2C-1277: -- I could reproduce this. Will fix asap

[jira] Created: (AXIS2C-1279) A soap fault of No Error return

A soap fault of No Error return - Key: AXIS2C-1279 URL: https://issues.apache.org/jira/browse/AXIS2C-1279 Project: Axis2-C Issue Type: Bug Reporter: Damitha Kumarage A soap fault with reason No

[jira] Updated: (AXIS2C-1279) A soap fault of No Error return

[ https://issues.apache.org/jira/browse/AXIS2C-1279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damitha Kumarage updated AXIS2C-1279: - Description: A soap fault with reason No Error return for certain errors at server

[jira] Updated: (AXIS2C-1277) Must use empty header in request

[ https://issues.apache.org/jira/browse/AXIS2C-1277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damitha Kumarage updated AXIS2C-1277: - Attachment: soap_header.c.diff File attached has the desired solution. If there is no

[jira] Created: (AXIS2C-1280) Headers don't compile with warnings turned on due to not entirely valid prototypes.

Headers don't compile with warnings turned on due to not entirely valid prototypes. --- Key: AXIS2C-1280 URL: https://issues.apache.org/jira/browse/AXIS2C-1280 Project:

[jira] Updated: (AXIS2C-1280) Headers don't compile with warnings turned on due to not entirely valid prototypes.

[ https://issues.apache.org/jira/browse/AXIS2C-1280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Haszlakiewicz updated AXIS2C-1280: --- Attachment: axis_headers.diff Headers don't compile with warnings turned on due to

[jira] Commented: (AXIS2C-1277) Must use empty header in request

[ https://issues.apache.org/jira/browse/AXIS2C-1277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12641979#action_12641979 ] Ruth Struck commented on AXIS2C-1277: - Thank you for the quick response. I will let

APIs for ws-security paramenters

Hi there,   I am planning to use rampart-c as a module in my axis2/c to support ws-security in a web service client application. I know I can configure the policy files in the client repository. My question is that if all these variables/parameters can be set programmably using some sort of

Re: APIs for ws-security paramenters

Hi, Uthaiyashankar,   Thanks much for the info. I am a bit surprised that we can only set the few parameters programmably. I don't think it's ideal for client users to set up so many parameters in a complicated xml file in a file system. For my self, I would certainly like to provide a UI for 

Re: APIs for ws-security paramenters

Hi Raymond, No plans as of now. Will be adding the APIs when time permits.. Do you need it urgently? Infact, it would be great if you can provide a patch :) Regards, Shankar Raymond Zhou wrote: Hi, Uthaiyashankar, Thanks much for the info. I am a bit surprised that we can only set the few

Re: APIs for ws-security paramenters

On Wed, 2008-10-22 at 22:06 -0700, Raymond Zhou wrote: Hi, Uthaiyashankar, Thanks much for the info. I am a bit surprised that we can only set the few parameters programmably. I don't think it's ideal for client users to set up so many parameters in a complicated xml file in a file system.