Fw: Dushshantha: FaultMappingDoc broken

hanks, Mark Mark Whitlock IBM - Forwarded by Mark Whitlock/UK/IBM on 18/08/2005 11:17 - "Samisa

Dushshantha: FaultMappingDoc broken

ike the SoapDeSerializer is stepping over one too many tags. FaultMappingRepeatedDoc and OtherFaultException also fail in the same way. I guess the same problem may happen for rpc-encoded. I don't understand what you were fixing so I don't like to back out your change. Please could you help me to fix this? Thanks, Mark Mark Whitlock

Solaris sockets problem

et on Solaris. MSG_DONTROUTE has been in the code since the original version of the first transport, so I don't know why it was added. If I don't hear otherwise, I'll remove it from the code for all platforms, since the tests work without it. Mark Mark Whitlock

[jira] Created: (AXISCPP-795) Errno not returned when SERVER_TRANSPORT_SOCKET_CREATE_ERROR is thrown

(axis3) Reporter: Mark Whitlock I ran a testcase with an endpoint url pointing at a machine that was not configured to accept incoming connections. I got an HTTPTransportException, and the exception code was SERVER_TRANSPORT_SOCKET_CREATE_ERROR which is reasonable. Unfortunately errno was

Fw: [VOTE] John Kelly for committer

+1 Mark Mark Whitlock - Forwarded by Mark Whitlock/UK/IBM on 09/08/2005 16:49 - John Hawkins/UK/[EMAIL PROTECTED

[jira] Commented: (AXISCPP-778) WSDL2Ws generates bad code with multiple xsd:any's in a complex type

[ http://issues.apache.org/jira/browse/AXISCPP-778?page=comments#action_12317607 ] Mark Whitlock commented on AXISCPP-778: --- Here's a snippet of my schema that I was using I think

[jira] Created: (AXISCPP-778) WSDL2Ws generates bad code with multiple xsd:any's in a complex type

ssing - Doc Reporter: Mark Whitlock I had a wsdl that has a complex type that contained a sequence of xsd:any, xsd:int and another xsd:any. The class that WSDL2Ws generated contained two AnyType's both with a field name of any and no int. Firstly the int was missing. Secondly the

Socket send() hangs on Solaris with more than 75K

I've tried trawling the Solaris bug reports and google but with no luck. When I try reproducing this problem in a testcase not using Axis but using the same socket APIs that Axis uses, I can't reproduce this problem. Has anyone seen a similar problem, or got any ideas on what the problem

[jira] Commented: (AXISCPP-743) SoapDeSerializer::getAttribute does not use namespace

[ http://issues.apache.org/jira/browse/AXISCPP-743?page=comments#action_12317347 ] Mark Whitlock commented on AXISCPP-743: --- Hi Dushshantha, I guess the way of recreating the problem is to write a test that has 2 elements with the same name but

Arrays of pointers to objects

cause array elements are no longer contiguous. Comments? I'm away for a week or so, so will not respond immediately to any discussion, Mark Mark Whitlock IBM

[jira] Closed: (AXISCPP-669) Client-side Attachment doc/lit support

[ http://issues.apache.org/jira/browse/AXISCPP-669?page=all ] Mark Whitlock closed AXISCPP-669: - Resolution: Fixed This support has now been completed > Client-side Attachment doc/lit supp

[jira] Assigned: (AXISCPP-669) Client-side Attachment doc/lit support

[ http://issues.apache.org/jira/browse/AXISCPP-669?page=all ] Mark Whitlock reassigned AXISCPP-669: - Assign To: Mark Whitlock > Client-side Attachment doc/lit support > -- > > Key:

Re: Memory model for arrays and complex types (was: Carsten: please help)

Mark Mark Whitlock IBM Nadir Amra <[EMAIL P

Fw: Integrating Guththila with axis-c++

se as well and I will commit them. Mark Mark Whitlock IBM - Forwarded by Mark Whitlock/UK/IBM on 18/07/2005 14:47 - Din%$h <[EMAIL P

Memory model for arrays and complex types (was: Carsten: please help)

roblem and if so, why? Does anyone have any comments on this proposal? Mark Mark Whitlock IBM

Fw: Using STL (Was: Exception model (more thoughts))

had lengthy discussions in the past about STL on this mailing list. Does anyone have links to the threads? Mark Mark Whitlock IBM - Forwarded by Mark Whitlock/UK/IBM on 16/07/2005 21:57 - "Henrik Nor

[jira] Created: (AXISCPP-744) Trace: no returnIndex set in SoapDeSerializer::getElement

Whitlock Assigned to: Mark Whitlock The SoapDeSerializer::getElement has lots of returns, and yet the exit trace of this method does not have the return index set. Looking at the instrumented code, this is a problem in the trace tool. -- This message is automatically generated by JIRA. - If

[jira] Closed: (AXISCPP-737) If same ISOAPAttachment object is passed as arguments to a service, Axis Engine creates an invalid SOAP Message

[ http://issues.apache.org/jira/browse/AXISCPP-737?page=all ] Mark Whitlock closed AXISCPP-737: - Resolution: Fixed The fix to AXISCPP-732 also fixed this problem. > If same ISOAPAttachment object is passed as arguments to a service, Axis >

[jira] Closed: (AXISCPP-732) Content-type header appears twice in MIME Header

[ http://issues.apache.org/jira/browse/AXISCPP-732?page=all ] Mark Whitlock closed AXISCPP-732: - Resolution: Fixed I have now fixed this problem by separating out SoapAttachmentReference from SoapAttachment. This allows a ISoapAttachment to be

[jira] Created: (AXISCPP-743) SoapDeSerializer::getAttribute does not use namespace

SoapDeSerializer::getAttribute does not use namespace - Key: AXISCPP-743 URL: http://issues.apache.org/jira/browse/AXISCPP-743 Project: Axis-C++ Type: Bug Components: Client - Deserialization Reporter: Mark

[jira] Closed: (AXISCPP-704) Problem in setSOAPMethodAttribute API in Call class

[ http://issues.apache.org/jira/browse/AXISCPP-704?page=all ] Mark Whitlock closed AXISCPP-704: - Resolution: Fixed I have now fixed problems 2 and 3. Problem 1 results in a useful SOAP fault being returned from the server, so there is no need to

Out of memory error when running tests under ant on AIX

Hi, We have been experiencing "out of memory" errors when running tests on AIX under ant. We believe the fix for this is to set the environment variable... ANT_OPTS=-Xmx256m Letting you know in case anyone else has the same problem, Mark Mark Whitlock IBM

Fw: Exception model (more thoughts)

Thanks :-) Mark Whitlock IBM - Forwarded by Mark Whitlock/UK/IBM on 12/07/2005 11:24 - "Samisa Abeys

[jira] Closed: (AXISCPP-445) Add Calculator C test

[ http://issues.apache.org/jira/browse/AXISCPP-445?page=all ] Mark Whitlock closed AXISCPP-445: - Resolution: Fixed A Calculator C test has now been added > Add Calculator C test > - > > Key: AXISCPP-445 &g

Fw: Re: FIXED: RE: Carston: please help

m but I didn't. Mark Mark Whitlock IBM - Forwarded by Mark Whitlock/UK/IBM on 08/07/2005 11:40 - Samisa Abeysinghe <[EM

FIXED: RE: Carston: please help

elete. This ensures that the array that's being deleted doesn't reference the strings that we want to keep. I don't like memset'ing objects to zero - I think I'll assign to them a clean class whose fields have their default values. Thank you for your help in solving t

[jira] Assigned: (AXISCPP-704) Problem in setSOAPMethodAttribute API in Call class

[ http://issues.apache.org/jira/browse/AXISCPP-704?page=all ] Mark Whitlock reassigned AXISCPP-704: - Assign To: Mark Whitlock > Problem in setSOAPMethodAttribute API in Call cl

Fw: RE: Carsten: please help

ncluding myself). Reluctantly I propose that I back out your fix from BeanParamWriter until AxisBench and ComplexLists work with your fix. Unless I hear from you otherwise, I will do this first thing tomorrow morning. Mark Mark Whitlock IBM - Forwarded by Mark Whitlock/UK/IBM on 0

Fw: unitTest in build process

Hi Dushshantha, The corrupted strings in ComplexLists is a separate problem that Carsten and I are working on. It also affects AxisBench. Of course if you see the fix to it, please let us know :-) Mark Mark Whitlock IBM - Forwarded by Mark Whitlock/UK/IBM on 07/07/2005 09:47

Carston: please help

he problem might be? Any help would be greatly appreciated, Thanks, Mark Mark Whitlock IBM

Fw: Dushshantha: Exception model

Hi Dushshantha, Yes that's fixed it. Thanks! Mark Mark Whitlock IBM - Forwarded by Mark Whitlock/UK/IBM on 06/07/2005 11:13 - "D

Dushshantha: Exception model

know why it can't cast a temporary to a reference? If you can fix this properly, please go ahead, Thanks, Mark Mark Whitlock IBM

[jira] Updated: (AXISCPP-727) User SOAP Faults lost

[ http://issues.apache.org/jira/browse/AXISCPP-727?page=all ] Mark Whitlock updated AXISCPP-727: -- Component: Server - General Added server as a component. > User SOAP Faults lost > - > > Key: AXISCPP-727 &g

[jira] Commented: (AXISCPP-727) User SOAP Faults lost

[ http://issues.apache.org/jira/browse/AXISCPP-727?page=comments#action_12315032 ] Mark Whitlock commented on AXISCPP-727: --- Hi Henrik, Please could you confirm that this problem is specific to the server. I checked the cvs history of SoapSerializer

[jira] Closed: (AXISCPP-406) Make AxisTrace work better with TraceAnalyzer

[ http://issues.apache.org/jira/browse/AXISCPP-406?page=all ] Mark Whitlock closed AXISCPP-406: - Resolution: Fixed All the problems reported in this JIRA have now been fixed except for multiline output AXISCPP-728 and throw out trace AXISCPP-729

[jira] Created: (AXISCPP-729) Trace: Unwind the call stack when exceptions are thrown

Whitlock Assigned to: Mark Whitlock When Axis C++ throws exceptions, the trace analyzer tool does not realise that the call stack should be unwound. Consequently, it appears in the trace that the method that threw the exception calls the method that catches the exception. For traces that contain

[jira] Created: (AXISCPP-728) Trace: better multiline output

Trace: better multiline output -- Key: AXISCPP-728 URL: http://issues.apache.org/jira/browse/AXISCPP-728 Project: Axis-C++ Type: Bug Components: Trace Utility Reporter: Mark Whitlock Assigned to: Mark Whitlock Priority

FW: Exception model (more thoughts)

Mark Whitlock IBM - Forwarded by Mark Whitlock/UK/IBM on 04/07/2005 14:56 - Mark Whitlock/UK/IBM

Re: FW: Exception model

is is probably a good fix since I can't see why C applications would need to construct AxisExceptions. Please get back to me if you still have problems, Mark Mark Whitlock IBM - Forwarded by Mark Whitlock/UK/IBM on 04/07/

Attachments wsdl

, DataSource and MimeMultipart into wsdl2ws.jar. Mark Mark Whitlock IBM

Nightly build out of date

Due a machine outage the CVS nightly build and test results at http://cvs.apache.org/dist/axis/nightly/ are several days out of date. This is being worked on and will be resolved soon. Mark Mark Whitlock IBM

[jira] Created: (AXISCPP-712) Attributes not supported on the SOAP header

Attributes not supported on the SOAP header --- Key: AXISCPP-712 URL: http://issues.apache.org/jira/browse/AXISCPP-712 Project: Axis-C++ Type: Wish Components: Client - API Reporter: Mark Whitlock Attributes are not

Fw: Samisa: TestSoapHeaderBlock fixed

Hi Samisa, I have raised AXISCPP-712 to externalise this support Mark Mark Whitlock IBM - Forwarded by Mark Whitlock/UK/IBM on 28/06/2005 10:53 - Samisa Abeysinghe

Samisa: TestSoapHeaderBlock fixed

ceDecl and Axis C++ built successfully. So no one sets attributes or namespaces on the SoapHeader. So there is code here that is never executed. Are Attributes and Namespaces on SoapHeader redundant, or should the methods to add them be externalised? Mark Mark Whitlock IBM

[jira] Created: (AXISCPP-702) UDDI tests should be run every night

UDDI tests should be run every night Key: AXISCPP-702 URL: http://issues.apache.org/jira/browse/AXISCPP-702 Project: Axis-C++ Type: Test Components: Test Reporter: Mark Whitlock The UDDI tests should be run every night

[jira] Created: (AXISCPP-703) Call::setSOAPMethodAttribute not tested

Call::setSOAPMethodAttribute not tested Key: AXISCPP-703 URL: http://issues.apache.org/jira/browse/AXISCPP-703 Project: Axis-C++ Type: Test Components: Test Reporter: Mark Whitlock The Call::setSOAPMethodAttribute

SOAP method attributes on Stub

I have removed m_vSOAPMethodAttributes and m_viCurrentSOAPMethodAttribute from Stub since these appear to be unused and redundant. It builds and tests fine without them. If they are required, please add them back in and accept my apologies, Mark Mark Whitlock IBM

[jira] Created: (AXISCPP-699) Missing tests for common user errors involving files and directories at initialisation

++ Type: Test Components: Test Reporter: Mark Whitlock There are a bunch of tests missing such as... - axiscpp.conf not found (this is not an error) - no permission to read axiscpp.conf - bad owner/group on axiscpp.conf - Incorrect spelling of keywords (ClientLogPath) in axiscpp.conf

Fw: Today build Fail

Fixed and committed Mark Mark Whitlock IBM - Forwarded by Mark Whitlock/UK/IBM on 16/06/2005 10:44 - Mark Whitlock/UK/IBM

Fw: Today build Fail

Hi Samisa, Apologies - it was my code that broke it - I'll fix it by making ContentIdSet optional on SoapAttachment::SoapAttachment. Mark Mark Whitlock IBM - Forwarded by Mark Whitlock/UK/IBM on 16/06/2005

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

t the WSDL MIME binding used (by Axis/Java)? Mark Mark Whitlock IBM

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

: Transport (axis3) Reporter: Mark Whitlock I was using the dynamic client API against a server that did not require SOAPAction to be set. So I did not set SOAPAction in my client application. When I invoked the web service I got a SIGSEGV out of HTTPTransport.FindTransportIndex [13/06

Attachments

n the soap body, providing support for referenced attachments. So I will change the methods that take the Content-ID as a char* to be a IAttachmentReference*. Comments? Mark Mark Whitlock IBM

[jira] Assigned: (AXISCPP-679) Data not passed back from multiple output parameters

[ http://issues.apache.org/jira/browse/AXISCPP-679?page=all ] Mark Whitlock reassigned AXISCPP-679: - Assign To: Mark Whitlock > Data not passed back from multiple output paramet

[jira] Closed: (AXISCPP-679) Data not passed back from multiple output parameters

[ http://issues.apache.org/jira/browse/AXISCPP-679?page=all ] Mark Whitlock closed AXISCPP-679: - Resolution: Fixed This issue is now fixed and tested by the MultiOut unit test > Data not passed back from multiple output paramet

[jira] Created: (AXISCPP-688) Missing multiple output/inout parameter tests

Missing multiple output/inout parameter tests - Key: AXISCPP-688 URL: http://issues.apache.org/jira/browse/AXISCPP-688 Project: Axis-C++ Type: Test Components: Test Reporter: Mark Whitlock There are a variety of

[jira] Created: (AXISCPP-680) Compiler warnings

Compiler warnings - Key: AXISCPP-680 URL: http://issues.apache.org/jira/browse/AXISCPP-680 Project: Axis-C++ Type: Bug Components: Basic Architecture Reporter: Mark Whitlock Priority: Minor On Windows, users get compiler warnings when

[jira] Created: (AXISCPP-681) STL used in generated stubs

STL used in generated stubs --- Key: AXISCPP-681 URL: http://issues.apache.org/jira/browse/AXISCPP-681 Project: Axis-C++ Type: Bug Components: WSDL processing - Doc Reporter: Mark Whitlock STL is used in generated stubs in the

All tests are broken

Hi, All tests broke on all platforms last night due to a java.net.MalformedURLException: unknown protocol: c out of wsdl2ws when building each test. I am currently investigating and will keep this list posted when it is fixed. Mark Mark Whitlock IBM

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

Problems with XSD types in AxisUserAPI.hpp -- Key: AXISCPP-676 URL: http://issues.apache.org/jira/browse/AXISCPP-676 Project: Axis-C++ Type: Bug Components: Basic Architecture Reporter: Mark Whitlock In

[jira] Created: (AXISCPP-679) Data not passed back from multiple output parameters

Data not passed back from multiple output parameters Key: AXISCPP-679 URL: http://issues.apache.org/jira/browse/AXISCPP-679 Project: Axis-C++ Type: Bug Components: WSDL processing - Doc Reporter: Mark

[jira] Created: (AXISCPP-677) WSDL2Ws fails with NullPointerException

WSDL2Ws fails with NullPointerException --- Key: AXISCPP-677 URL: http://issues.apache.org/jira/browse/AXISCPP-677 Project: Axis-C++ Type: Bug Components: WSDL processing - Doc Reporter: Mark Whitlock This wsdl makes

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

WSDL2Ws generates header that does not compile -- Key: AXISCPP-678 URL: http://issues.apache.org/jira/browse/AXISCPP-678 Project: Axis-C++ Type: Bug Components: WSDL processing - Doc Reporter: Mark Whitlock This

Deserializing attachments

ave implemented but not yet committed. Or am I missing something? Mark Mark Whitlock IBM

[jira] Created: (AXISCPP-673) Test WSDL containing message with no parts

Test WSDL containing message with no parts -- Key: AXISCPP-673 URL: http://issues.apache.org/jira/browse/AXISCPP-673 Project: Axis-C++ Type: Test Components: Test Reporter: Mark Whitlock A test should be added to

[jira] Created: (AXISCPP-672) WSDL2Ws fails when message has no parts

WSDL2Ws fails when message has no parts --- Key: AXISCPP-672 URL: http://issues.apache.org/jira/browse/AXISCPP-672 Project: Axis-C++ Type: Bug Components: WSDL processing - Doc Reporter: Mark Whitlock WSDL2Ws fails with

[jira] Commented: (AXISCPP-672) WSDL2Ws fails when message has no parts

[ http://issues.apache.org/jira/browse/AXISCPP-672?page=comments#action_12312745 ] Mark Whitlock commented on AXISCPP-672: --- this is related to AXISCPP-673 > WSDL2Ws fails when message has no pa

Fw: Channel loading causes stress test problems

ion that IBM is interested in and it's not tested but I've tried to ensure that I haven't broken it for whoever uses it. Please alter this implementation if you need to. BTW I'm on holiday next week, Mark Mark Whitlock IBM - Forwarded by Mark

Channel loading causes stress test problems

could be loaded when the transport and XML parser libraries are loaded during module_initialise called from Axis::initialize. Mark Mark Whitlock IBM

[jira] Commented: (AXISCPP-660) errno not output if library load fails

[ http://issues.apache.org/jira/browse/AXISCPP-660?page=comments#action_66268 ] Mark Whitlock commented on AXISCPP-660: --- This is related to AXISCPP-548 > errno not output if library load fa

[jira] Commented: (AXISCPP-548) Better error msgs when failing to load library

[ http://issues.apache.org/jira/browse/AXISCPP-548?page=comments#action_66267 ] Mark Whitlock commented on AXISCPP-548: --- This is related to AXISCPP-660 > Better error msgs when failing to load libr

[jira] Created: (AXISCPP-660) errno not output if library load fails

errno not output if library load fails -- Key: AXISCPP-660 URL: http://issues.apache.org/jira/browse/AXISCPP-660 Project: Axis-C++ Type: Bug Components: Transport (axis3) Reporter: Mark Whitlock In ChannelFactory, if the

[jira] Commented: (AXISCPP-657) Stress test fails to dlopen channel

[ http://issues.apache.org/jira/browse/AXISCPP-657?page=comments#action_66167 ] Mark Whitlock commented on AXISCPP-657: --- I ran the same test on Windows XP. I never got any dlopen failures. Instead with 50threads * 50loops I got lots of

[jira] Created: (AXISCPP-657) Stress test fails to dlopen channel

Stress test fails to dlopen channel --- Key: AXISCPP-657 URL: http://issues.apache.org/jira/browse/AXISCPP-657 Project: Axis-C++ Type: Bug Components: Basic Architecture Reporter: Mark Whitlock I changed the

[jira] Commented: (AXISCPP-657) Stress test fails to dlopen channel

[ http://issues.apache.org/jira/browse/AXISCPP-657?page=comments#action_66166 ] Mark Whitlock commented on AXISCPP-657: --- I was running this test on AIX. I haven't tried other platforms as yet. > Stress test fails to dlopen

Fw: Platform abstraction layer thoughts

libraries need it. Currently trace entrypoints are called by address from the transport, channel, etc libraries, since these libraries are not linked with AxisClient. This makes for horrible code which would be greatly simplified by moving trace into the new platform abstraction library. Mark Mark Whitlock

Fw: Error when build Axis Client code with C++ Builder 6.0

get in C++ are the Axis C++ entrypoints which are exported from the AxisClient.dll. Unfortunately VC++ and C++ builder have different name-mangling rules. Mark Mark Whitlock IBM - Forwarded by Mark Whitlock/UK/IBM on 24/05/2005 10:14

Attachments in WS-I

ample in section 4.4 "Referencing Attachments from the SOAP Envelope". If the attachment is an element in the wsdl message, then I propose Axis C++ should represent it as a parameter on the generated Stub web service invocation. Comments? Mark Mark Whitlock IBM

Fw: Platform abstraction layer thoughts

be full of such small functions. The advantage of linking the platform-specific code into a separate library is that the transport, channel and XML parser libraries could all link with the PS library (since they are not linked with the AxisClient library). Which do you prefer? Mark Mark Whitlock

Fw: Today CVS Build failing

this break occured on unix platforms as well. Mark Mark Whitlock IBM - Forwarded by Mark Whitlock/UK/IBM on 18/05/2005 14:44 - "Samisa

[jira] Closed: (AXISCPP-649) OtherFaultException not tested

[ http://issues.apache.org/jira/browse/AXISCPP-649?page=all ] Mark Whitlock closed AXISCPP-649: - > OtherFaultException not tested > -- > > Key: AXISCPP-649 > URL: http://issues.apache.

Fw: XSD types

In src/soap/xsd the classes (eg Int.cpp) use hardcoded values because these limits are defined by the SOAP spec. Values from limits.h are platform specific. Mark Mark Whitlock IBM - Forwarded by Mark Whitlock/UK/IBM on 18/05/2005 09:53

Fw: Attachments

Hi Rangika, We build but we don't test the Axis C++ server. We run all our tests against WebSphere Application Server. So unfortunately I don't know whether server-side attachments work on AIX. Mark Mark Whitlock IBM - Forwarded by Mark Whitlock/UK/IBM on 18/05/

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 - Forw

Fw: Attachments

post to the mailing list what changes I intend to make, so that I do not break the server-side support. Thanks, Mark Mark Whitlock IBM - Forwarded by Mark Whitlock/UK/IBM on 17/05/2005 17:25 - Rangika

[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 deallo

[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

XSD types

avoid using longs for xsd types. Nadir - is this the same on OS/400? In the future, we could use LONG_MAX and INT_MAX in #if's to conditionally use the correct primitive for the correct xsd type, for platforms and modes where ints aren't 32 bits. Mark Mark Whitlock IBM

Fw: FFDC (2)

tempted at the time. Mark Mark Whitlock IBM ----- Forwarded by Mark Whitlock/UK/IBM on 16/05/2005 14:14 - "Samisa

[jira] Closed: (AXISCPP-648) Fix build break

[ http://issues.apache.org/jira/browse/AXISCPP-648?page=all ] Mark Whitlock closed AXISCPP-648: - Resolution: Fixed > Fix build break > --- > > Key: AXISCPP-648 > URL: http://issues.apache.org/jira/bro

[jira] Created: (AXISCPP-649) OtherFaultException not tested

OtherFaultException not tested -- Key: AXISCPP-649 URL: http://issues.apache.org/jira/browse/AXISCPP-649 Project: Axis-C++ Type: Test Components: Test Reporter: Mark Whitlock OtherFaultException allows a client application to

Attachments

addAttachment methods on Stub and Call - is this how you imagine it will work? Thank you for your help, Mark Mark Whitlock IBM

[jira] Created: (AXISCPP-648) Fix build break

Fix build break --- Key: AXISCPP-648 URL: http://issues.apache.org/jira/browse/AXISCPP-648 Project: Axis-C++ Type: Bug Components: Build - ANT Reporter: Mark Whitlock Assigned to: Mark Whitlock Priority: Blocker Various builds are

Fw: FFDC

. Someone will probably explain this better than I, Mark Mark Whitlock IBM - Forwarded by Mark Whitlock/UK/IBM on 13/05/2005 17:19 - "Lil

[jira] Closed: (AXISCPP-647) Trace globals cause SIGSEGV in multithreaded test

[ http://issues.apache.org/jira/browse/AXISCPP-647?page=all ] Mark Whitlock closed AXISCPP-647: - Resolution: Fixed Fixed the trace globals that are passed to dynamically loaded shared libraries to make them thread safe. > Trace globals ca

[jira] Created: (AXISCPP-647) Trace globals cause SIGSEGV in multithreaded test

Trace globals cause SIGSEGV in multithreaded test - Key: AXISCPP-647 URL: http://issues.apache.org/jira/browse/AXISCPP-647 Project: Axis-C++ Type: Bug Components: Trace Utility Reporter: Mark Whitlock Assigned

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

[ http://issues.apache.org/jira/browse/AXISCPP-551?page=all ] Mark Whitlock reassigned AXISCPP-551: - Assign To: Adrian Dick (was: Mark Whitlock) Adrian is working on faults now > getAnyObject() API in call class does not return SOAP Fa

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

[ http://issues.apache.org/jira/browse/AXISCPP-476?page=all ] Mark Whitlock reassigned AXISCPP-476: - Assign To: Adrian Dick (was: Mark Whitlock) Adrian is working on faults now > Memory leak throwing user-defined soap fau

Fw: FFDC (2)

If we required toString() methods in our classes, then the existing trace tool could generate these toString() methods during the build, since it already parses class definitions and recognises fields within them. Mark Mark Whitlock IBM - Forwarded by Mark Whitlock/UK/IBM on 13/05/2005 13

Fw: FFDC

tAxisEngine.toString(), ..., etc, which in turn would call the toString() method on all other objects. Mark Mark Whitlock IBM ----- Forwarded by Mark Whitlock/UK/IBM on 13/05/2005 13:22 -

  1   2   3   >