[jira] Created: (AXISCPP-904) undeclared xml namespaces

undeclared xml namespaces - Key: AXISCPP-904 URL: http://issues.apache.org/jira/browse/AXISCPP-904 Project: Axis-C++ Type: Bug Components: Client - Engine Versions: 1.6 Alpha Environment: WIN2KSP4 JDK1.5.0_06 MSVC6SP6 Reporter

[jira] Updated: (AXISCPP-903) extra ampersand in serializexxx methods

[ http://issues.apache.org/jira/browse/AXISCPP-903?page=all ] Franz Fehringer updated AXISCPP-903: Attachment: vakanz.wsdl vakanz.xsd > extra ampersand in serializexxx methods > --- > > Key

[jira] Created: (AXISCPP-903) extra ampersand in serializexxx methods

extra ampersand in serializexxx methods --- Key: AXISCPP-903 URL: http://issues.apache.org/jira/browse/AXISCPP-903 Project: Axis-C++ Type: Bug Versions: 1.6 Alpha Environment: WIN2KSP4 JDK1.5.0_06 MSVC6SP6 Reporter: Fr

JIRA

Hello John, I have updated AXISCPP-753 and AXISCPP-898 with attachments. I still consider AXISCPP-897 as the biggest problem (generation of noncompilable code and a regression too). Note that AXISCPP-753 is also a Java issue for which AXIS-2281 was recently created. Best regards Franz Dr. Franz

[jira] Updated: (AXISCPP-753) WSDL2Ws can't handle complexTypes?

[ http://issues.apache.org/jira/browse/AXISCPP-753?page=all ] Franz Fehringer updated AXISCPP-753: Attachment: PegsTour.wsdl PegsTour.xsd > WSDL2Ws can't handle complexTypes? > -- > > Key: AXIS

[jira] Updated: (AXISCPP-898) simple problem with simpleTypes

[ http://issues.apache.org/jira/browse/AXISCPP-898?page=all ] Franz Fehringer updated AXISCPP-898: Attachment: PegsTour.wsdl PegsTour.xsd > simple problem with simpleTypes > --- > > Key: AXISCPP-89

[jira] Created: (AXIS2C-18) If there is an XML error in the incomming SOAP message, the server hangs

If there is an XML error in the incomming SOAP message, the server hangs Key: AXIS2C-18 URL: http://issues.apache.org/jira/browse/AXIS2C-18 Project: Axis2-C Type: Bug Components: xml/soap

[jira] Commented: (AXISCPP-898) simple problem with simpleTypes

[ http://issues.apache.org/jira/browse/AXISCPP-898?page=comments#action_12363009 ] John Hawkins commented on AXISCPP-898: -- Pleae can you attach the WSDlL that is causing you this issue so that we can reproduce the problem. > simple problem with simpl

[jira] Commented: (AXISCPP-753) WSDL2Ws can't handle complexTypes?

[ http://issues.apache.org/jira/browse/AXISCPP-753?page=comments#action_12363008 ] John Hawkins commented on AXISCPP-753: -- Please can you attach the wsdl that is giving you the problem. > WSDL2Ws can't handle complexTypes? > --

[jira] Resolved: (AXISCPP-880) Client deserialization issue with element in a complextype

[ http://issues.apache.org/jira/browse/AXISCPP-880?page=all ] Adrian Dick resolved AXISCPP-880: - Fix Version: 1.6 Alpha Resolution: Fixed I have made some changes to the SoapDeSerializer to ensure it only deserializes the correct number of el

undeclared xml namespaces

Hello, For me AxisC (both 1.5 and 1.6) generates invalid SOAP messages referring to undeclared namespaces. The problem occurs only if i set soap:header elements for inclusion in the SOAP message. Possibility 1 IHeaderBlock* phb = pegs->createSOAPHeaderBlock("Token", "http://www.pegs-pegstour.com/A

[jira] Assigned: (AXISCPP-880) Client deserialization issue with element in a complextype

[ http://issues.apache.org/jira/browse/AXISCPP-880?page=all ] Adrian Dick reassigned AXISCPP-880: --- Assign To: Adrian Dick > Client deserialization issue with element in a complextype > --

[jira] Resolved: (AXISCPP-895) Code generated by WSDL2Ws tool shows compilation error

[ http://issues.apache.org/jira/browse/AXISCPP-895?page=all ] Adrian Dick resolved AXISCPP-895: - Fix Version: 1.6 Alpha Resolution: Fixed We have made some small modification to the WSDL2Ws code, which mean this compilation error should no lon

[jira] Closed: (AXISCPP-685) SSL and non-SSL test suite

[ http://issues.apache.org/jira/browse/AXISCPP-685?page=all ] Adrian Dick closed AXISCPP-685: --- Resolution: Fixed You can now include true within the property file for any given testcase if it requires the SSL library - and this will ensure the approp

[jira] Resolved: (AXISCPP-902) Synchronization used by engine\axis.cpp in start_initializing and done_initializing was wrong for Win32

[ http://issues.apache.org/jira/browse/AXISCPP-902?page=all ] Adrian Dick resolved AXISCPP-902: - Fix Version: 1.6 Alpha Resolution: Fixed I have made the modifications as suggested, and they seem to work nicely across the test suite using VC++

[jira] Assigned: (AXISCPP-902) Synchronization used by engine\axis.cpp in start_initializing and done_initializing was wrong for Win32

[ http://issues.apache.org/jira/browse/AXISCPP-902?page=all ] Adrian Dick reassigned AXISCPP-902: --- Assign To: Adrian Dick > Synchronization used by engine\axis.cpp in start_initializing and > done_initializing was wrong for Win32 > ---

extra ampersand in serializexxx methods

Hello, Both AxisC 1.5 and the upcoming 1.6 have issues with serializexxx methods in generated code. The point is that all data items are passed as void* (opaque pointers). Therefore integer items get an ampersand & applied in front like pSZ->serializeAsAttribute( "xsi:nil", 0, (void*)&(xsd_boolean