[jira] Created: (AXISCPP-696) Test framework hangs executing FaultMappingDoc test

Test framework hangs executing FaultMappingDoc test --- Key: AXISCPP-696 URL: http://issues.apache.org/jira/browse/AXISCPP-696 Project: Axis-C++ Type: Bug Environment: Linux C++ server side Reporter: Samisa Abeysin

[jira] Closed: (AXISCPP-678) WSDL2Ws generates header that does not compile

[ http://issues.apache.org/jira/browse/AXISCPP-678?page=all ] Dushshantha Chandradasa closed AXISCPP-678: --- Fixed and tested. > WSDL2Ws generates header that does not compile > -- > > Key: A

[jira] Resolved: (AXISCPP-678) WSDL2Ws generates header that does not compile

[ http://issues.apache.org/jira/browse/AXISCPP-678?page=all ] Dushshantha Chandradasa resolved AXISCPP-678: - Resolution: Fixed > WSDL2Ws generates header that does not compile > -- > >

[jira] Assigned: (AXISCPP-678) WSDL2Ws generates header that does not compile

[ http://issues.apache.org/jira/browse/AXISCPP-678?page=all ] Dushshantha Chandradasa reassigned AXISCPP-678: --- Assign To: Dushshantha Chandradasa > WSDL2Ws generates header that does not compile > ---

[jira] Created: (AXISCPP-694) Test framwork hangs executing DynamicGet_AddAnyObjectTestOutOfScope test

Test framwork hangs executing DynamicGet_AddAnyObjectTestOutOfScope test Key: AXISCPP-694 URL: http://issues.apache.org/jira/browse/AXISCPP-694 Project: Axis-C++ Type: Bug Components: Test

[jira] Created: (AXISCPP-695) Test framework hangs executing FaultMapping test

Test framework hangs executing FaultMapping test Key: AXISCPP-695 URL: http://issues.apache.org/jira/browse/AXISCPP-695 Project: Axis-C++ Type: Bug Components: Test Versions: current (nightly) Environment:

[jira] Created: (AXISCPP-692) SSL test failing - due to SLL port not being correctly set

SSL test failing - due to SLL port not being correctly set -- Key: AXISCPP-692 URL: http://issues.apache.org/jira/browse/AXISCPP-692 Project: Axis-C++ Type: Test Components: Test Versions: current (night

[jira] Closed: (AXISCPP-692) SSL test failing - due to SLL port not being correctly set

[ http://issues.apache.org/jira/browse/AXISCPP-692?page=all ] Adrian Dick closed AXISCPP-692: --- Fix Version: current (nightly) Resolution: Fixed Renamed test.port back to testPort - allowing the property test.port to be used from the individual t

[jira] Created: (AXISCPP-693) Type defined as nillable is not defined as a pointer

Type defined as nillable is not defined as a pointer Key: AXISCPP-693 URL: http://issues.apache.org/jira/browse/AXISCPP-693 Project: Axis-C++ Type: Bug Environment: n/a Reporter: Fred Preston Assigned to: Fre

[jira] Closed: (AXISCPP-691) Memory leak in generated stubs for non-nillable simple types

[ http://issues.apache.org/jira/browse/AXISCPP-691?page=all ] Adrian Dick closed AXISCPP-691: --- Fix Version: current (nightly) Resolution: Fixed > Memory leak in generated stubs for non-nillable simple types > -

[jira] Created: (AXISCPP-691) Memory leak in generated stubs for non-nillable simple types

Memory leak in generated stubs for non-nillable simple types Key: AXISCPP-691 URL: http://issues.apache.org/jira/browse/AXISCPP-691 Project: Axis-C++ Type: Bug Components: WSDL processing - Doc Vers

[jira] Resolved: (AXISCPP-676) Problems with XSD types in AxisUserAPI.hpp

[ http://issues.apache.org/jira/browse/AXISCPP-676?page=all ] Adrian Dick resolved AXISCPP-676: - Fix Version: current (nightly) Resolution: Fixed Corrected the problems described - found a couple of additional types that had been incorrectly d

http://xml.apache.org/xml-soap

Hi, Does anyone know anything about the http://xml.apache.org/xml-soap namespace? The WebSphere tooling generates WSDL describing attachments using types under the http://xml.apache.org/xml-soap namespace. Is this a standard? Does anyone know where I could find documentation? Why isn't the WSD

[jira] Closed: (AXISCPP-690) Unable to deserialize large xsd:long values

[ http://issues.apache.org/jira/browse/AXISCPP-690?page=all ] Adrian Dick closed AXISCPP-690: --- Fix Version: current (nightly) Resolution: Fixed I have improved the serialization logic in Integer.cpp - which was limited to the size of (c-type) lo

[jira] Commented: (AXISCPP-664) Improve Call::initialize() method and make sure one off activities are not executed for multiple invocations

[ http://issues.apache.org/jira/browse/AXISCPP-664?page=comments#action_12313558 ] Samisa Abeysinghe commented on AXISCPP-664: --- I successfully moved AxisEngine::initilize() from Call::initialize() to Call constructor. The tests are successful. >

[jira] Assigned: (AXISCPP-689) SIGSEGV in HTTPTransport::FindTransportPropertyIndex when no SOAPAction set

[ http://issues.apache.org/jira/browse/AXISCPP-689?page=all ] Dushshantha Chandradasa reassigned AXISCPP-689: --- Assign To: Dushshantha Chandradasa > SIGSEGV in HTTPTransport::FindTransportPropertyIndex when no SOAPAction set > --

[jira] Closed: (AXISCPP-689) SIGSEGV in HTTPTransport::FindTransportPropertyIndex when no SOAPAction set

[ http://issues.apache.org/jira/browse/AXISCPP-689?page=all ] Dushshantha Chandradasa closed AXISCPP-689: --- Fixed and tested. > SIGSEGV in HTTPTransport::FindTransportPropertyIndex when no SOAPAction set > -

[jira] Resolved: (AXISCPP-689) SIGSEGV in HTTPTransport::FindTransportPropertyIndex when no SOAPAction set

[ http://issues.apache.org/jira/browse/AXISCPP-689?page=all ] Dushshantha Chandradasa resolved AXISCPP-689: - Resolution: Fixed Fixed. Made the do.. while loop a while loop with the same condition. > SIGSEGV in HTTPTransport::FindTrans

[jira] Assigned: (AXISCPP-676) Problems with XSD types in AxisUserAPI.hpp

[ http://issues.apache.org/jira/browse/AXISCPP-676?page=all ] Adrian Dick reassigned AXISCPP-676: --- Assign To: Adrian Dick > Problems with XSD types in AxisUserAPI.hpp > -- > > Key: AXISCPP-676 >

[jira] Created: (AXISCPP-690) Unable to deserialize large xsd:long values

Unable to deserialize large xsd:long values --- Key: AXISCPP-690 URL: http://issues.apache.org/jira/browse/AXISCPP-690 Project: Axis-C++ Type: Bug Components: Client - Deserialization, Server - Deserialization Versions:

[jira] Resolved: (AXISCPP-640) mallocs in C++ engine

[ http://issues.apache.org/jira/browse/AXISCPP-640?page=all ] Chinthana Danapala resolved AXISCPP-640: Fix Version: 1.6 Alpha Resolution: Incomplete (Visible to axiscpp-developers) > mallocs in C++ engine > - > >

[jira] Commented: (AXISCPP-640) mallocs in C++ engine

[ http://issues.apache.org/jira/browse/AXISCPP-640?page=comments#action_12313560 ] Chinthana Danapala commented on AXISCPP-640: I have removed the "malloc" and "free" code in SoapDeSerializer.cpp, XercesHandler.cpp files. I have tested the chan

[jira] Closed: (AXISCPP-644) Nillable response-fields lead to corrupt a XML-response

[ http://issues.apache.org/jira/browse/AXISCPP-644?page=all ] Dushshantha Chandradasa closed AXISCPP-644: --- > Nillable response-fields lead to corrupt a XML-response > --- > > Key: AX

[jira] Resolved: (AXISCPP-635) Remove axis2 from ant build system

[ http://issues.apache.org/jira/browse/AXISCPP-635?page=all ] Dushshantha Chandradasa resolved AXISCPP-635: - Resolution: Fixed Done. i removed Axis2 transport from the Ant build system as we don't use Axis2 anymore in Axis C++. > Remo