RE: Today CVS Build failing

Using ‘/TP’ option (compile all files as .cpp) with cl seem to solve the problem. Include in buildInitialize.xml VC++ compiler options.   Samisa…   -Original Message- From: Chinthana C. Dinapala [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 18, 2005 10:17 AM To: Apache AXIS C

Re: Fw: Attachments

Hi Mark, Yeah sure, post the changes that you intend to make in the mailing list so that we may be able to help you whether your changes will fit in with our design or not. BTW are attachments (server side) running on AIX? Rangika On Tue, 2005-05-17 at 17:34 +0100, Mark Whitlock wrote: > > >

Today CVS Build failing

Hi guys,   Today build failing due to following error.      [cc] Generating Code...    [cc] Compiling...    [cc] apr_base64.c    [cc] C:\Program Files\Microsoft Visual Studio\VC98\include\eh.h(32) : fat al error C1189: #error :  "eh.h is only for C++!"    [cc] G

[jira] Updated: (AXISCPP-652) NilValuesTest failing

[ http://issues.apache.org/jira/browse/AXISCPP-652?page=all ] Chinthana Danapala updated AXISCPP-652: --- Attachment: BeanParamWriter.java This problem occurs due to the changes i have made for support "all" construct. I have made the corrections and

RE: OS and compiler compatibilites

Hi John,     We run our test server on windows 2003 server and VC++ 6. (So only the OS differes). In addition, we develop on Win XP machines with VC6.     We have never tried VC7.       Linux: We have Fedora core 2 system with gcc version 3.3.3   Thanks, Samis

RE: Handling Nillable elements which are wsdl choices

Let me clear the air a bit more here.   In the way we have implemented both ‘choice’ and ‘all’ constructs, we use C++ NULL value to check if some field is optional in serialization. In other words, if a field is optional as per the WSDL definition, and if the C++ class attribute is NULL,

[jira] Assigned: (AXISCPP-652) NilValuesTest failing

[ http://issues.apache.org/jira/browse/AXISCPP-652?page=all ] Samisa Abeysinghe reassigned AXISCPP-652: - Assign To: Dushshantha Chandradasa Chintana has found how to fix this. Dushshantha will take care of the commits > NilValuesTest failing > -

Re: OS and compiler compatibilites

John, Differences in the compiler used for the product vs. an application should not normally present a problem However the one place you can get issues is with name mangling of C++ functions, though I don't think there are issues between MS VC6 and VC7 on Windows. There ARE mangling issues bet

Re: XSD types

OS/400 is 64-bit machine. ints and longs are 32 bit. long long is 64bit. In addition, I was wondering why we do not use the file to determine max/min value for the various types? I saw that we hard-code the values when checking for ranges. Nadir K. Amra Mark Whitlock <[EMAIL PROTECTED]> wr

Handling Nillable elements which are wsdl choices

Hi All,   I implemented the support for ‘choice’ WSDL construct in Axis C++ . According to our design,  generated stub level classes serialize the choice elements in the following way.   int Axis_Serialize_ChoiceComplexType(ChoiceComplexType* param, IWrapperSoapSerializer* pSZ, bool bAr

Fw: Web service DLL including class derived from SoapFaultException f ails to load

Hi Jeff, The soap fault model in the client changed in the last release. I don't know whether soap faults work in the server. Does your service load when you remove the soap faults from your wsdl? I have reopened AXISCPP-237 since it is still a problem. Mark Mark Whitlock IBM - Forwarded

Fw: Attachments

Hi Rangika, I will continue to investigate what I need over what support is already in the code. I did not want to offend yourself or Damitha by implementing this if he already part-way through implementing this himself. I am keen to ensure that my changes fit in with your design so I will post

[jira] Reopened: (AXISCPP-237) dlopen failures should show reason for failure

[ http://issues.apache.org/jira/browse/AXISCPP-237?page=all ] Mark Whitlock reopened AXISCPP-237: --- Jeff Clary wrote on the mailing list... > One more thing. The JIRA bug AXISCPP-237 has a comment at > the bottom that mentions a memory deallocation

[jira] Created: (AXISCPP-653) xsd_unsignedLong not long enough to hold max SOAP value

xsd_unsignedLong not long enough to hold max SOAP value --- Key: AXISCPP-653 URL: http://issues.apache.org/jira/browse/AXISCPP-653 Project: Axis-C++ Type: Bug Components: SOAP Reporter: Mark Whitlock In Ax

XSD types

Hi, I am investigating getting Axis C++ working on AIX 64 bit mode. The sizes of longs (and ints?) are different on different platforms and in 32bit and 64bit mode. I propose that the sizes of the xsd types in AxisUserAPI.hpp should be the same on all platforms in all modes since the maximum va

[jira] Commented: (AXISCPP-652) NilValuesTest failing

[ http://issues.apache.org/jira/browse/AXISCPP-652?page=comments#action_65592 ] Dushshantha Chandradasa commented on AXISCPP-652: - I found the problem here. Here the elements in aRecord complex type are in a wsdl 'all' block.

OS and compiler compatibilites

Hi Folks, Does any one have any information on what OS's and compilers on those OS's are upwards compatibile? i.e. if I build using compiler level 'a' what newer levels of compiler and Os can I build and run my app on? If you could give me any information on what you are running AXISCPP on would

Re: Attachments

Hi Mark, I'm not involved in attachment support client side.I was only involved in server side.Damitha is working on client side I'm not sure how far he has done.I think he wouldn't mind you working on it. Regds Rangika On Mon, 2005-05-16 at 13:31 +0100, Mark Whitlock wrote: > > > > Hi Damit