274 messages

org.apache.ws.sandesha-dev [All Lists]

2013 January [All Months]

Page 11 (Messages 251 to 274): 1 2 3 4 5 6 7 8 9 10 11

[jira] [Commented] (AXIS-2886) xs:date not serialized/deserialized correctly - Martin Gainty (JIRA)
[jira] [Updated] (RAMPART-399) Rampart Samples page should be updated. - Suresh Attanayake (JIRA)
Jenkins build became unstable: sandesha2-trunk #1116 - Apache Jenkins Server
Jenkins build became unstable: sandesha2-trunk » Sandesha2 - Persistent Storage #1118 - Apache Jenkins Server
[jira] [Commented] (AXIS-2863) Circular Reference in Deserialization and XMLReader - Andreas Veithen (JIRA)
[jira] [Commented] (AXIS-2677) wrong order of elements in response message for complex types - Rahul Bhagat (JIRA)
Jenkins build is back to stable : sandesha2-trunk » Sandesha2 - Persistent Storage #1120 - Apache Jenkins Server
[jira] [Updated] (AXIS2-5475) Unable to generate code using jaxbri - VictorQian (JIRA)
[jira] [Resolved] (AXIS2-5469) WstxIOException when trying to retrieve inbound envelope from last operation message context - Ryan H (JIRA)
[jira] [Commented] (AXIS2-5342) Generated code for xsd:totalDigits cause errors - Pramod CA (JIRA)
[jira] [Commented] (AXIS2-5474) DefaultSchemaGenerator : properly handle failure when a bean property has no getReadMethod() - Mark Carpenter (JIRA)
[jira] [Commented] (AXIS2-5474) DefaultSchemaGenerator : properly handle failure when a bean property has no getReadMethod() - Kishanthan Thangarajah (JIRA)
[jira] [Updated] (AXIS2-5474) DefaultSchemaGenerator : properly handle failure when a bean property has no getReadMethod() - Philippe Le Berre (JIRA)
[jira] [Comment Edited] (AXIS2-5474) DefaultSchemaGenerator : properly handle failure when a bean property has no getReadMethod() - Philippe Le Berre (JIRA)
Jenkins build is still unstable: Axis2-trunk-java-1.6 #1486 - Apache Jenkins Server
Jenkins build is back to stable : sandesha2-trunk #1137 - Apache Jenkins Server
[jira] [Created] (AXIS2-5478) documantation has wrong config example - tibi (JIRA)
[jira] [Commented] (RAMPART-385) Rampart does check username token password (via callback), even though "NoPassword" was specified in Security Policy - Suresh Attanayake (JIRA)
[jira] [Resolved] (RAMPART-384) Invalid serialization for UsernameToken with WS-SecurityPolicy 1.2 - Ruchith Udayanga Fernando (JIRA)
[jira] [Commented] (AXIS2-5473) System hangs (cpu 100%) after sending a corrupt soap message - Mario Hercog (JIRA)
[jira] [Updated] (AXIS-2887) SOAPAction being set even when WSDL has soapAction="" - Wayne Holmes (JIRA)
[jira] [Commented] (AXIS-2887) SOAPAction being set even when WSDL has soapAction="" - Wayne Holmes (JIRA)
[jira] [Commented] (AXIS2-3964) WSDL20ToAxisServiceBuilder > HTTP Binding: AxisBindingMessage entry is being overwritten in corresponding AxisBindingOperation - Matt Fluet (JIRA)
RE : How to disable BSP compliance check on Rampart (1.6.2) - WIELGUS Franck

Page 11 (Messages 251 to 274): 1 2 3 4 5 6 7 8 9 10 11