[jira] [Resolved] (RAMPART-342) ant service.01 build fails due to missmatching versions of mar files in axis2_home/repository/modules

2011-12-06 Thread Ruchith Udayanga Fernando (Resolved) (JIRA)
[ https://issues.apache.org/jira/browse/RAMPART-342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ruchith Udayanga Fernando resolved RAMPART-342. --- Resolution: Duplicate Fix Version/s: (was: 1.6.2) https:/

[jira] [Closed] (RAMPART-70) RAMPART Problems on building messages

2011-12-06 Thread Ruchith Udayanga Fernando (Closed) (JIRA)
[ https://issues.apache.org/jira/browse/RAMPART-70?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ruchith Udayanga Fernando closed RAMPART-70. Resolution: Not A Problem Fix Version/s: 1.6.1 Rampart can encrypt w

[Axis2] [Rampart] How to check exactly what key is used to check signature

2011-12-06 Thread Tor-Erik Steinsland
Hello, I have developed a web service which uses signature for authentication and message integrity checking. I have managed to get it to work after following this guide: http://wso2.org/library/3415 My challenge is: If I assume that I have a number of clients using this web service, how can I fi

[jira] [Updated] (AXIS2-5207) JSON formatted content gives an error if there is a line break ('\n') or tab space ('\t') or carriage return ('\r') after the first curly bracket

2011-12-06 Thread Thilini Ishaka (Updated) (JIRA)
[ https://issues.apache.org/jira/browse/AXIS2-5207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thilini Ishaka updated AXIS2-5207: -- Attachment: axis2_5207.patch I have created a patch to resolve this issue. Please apply the pat

[jira] [Created] (AXIS2-5207) JSON formatted content gives an error if there is a line break ('\n') or tab space ('\t') or carriage return ('\r') after the first curly bracket

2011-12-06 Thread Thilini Ishaka (Created) (JIRA)
JSON formatted content gives an error if there is a line break ('\n') or tab space ('\t') or carriage return ('\r') after the first curly bracket -

Axis 1.3 parsing error on optional elements

2011-12-06 Thread dugolf
My soap message contains 1 mandatory element and 3 optionals complexe type (minOccurs = 0):