Re: Axis C++: Looking for some guidance - what to do on parser errors?

___ Adrian Dick ([EMAIL PROTECTED]) Nadir Amra [EMAIL PROTECTED] wrote on 25/01/2007 06:59:39: I have been frustrated somewhat in debugging problems relating to SOAP deserialization/parsing. It seems that the deserializer ignores parsing errors by simply returning AXIS_FAIL or NULL or empty array

Re: how to compile axis C++ with VS 2003 or VS 2005?

here, we could see about getting them included. Regards, Adrian ___ Adrian Dick ([EMAIL PROTECTED]) Anatoly Gutnick [EMAIL PROTECTED] wrote on 20/01/2007 18:35:46: Hi, i am able to build Axis C++ client using ANT based build http://ws.apache.org/axis/cpp

Re: axiscpp problems

Hi, Don't forget to ensure you have the Xerces-C parser libraries at an appropriate level available on the path, otherwise the Axis parser library will fail to load (as in the error message you describe). What's the state of this project? should I be using axis2c instead? Is all this

Re: axiscpp problems

___ Adrian Dick ([EMAIL PROTECTED]) Franz Fehringer [EMAIL PROTECTED] wrote on 16/11/2006 09:34:30: Without axiscpp.conf how does Axis know the names of the libraries to load? Franz The library names are hardcoded within the engine. If looking for them

[jira] Commented: (AXISCPP-1002) Support for xsi:type when serializing complex objects and arrays of complex objects.

[ http://issues.apache.org/jira/browse/AXISCPP-1002?page=comments#action_12438359 ] Adrian Dick commented on AXISCPP-1002: -- Hi, I was under the impression that for rpc/encoded web services, the WSDL2Ws tooling will generate

Re: Removing dependency on AXISCPP_DEPLOY and axiscpp.conf forsimple_axis_server

it correctly. Regards, Adrian ___ Adrian Dick ([EMAIL PROTECTED]) Henrik Nordberg [EMAIL PROTECTED] wrote on 14/09/2006 05:44:11: I think it would quite easy and worthwhile to do. Cheers - Henrik - Original Message - From: William D. Strathearn

[jira] Commented: (AXISCPP-986) ANT Build failed

[ http://issues.apache.org/jira/browse/AXISCPP-986?page=comments#action_12423326 ] Adrian Dick commented on AXISCPP-986: - Hi, It really isn't clear to me how you're trying to compile the code, but there seem to be a lot of inconsistencies

[jira] Commented: (AXISCPP-986) ANT Build failed

[ http://issues.apache.org/jira/browse/AXISCPP-986?page=comments#action_12423016 ] Adrian Dick commented on AXISCPP-986: - Hi, I've just done a quick check using VC++ 8 (MS Visual Studio 2005) and see the same problems as those you're

[jira] Commented: (AXISCPP-986) ANT Build failed

[ http://issues.apache.org/jira/browse/AXISCPP-986?page=comments#action_12422059 ] Adrian Dick commented on AXISCPP-986: - Hi, You don't mention which compiler you're using, but I know (from personal experience) that for Windows it should

[jira] Commented: (AXISCPP-983) Windows Mobile

[ http://issues.apache.org/jira/browse/AXISCPP-983?page=comments#action_12422173 ] Adrian Dick commented on AXISCPP-983: - Hi, It sounds like you will need to recompile Axis C++ specifically for the Windows mobile platform, using the ANT

Re: javacode gen remnants

support this, so maybe it would make more sense to re-introduce the function when someone gets to implementing C++ namespaces. Adrian ___ Adrian Dick ([EMAIL PROTECTED]) Nadir Amra [EMAIL PROTECTED] wrote on 19/07/2006 15:18:52: I plan on removing stuff

Re: handling of xml attributes flawed

is actually the one from the parent ParamInfo -- it really isn't obvious to me how this is used. In class Type, the attributes member should be a map from String to AttributeInfo. Regards, Adrian ___ Adrian Dick ([EMAIL PROTECTED

Re: compilation slow down

, Adrian ___ Adrian Dick ([EMAIL PROTECTED]) Franz Fehringer [EMAIL PROTECTED] wrote on 21/06/2006 10:51:21: Hello, I notice a considerable compilation slow down for generated Code (it happened several weaks ago). I do not know the exact turning point

Re: Makefile.am

, Adrian ___ Adrian Dick ([EMAIL PROTECTED]) Franz Fehringer [EMAIL PROTECTED] wrote on 01/06/2006 09:39:02: Hello, The repository contains obsolete Makefile.ams. Perhaps they could be removed? Greetings Franz [attachment feh.vcf deleted by Adrian

Re: Axis_GetSize_XXX not needed

Hi, I had been thinking this might be redundant, in which case I agree that it's best to remove. Regards, Adrian ___ Adrian Dick ([EMAIL PROTECTED]) Nadir Amra [EMAIL PROTECTED] wrote on 01/05/2006 06:15:44: I do not think the generation of the function

[jira] Updated: (AXISCPP-966) WSDL2WS generate wrong code: redundant value reference * in Wrapper

[ http://issues.apache.org/jira/browse/AXISCPP-966?page=all ] Adrian Dick updated AXISCPP-966: Environment: Platform: Linux fedora 3.0 Axis version: Server-side Axis C++ 1.6Beta XML Parser Lib: xersesc 2.6 WSDL2ws tool by using axis

[jira] Commented: (AXISCPP-966) WSDL2WS generate wrong code: redundant value reference * in Wrapper

[ http://issues.apache.org/jira/browse/AXISCPP-966?page=comments#action_12376195 ] Adrian Dick commented on AXISCPP-966: - Hi, I agree this code doens't look right ... would it be possible to attach your WSDL file so we can reproduce the problem

Re: api doc

problem, this is actually when the trace instrumentor is being run, though I'm not too certain about the cause. I shall take a dig around. Regards, Adrian ___ Adrian Dick ([EMAIL PROTECTED]) Franz Fehringer [EMAIL PROTECTED] wrote on 25/04/2006 11:03:30

[jira] Updated: (AXISCPP-965) Manual have to change version number in SimpleAxisServer

[ http://issues.apache.org/jira/browse/AXISCPP-965?page=all ] Adrian Dick updated AXISCPP-965: type: Improvement (was: Bug) Manual have to change version number in SimpleAxisServer

[jira] Closed: (AXISCPP-169) Incomplete documentation of Public API

[ http://issues.apache.org/jira/browse/AXISCPP-169?page=all ] Adrian Dick closed AXISCPP-169: --- Fix Version: current (nightly) Resolution: Fixed The public API has now been completely documented, and all doxygen errors have been resolved. I'm

Re: Engine incorrectly sends a MustUndersand fault code

over-the-wire SOAP messages). Regards, Adrian ___ Adrian Dick ([EMAIL PROTECTED]) Nabeel [EMAIL PROTECTED] wrote on 21/04/2006 05:28:56: Engine incorrectly sends a MustUndersand fault code when the request message has headers with mustunderstand attribute

Re: Change prototypes for AXIS_OBJECT_CREATE_FUNCT

___ Adrian Dick ([EMAIL PROTECTED]) Nadir Amra [EMAIL PROTECTED] wrote on 19/04/2006 05:33:40: As I have been implementing the C bindings (getting close, AxisBench, CalculatorDoc, and SimpleTypeArray works like a charm), I think we should be able to change the typedef for typedef void

[jira] Closed: (AXISCPP-551) getAnyObject() API in call class does not return SOAP Fault correctly

[ http://issues.apache.org/jira/browse/AXISCPP-551?page=all ] Adrian Dick closed AXISCPP-551: --- Resolution: Fixed This problem now seems to be resolved as the client testcase mentioned is now passing. getAnyObject() API in call class does

[jira] Closed: (AXISCPP-910) In the Error message for SERVER_TRANSPORT_TIMEOUT_EXPIRED - 'receiving' is mispelled as 'receving'

[ http://issues.apache.org/jira/browse/AXISCPP-910?page=all ] Adrian Dick closed AXISCPP-910: --- Resolution: Fixed All occurances of this spelling mistake have now been corrected. In the Error message for SERVER_TRANSPORT_TIMEOUT_EXPIRED - 'receiving

[jira] Resolved: (AXISCPP-858) client stub delete Ret; causes Debug Assertion Failed! Win32

[ http://issues.apache.org/jira/browse/AXISCPP-858?page=all ] Adrian Dick resolved AXISCPP-858: - Fix Version: 1.6 Beta Resolution: Fixed Brian, I'm going to mark this as resolved because this problem has been reported several times

Re: Patch licensing question

(details here: http://www.apache.org/foundation/mailinglists.html#foundation-legal ) Regards, Adrian ___ Adrian Dick ([EMAIL PROTECTED]) Eneko Lacunza [EMAIL PROTECTED] wrote on 12/04/2006 10:54:09: Hi, I'm sorry to bother you with this, but we may

Re: last wsdl2ws reorganization / AXISCPP-918

. Regards, Adrian ___ Adrian Dick ([EMAIL PROTECTED]) Franz Fehringer [EMAIL PROTECTED] wrote on 05/04/2006 15:46:43: Hello Adrian, My fix is contained in my comment to AXISCPP-918 (scroll to the bottom of http://issues.apache.org/jira/browse/AXISCPP-918

RE: [AXIS C++ 1.6b] : Deserialization problems

nightly build. I'm a little mystified by problems you're seeing with non-US-ASCII characters and will need to do a little more digging into this problem. Regards, Adrian ___ Adrian Dick ([EMAIL PROTECTED]) Damien Bouchet [EMAIL PROTECTED] wrote on 06/04/2006 13

Re: C-support and array implementation

an additional and optional parameter to indicate a deep copy is wanted, with the current behaviour being the default. I hope this is of help. Regards, Adrian ___ Adrian Dick ([EMAIL PROTECTED]) Nadir Amra [EMAIL PROTECTED] wrote on 05/04/2006 00:14:35

[jira] Closed: (AXISCPP-429) generated stubs use request message name, instead of operation name for setOperation

[ http://issues.apache.org/jira/browse/AXISCPP-429?page=all ] Adrian Dick closed AXISCPP-429: --- generated stubs use request message name, instead of operation name for setOperation

[jira] Closed: (AXISCPP-938) soap encoding namespace for xsi:type fails when deserializing basic types

[ http://issues.apache.org/jira/browse/AXISCPP-938?page=all ] Adrian Dick closed AXISCPP-938: --- soap encoding namespace for xsi:type fails when deserializing basic types

[jira] Resolved: (AXISCPP-823) Some memory leaks have course the XSD type test failing.

[ http://issues.apache.org/jira/browse/AXISCPP-823?page=all ] Adrian Dick resolved AXISCPP-823: - Resolution: Fixed Hi, This problem appears to have been resolved by recent memory fixes to xsd__hexBinary and xsd__base64Binary, so I am going

Re: last wsdl2ws reorganization / AXISCPP-918

formatting), while any WSDL2Ws patch files may need to be reworked to the new location - but the patch content is probably still good. Regards, Adrian ___ Adrian Dick ([EMAIL PROTECTED]) Franz Fehringer [EMAIL PROTECTED] wrote on 05/04/2006 09:23:17: Hello

[jira] Assigned: (AXISCPP-961) The generated deserialization methods are producing the wrong code for nillable simple-type elements

[ http://issues.apache.org/jira/browse/AXISCPP-961?page=all ] Adrian Dick reassigned AXISCPP-961: --- Assign To: Adrian Dick The generated deserialization methods are producing the wrong code for nillable simple-type elements

[jira] Commented: (AXISCPP-961) The generated deserialization methods are producing the wrong code for nillable simple-type elements

[ http://issues.apache.org/jira/browse/AXISCPP-961?page=comments#action_12373110 ] Adrian Dick commented on AXISCPP-961: - It would appear the WSDL2Ws tooling is missing some important fixes relating to the deserialization optional and nillable

[jira] Resolved: (AXISCPP-961) The generated deserialization methods are producing the wrong code for nillable simple-type elements

[ http://issues.apache.org/jira/browse/AXISCPP-961?page=all ] Adrian Dick resolved AXISCPP-961: - Fix Version: current (nightly) Resolution: Fixed I have included a number of updates, which will be available in the next nightly build. Testing

[jira] Closed: (AXISCPP-285) WSDDService seems to be redundant in IMessageData.hpp

[ http://issues.apache.org/jira/browse/AXISCPP-285?page=all ] Adrian Dick closed AXISCPP-285: --- WSDDService seems to be redundant in IMessageData.hpp -- Key: AXISCPP-285 URL: http

[jira] Closed: (AXISCPP-368) IHandlerSoapSerializer-setSoapVersion creates incorrect and duplicate namespaces in header

[ http://issues.apache.org/jira/browse/AXISCPP-368?page=all ] Adrian Dick closed AXISCPP-368: --- IHandlerSoapSerializer-setSoapVersion creates incorrect and duplicate namespaces in header

[jira] Closed: (AXISCPP-460) WSDL2Ws creates code which does NOT compile

[ http://issues.apache.org/jira/browse/AXISCPP-460?page=all ] Adrian Dick closed AXISCPP-460: --- WSDL2Ws creates code which does NOT compile --- Key: AXISCPP-460 URL: http://issues.apache.org

[jira] Closed: (AXISCPP-461) Duration xsd type not supported

[ http://issues.apache.org/jira/browse/AXISCPP-461?page=all ] Adrian Dick closed AXISCPP-461: --- Duration xsd type not supported --- Key: AXISCPP-461 URL: http://issues.apache.org/jira/browse/AXISCPP-461

[jira] Closed: (AXISCPP-515) Complex response containing array of complex elements does not deserialize

[ http://issues.apache.org/jira/browse/AXISCPP-515?page=all ] Adrian Dick closed AXISCPP-515: --- Complex response containing array of complex elements does not deserialize

[jira] Closed: (AXISCPP-130) Client memory problems with globals

[ http://issues.apache.org/jira/browse/AXISCPP-130?page=all ] Adrian Dick closed AXISCPP-130: --- Client memory problems with globals --- Key: AXISCPP-130 URL: http://issues.apache.org/jira/browse

[jira] Closed: (AXISCPP-165) Improve trace readability

[ http://issues.apache.org/jira/browse/AXISCPP-165?page=all ] Adrian Dick closed AXISCPP-165: --- Improve trace readability - Key: AXISCPP-165 URL: http://issues.apache.org/jira/browse/AXISCPP-165 Project

[jira] Closed: (AXISCPP-189) Stub falls over after first stub has been deleted

[ http://issues.apache.org/jira/browse/AXISCPP-189?page=all ] Adrian Dick closed AXISCPP-189: --- Stub falls over after first stub has been deleted - Key: AXISCPP-189 URL: http

[jira] Closed: (AXISCPP-202) enums cause name clashes

[ http://issues.apache.org/jira/browse/AXISCPP-202?page=all ] Adrian Dick closed AXISCPP-202: --- enums cause name clashes Key: AXISCPP-202 URL: http://issues.apache.org/jira/browse/AXISCPP-202 Project

[jira] Closed: (AXISCPP-210) Add back in C support in 1.5

[ http://issues.apache.org/jira/browse/AXISCPP-210?page=all ] Adrian Dick closed AXISCPP-210: --- Add back in C support in 1.5 Key: AXISCPP-210 URL: http://issues.apache.org/jira/browse/AXISCPP-210

[jira] Closed: (AXISCPP-241) Problems with SoapEnvVersions

[ http://issues.apache.org/jira/browse/AXISCPP-241?page=all ] Adrian Dick closed AXISCPP-241: --- Problems with SoapEnvVersions - Key: AXISCPP-241 URL: http://issues.apache.org/jira/browse/AXISCPP-241

[jira] Closed: (AXISCPP-393) IWrapperDeSerializer::getAttributeAsLong returns 32 bit long

[ http://issues.apache.org/jira/browse/AXISCPP-393?page=all ] Adrian Dick closed AXISCPP-393: --- IWrapperDeSerializer::getAttributeAsLong returns 32 bit long Key: AXISCPP-393

[jira] Closed: (AXISCPP-440) Add option to switch off building C bindings

[ http://issues.apache.org/jira/browse/AXISCPP-440?page=all ] Adrian Dick closed AXISCPP-440: --- Add option to switch off building C bindings Key: AXISCPP-440 URL: http://issues.apache.org

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

[ http://issues.apache.org/jira/browse/AXISCPP-640?page=all ] Adrian Dick closed AXISCPP-640: --- mallocs in C++ engine - Key: AXISCPP-640 URL: http://issues.apache.org/jira/browse/AXISCPP-640 Project: Axis-C

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

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

[jira] Created: (AXISCPP-960) Inconsistent generated APIs when processing WSDLs with xsd:all, xsd:choice and xsd:sequence

++ Type: Bug Components: WSDL processing - Doc, WSDL processing - RPC Versions: current (nightly) Reporter: Adrian Dick Currently, WSDL2Ws generates inconsistent APIs for xsd:all, xsd:choice and xsd:sequence within a WSDL file. For example, taking this WSDL snippet

[jira] Created: (AXISCPP-959) SimpleAxisServer fails for large request messages

SimpleAxisServer fails for large request messages - Key: AXISCPP-959 URL: http://issues.apache.org/jira/browse/AXISCPP-959 Project: Axis-C++ Type: Bug Components: Server - General Reporter: Adrian Dick

[jira] Closed: (AXISCPP-959) SimpleAxisServer fails for large request messages

[ http://issues.apache.org/jira/browse/AXISCPP-959?page=all ] Adrian Dick closed AXISCPP-959: --- Fix Version: current (nightly) Resolution: Fixed It would appear that we were not using substring correctly. So instead of taking from 0 to piSize

[jira] Resolved: (AXISCPP-476) Memory leak throwing user-defined soap faults

[ http://issues.apache.org/jira/browse/AXISCPP-476?page=all ] Adrian Dick resolved AXISCPP-476: - Fix Version: current (nightly) Resolution: Fixed As part of the work for AXISCPP-149, the Purify tool found this memory leak and I put in a fix

[jira] Commented: (AXISCPP-533) Inter shared library exception handling broken on Linux

[ http://issues.apache.org/jira/browse/AXISCPP-533?page=comments#action_12372075 ] Adrian Dick commented on AXISCPP-533: - In response to Emanuel Norrbin. The issue of namespaces to avoid name collisions is a known issue (see AXISCPP-882). Inter

[jira] Resolved: (AXISCPP-957) AxisConfiguration fails to start in AIX

[ http://issues.apache.org/jira/browse/AXISCPP-957?page=all ] Adrian Dick resolved AXISCPP-957: - Fix Version: current (nightly) Resolution: Fixed I have now updated the ant script to use the correct linker definition on AIX

[jira] Commented: (AXISCPP-858) client stub delete Ret; causes Debug Assertion Failed! Win32

[ http://issues.apache.org/jira/browse/AXISCPP-858?page=comments#action_12372078 ] Adrian Dick commented on AXISCPP-858: - Hi, A number of changes have been made between 1.5final and the 1.6beta to resolve problems as you describe here. Can you

[jira] Closed: (AXISCPP-951) AxisCPP Server cannot parse Java arrays

[ http://issues.apache.org/jira/browse/AXISCPP-951?page=all ] Adrian Dick closed AXISCPP-951: --- Resolution: Duplicate Closing as this is a duplicate of AXISCPP-952 AxisCPP Server cannot parse Java arrays

[jira] Created: (AXISCPP-958) Generated complex types with multiple array children for RPC/encoded don't compile

Components: WSDL processing - RPC Versions: current (nightly) Reporter: Adrian Dick Assigned to: Adrian Dick The deserialize method on generated rpc/encoded complex types fails to compile if it contains multiple array child elements. This is due to the re-declaration

[jira] Closed: (AXISCPP-958) Generated complex types with multiple array children for RPC/encoded don't compile

[ http://issues.apache.org/jira/browse/AXISCPP-958?page=all ] Adrian Dick closed AXISCPP-958: --- Fix Version: current (nightly) Resolution: Fixed Added increment to array counter. Generated complex types with multiple array children for RPC

[jira] Assigned: (AXISCPP-633) Trace documentation should be on the Apache website

[ http://issues.apache.org/jira/browse/AXISCPP-633?page=all ] Adrian Dick reassigned AXISCPP-633: --- Assign To: Adrian Dick (was: Mark Whitlock) Trace documentation should be on the Apache website

[jira] Resolved: (AXISCPP-633) Trace documentation should be on the Apache website

[ http://issues.apache.org/jira/browse/AXISCPP-633?page=all ] Adrian Dick resolved AXISCPP-633: - Fix Version: current (nightly) Resolution: Fixed I have now added a new document to the website describing trace and its usage. This should

[jira] Resolved: (AXISCPP-953) In AIX AxisAdminClient fails to start

[ http://issues.apache.org/jira/browse/AXISCPP-953?page=all ] Adrian Dick resolved AXISCPP-953: - Fix Version: current (nightly) Resolution: Fixed It looks like this is now working. In AIX AxisAdminClient fails to start

[jira] Created: (AXISCPP-954) Build problems caused by CBinding generation

: Adrian Dick Assigned to: Adrian Dick We have recently been seeing a number of problems on the mailing list with problems building the CBindings. 1) The source and binary packages contain the Apache 1.3 and Apache 2.0 header files (ok, this isn't strictly related to CBindings!) 2

[jira] Updated: (AXISCPP-954) Build problems caused by CBinding generation

[ http://issues.apache.org/jira/browse/AXISCPP-954?page=all ] Adrian Dick updated AXISCPP-954: Description: We have recently been seeing a number of problems on the mailing list with problems building the CBindings, due to he generation tool attempting

[jira] Created: (AXISCPP-955) Apache header files included with source and binary packages

: current (nightly) Reporter: Adrian Dick Assigned to: Adrian Dick The source and binary packages incorrectly contain the Apache 1.3 and Apache 2.0 header files. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators

[jira] Closed: (AXISCPP-954) Build problems caused by CBinding generation

[ http://issues.apache.org/jira/browse/AXISCPP-954?page=all ] Adrian Dick closed AXISCPP-954: --- Fix Version: current (nightly) Resolution: Fixed I have made some fixes to the C Binding generation tool, so this should no longer be a problem

[jira] Closed: (AXISCPP-955) Apache header files included with source and binary packages

[ http://issues.apache.org/jira/browse/AXISCPP-955?page=all ] Adrian Dick closed AXISCPP-955: --- Fix Version: current (nightly) Resolution: Fixed I have fixed the package script to explicitly select just the Axis C++ header files. Apache header

[jira] Resolved: (AXISCPP-845) Anchor tags does not work in the documentation on website

[ http://issues.apache.org/jira/browse/AXISCPP-845?page=all ] Adrian Dick resolved AXISCPP-845: - Fix Version: current (nightly) Resolution: Fixed It looks like this has been fixed in the most recent set of documentation updates. Anchor tags

[jira] Resolved: (AXISCPP-440) Add option to switch off building C bindings

[ http://issues.apache.org/jira/browse/AXISCPP-440?page=all ] Adrian Dick resolved AXISCPP-440: - Fix Version: current (nightly) Resolution: Fixed This function has recently been added. The property buildCBindings needs to exist for the C

[jira] Assigned: (AXISCPP-953) In AIX AxisAdminClient fails to start

[ http://issues.apache.org/jira/browse/AXISCPP-953?page=all ] Adrian Dick reassigned AXISCPP-953: --- Assign To: Adrian Dick In AIX AxisAdminClient fails to start - Key: AXISCPP-953 URL: http

[jira] Commented: (AXISCPP-953) In AIX AxisAdminClient fails to start

[ http://issues.apache.org/jira/browse/AXISCPP-953?page=comments#action_12371538 ] Adrian Dick commented on AXISCPP-953: - The cc tasks within build/buildAdminClient.xml is using the wrong AIX linker. It should be using the executable linker

Re: installing Axis c++ on linux

). Of course, if you should encounter any problems please let us know so we can update accordingly. Regards, Adrian ___ Adrian Dick ([EMAIL PROTECTED]) Dubi Lego [EMAIL PROTECTED] wrote on 22/03/2006 07:50:02: Hi all! I am trying to install Axis c++ client

[jira] Assigned: (AXISCPP-950) simple_axis_server and AdminClient doesn't have execute permission

[ http://issues.apache.org/jira/browse/AXISCPP-950?page=all ] Adrian Dick reassigned AXISCPP-950: --- Assign To: Adrian Dick simple_axis_server and AdminClient doesn't have execute permission

[jira] Commented: (AXISCPP-950) simple_axis_server and AdminClient doesn't have execute permission

[ http://issues.apache.org/jira/browse/AXISCPP-950?page=comments#action_12371432 ] Adrian Dick commented on AXISCPP-950: - I have applied this patch, If it causes problems in the next build, I shall back out the change. simple_axis_server

Re: crash problem

is not available on the library path (or if configuration file incorrectly specifies location). Do you have the stub creation within a try-catch block? What messages do you get? Have you tried turning on trace? Regards, Adrian ___ Adrian Dick ([EMAIL PROTECTED]) Dubi

Re: latest svn doesnt compile

___ Adrian Dick ([EMAIL PROTECTED]) Franz Fehringer [EMAIL PROTECTED] wrote on 17/03/2006 09:53:17: compileAxisConfiguration: [cc] 2 total files to be compiled. [cc] Befehlszeilenwarnung D4002 : Unbekannte Option '/w44290' wird ignoriert [cc

[jira] Updated: (AXISCPP-950) simple_axis_server and AdminClient doesn't have execute permission

[ http://issues.apache.org/jira/browse/AXISCPP-950?page=all ] Adrian Dick updated AXISCPP-950: Attachment: package.xml.diff I believe the attached patch will resolve this problem, but I haven't had an opportunity to test on a Unix platform

[jira] Commented: (AXISCPP-941) windows compilerarg

[ http://issues.apache.org/jira/browse/AXISCPP-941?page=comments#action_12370128 ] Adrian Dick commented on AXISCPP-941: - Hi, Henrik: You can add the location attribute, you'll need to experiment to find the correct position (start, mid or end

[jira] Commented: (AXISCPP-949) Client call on a great port number (endpoint URL) fails

[ http://issues.apache.org/jira/browse/AXISCPP-949?page=comments#action_12369618 ] Adrian Dick commented on AXISCPP-949: - Hi, I have done some quick testing (thanks also to James) and the described problem doesn't appear to be present on Windows

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

[ http://issues.apache.org/jira/browse/AXISCPP-904?page=comments#action_12368375 ] Adrian Dick commented on AXISCPP-904: - Hi, There are still some issues regarding namespaces when creating HeaderBlocks. As a workaround, have you tried explicitely

[jira] Commented: (AXISCPP-905) dllexport warnings

[ http://issues.apache.org/jira/browse/AXISCPP-905?page=comments#action_12368377 ] Adrian Dick commented on AXISCPP-905: - I see and, to a certain extent, agree with what you say here. It certainly doesn't look good to have extraneous warnings, etc

[jira] Commented: (AXISCPP-914) fault/exception/error handling flawed

[ http://issues.apache.org/jira/browse/AXISCPP-914?page=comments#action_12368383 ] Adrian Dick commented on AXISCPP-914: - The Fault model is a known weak area. Sometime ago I made a proposal to re-work the model, including extending support for SOAP

[jira] Commented: (AXISCPP-918) generated copy constructor wrong/incomplete

[ http://issues.apache.org/jira/browse/AXISCPP-918?page=comments#action_12368386 ] Adrian Dick commented on AXISCPP-918: - I think the problem you describe is due to WSDL2Ws having very limited support for xsd:extension. This is an area we need

Re: AW: Proposal : Time to release Axis C++ 1.6beta

provide to improve Axis C++. Regards, Adrian ___ Adrian Dick ([EMAIL PROTECTED]) Franz Fehringer [EMAIL PROTECTED] wrote on 01/03/2006 11:34:10: As an additional note i did not check if any of these issues got resolved as a side effect of other bug fixing efforts

[jira] Closed: (AXISCPP-942) Client doesn't handle chunked messages containing very large chunks (48k)

[ http://issues.apache.org/jira/browse/AXISCPP-942?page=all ] Adrian Dick closed AXISCPP-942: --- Client doesn't handle chunked messages containing very large chunks (48k

[jira] Created: (AXISCPP-942) Client doesn't handle chunked messages containing very large chunks (48k)

: Transport (Client), Transport (axis3) Versions: current (nightly) Reporter: Adrian Dick Assigned to: Fred Preston While testing the Axis C++ client against Axis C++ server, hosted on Apache (1.3 and 2.0), I found the returned message contained very large chunks. After some digging

[jira] Resolved: (AXISCPP-901) Compilation error in code generated by WSDL2Ws for SimpleArray(RPC style) wsdl

[ http://issues.apache.org/jira/browse/AXISCPP-901?page=all ] Adrian Dick resolved AXISCPP-901: - Fix Version: current (nightly) Resolution: Fixed I believe this problem has recently been fixed. This was caused by a missing #include within

[jira] Closed: (AXISCPP-937) Server leaks memory for arrays

[ http://issues.apache.org/jira/browse/AXISCPP-937?page=all ] Adrian Dick closed AXISCPP-937: --- Fix Version: current (nightly) Resolution: Fixed I have resolved this by the following: 1) Introducing an additional clone method on Axis_Array

[jira] Created: (AXISCPP-938) soap encoding namespace for xsi:type fails when deserializing basic types

: Server - Deserialization, Client - Deserialization Versions: 1.5 Final, current (nightly) Reporter: Adrian Dick Assigned to: Adrian Dick This problem has been reported on the mailing list: ( http://marc.theaimsgroup.com/?l=axis-c-userm=113892568813046w=2 ) I also recall this problem

[jira] Created: (AXISCPP-939) TypeMapping doesn't include all built-in simple types to the lookup table used for rpc/encoded deserialization

/browse/AXISCPP-939 Project: Axis-C++ Type: Bug Components: Server - Deserialization, Client - Deserialization Versions: current (nightly) Reporter: Adrian Dick Assigned to: Adrian Dick The lookup table in TypeMapping, as used for deserialization of basic types in rpc

[jira] Closed: (AXISCPP-939) TypeMapping doesn't include all built-in simple types to the lookup table used for rpc/encoded deserialization

[ http://issues.apache.org/jira/browse/AXISCPP-939?page=all ] Adrian Dick closed AXISCPP-939: --- Fix Version: current (nightly) Resolution: Fixed I have added the missing types to TypeMapping. TypeMapping doesn't include all built-in simple

[jira] Commented: (AXISCPP-932) Error use of address operator bug

[ http://issues.apache.org/jira/browse/AXISCPP-932?page=comments#action_12367327 ] Adrian Dick commented on AXISCPP-932: - I have now resolved AXISCPP-903 which I believe to be the same problem as you describe here. Can you try the next nightly build

[jira] Created: (AXISCPP-933) Startup trace but not runtime trace fails on shutdown

(nightly) Reporter: Adrian Dick Assigned to: Adrian Dick When startup trace is used, but not runtime trace, the trace file handle is not correctly cleaned up after closing, causing ModuleUninitialize to fail. -- This message is automatically generated by JIRA. - If you think it was sent

[jira] Closed: (AXISCPP-933) Startup trace but not runtime trace fails on shutdown

[ http://issues.apache.org/jira/browse/AXISCPP-933?page=all ] Adrian Dick closed AXISCPP-933: --- Fix Version: current (nightly) Resolution: Fixed Startup trace but not runtime trace fails on shutdown

[jira] Created: (AXISCPP-934) Services are unloaded before last message objects have been deleted

Versions: current (nightly) Reporter: Adrian Dick Assigned to: Adrian Dick The ModuleUninitialize method deletes the handler loader before deleting the SoapSerializer. This results in the service libraries being unloaded before the last message objects have been deleted

[jira] Created: (AXISCPP-935) Delete method in generated beans does not correctly delete arrays of the given type.

: Bug Components: WSDL processing - RPC, WSDL processing - Doc Versions: current (nightly) Reporter: Adrian Dick Assigned to: Adrian Dick The generated delete method (as handed into the engine for serialization) does not correctly delete arrays of that type. It currently does

[jira] Created: (AXISCPP-936) Server leaks memory for arrays if simple types.

) Reporter: Adrian Dick Assigned to: Adrian Dick When the server-side serializer cleans up the last message it doesn't completely delete arrays of simple types. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http

[jira] Updated: (AXISCPP-936) Server leaks memory for arrays of simple types.

[ http://issues.apache.org/jira/browse/AXISCPP-936?page=all ] Adrian Dick updated AXISCPP-936: Summary: Server leaks memory for arrays of simple types. (was: Server leaks memory for arrays if simple types.) Server leaks memory for arrays of simple

  1   2   3   4   >