Re: Attachments - AXIS Server, .NET Client

Hi, John, Could you please share your C# client code with us since the reference is so hard to find on this topic in the .NET society? I am writing a C# client to send an attachment to an Axis server. Thanks, Scott [John Walker wrote] Do you mean the .NET client side? I have

Is service endpoint in service locator class in server side code actually used?

Hi, All, There is this service address in both client and server side service locator classes. // Use to get a proxy class for MyService private final java.lang.String MyService_address = http://xxx/services/MyEndPoint;; On client side this is where a client sends the service request.

Stub.getHeader in axis 1.1 or 1.2

It looks like both getHeader() and Stub.getResponseHeaders() are deprecated in axis 1.1. as discussed a little while ago in the attached message. Does anyone know an alternative way to access soap headers in an Axis client? I have not tried 1.2 yet and do not know if it works there. In

RE: Stub.getHeader in axis 1.1 or 1.2

) the response headers. -- Tom Jordahl Macromedia Server Development -Original Message- From: Liu, Scott [mailto:[EMAIL PROTECTED] Sent: Thursday, December 09, 2004 4:08 PM To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Stub.getHeader in axis 1.1 or 1.2

Why can't I have a enum type element as a request parameter?

Hi, All, I am using the wrapper style and I encountered a runtime exception with a new operation I just created with a enum request parameter. My operation getAll is a query to get all records for a given record type which is defined as a enum type. The related schema is as follows.

RE: The Attributes and the UN-wrapper style

affecting the abstract description or the client. Jeff - Original Message - From: Liu, Scott [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, September 10, 2004 4:31 PM Subject: The Attributes and the UN-wrapper style Hi, All, There has been discussion about the wrapper style

The Attributes and the UN-wrapper style

Hi, All, There has been discussion about the wrapper style and the attributes in the past. And Axis does not support wrapper element attributes since JAX-RPC spec says that the wrapper element should not have attributes. I have no problem with it. But I do like people to clarify the following

RE: How to enable Axis client to return more than one cookie

On Sun, 8 Aug 2004 14:40:52 -0700, Liu, Scott [EMAIL PROTECTED] wrote: I updated my code according to the patch (the diff file) and it works now. I did not use all the changes suggested in HTTPTransport class. I only made a simple change in processReturnedMessageContext() like cookies

RE: Strange behavior on soap message generated by axis1.1?

-Original Message- From: Liu, Scott Sent: Friday, August 06, 2004 6:01 PM To: [EMAIL PROTECTED] Subject: Strange behavior on soap message generated by axis1.1? I used Axis 1.1 RC2 before I switched to the stable Axis 1.1 final version (June 2003). Then the RESPONSE soap message in my

RE: How to enable Axis client to return more than one cookie

for all the good work, Scott -Original Message- From: Liu, Scott Sent: Thursday, August 05, 2004 12:18 PM To: [EMAIL PROTECTED] Subject: RE: How to enable Axis client to return more than one cookie Thanks. The patch has not been checked in yet. The patch link only provides differences. Does

Strange behavior on soap message generated by axis1.1?

I used Axis 1.1 RC2 before I switched to the stable Axis 1.1 final version (June 2003). Then the RESPONSE soap message in my service was changed to an undesired form. The message looks like this. ?xml version=1.0 encoding=UTF-8? soapenv:Envelope

RE: How to enable Axis client to return more than one cookie

, Scott -Original Message- From: Liu, Scott Sent: Wednesday, August 04, 2004 10:17 PM To: [EMAIL PROTECTED] Subject: How to enable Axis client to return more than one cookie Hi, All, I have a question on cookie or session management. This has been baffling me for a while. Hope

RE: How to enable Axis client to return more than one cookie

] Sent: Thursday, August 05, 2004 11:33 AM To: [EMAIL PROTECTED] Subject: Re: How to enable Axis client to return more than one cookie http://issues.apache.org/jira/browse/AXIS-1080 - Original Message - From: Liu, Scott [EMAIL PROTECTED] Date: Thu, 5 Aug 2004 08:43:28 -0700 Subject: RE: How

How to enable Axis client to return more than one cookie

Hi, All, I have a question on cookie or session management. This has been baffling me for a while. Hope that someone there has solved a similar problem. In the application I am running there are two cookies from server. First one is the JSESSIONID and the second one is application

RE: Illegal XML character: amp;#x0;. DONOT see this character in TCP Mon

Will anyone in the Axis community care to respond? Or is this a fact of life? Thanks, Scott -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Friday, July 30, 2004 8:54 AM To: [EMAIL PROTECTED] Subject: Illegal XML character: amp;#x0;. DONOT see this character

Illegal XML character revisit and ways to handle the exception

Hi, All, Searching from the mailing list and I have found several past entries about the illegal XML character topic but none of them have given a definite answer. I would like to know how people are handling them in their applications. My own example is due to the fact that there are

RE: Is Axis creating a DOM object and hence it may cause memory issue?

:[EMAIL PROTECTED] Sent: Tuesday, April 13, 2004 1:38 PM To: [EMAIL PROTECTED] Subject: RE: Is Axis creating a DOM object and hence it may cause memory issue? The Axis Messaging interface returns a DOM. Use the JAX-RCP interface instead. It returns Java types. From: Liu, Scott [mailto

RE: Is Axis creating a DOM object and hence it may cause memory issue?

the RPC provider (RPC, Wrapped, or Document style), Axis uses SAX to parse the message and convert the XML to Java objects. When using the MSG provider (Message style), Axis converts the message into a DOM. From: Liu, Scott [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 14, 2004 6:10

Is Axis creating a DOM object and hence it may cause memory issue?

I have read somewhere that Axis uses SAX parser and the memory is basically well managed. But in org.apache.axis.message.SOAPBodyElement class the getDocumentElement method is implemented as such private static Element getDocumentElement(InputStream input) { try { return

Intercept XML payload for modification

From reading axis architecture guide it seems feasible to add a customized handler in the handler chain so that operations could be performed on the raw xml payload. Can anyone please share some experience or sample code with me on doing this or tell me if there is a better way to modify

Found another user experiencing similar null response problem with .NET client working with Axis web service server

I dont know if I am happy with my discovery or not. I have tried to solve my problem with null response with .NET/C# client working with Axis WS server in last week and found that there was another Axis user experienced similar problem which was posted to Microsoft newsgroup in last

Help: .NET C# client failed to generate an object corresponding to a valid soap message in AXIS WS application

Hi, All, This problem really frustrates me. Even though it looks more like a .NET WS support problem than AXIS problem I post it here in hoping that AXIS developers have used .NET clients and may provide me suggestions to address the issue. I have a AXIS web service running as the

namespace and java class mapping

Hi, All, In using WSDL2java to generate java classes Axis creates java packages using the namespaces by default. When there is only one namespace there is a command option -p to create classes for a user defined package. Does anyone know if there is a way to map more than one namespace to