How to retrieve a client set property?

Hello, I want the client to be able to set a property to affect the behavior of an outbound handler. However, I haven't figured out how to obtain the property from within my handler. How can I retrieve the property? I'm using the following client code to set the property:

How to specify code and subcode on generated fault

How can my server side handler generate a fault with specific values for code and subcode? I don't see an API to do it. The only option I see if to manually generate the fault message, but that's messy because of SOAP versions etc.

Can a module include a transport?

Can a module include a transport? I've tried and it doesn't seem to work. It looks like Axis2 loads the transports before it loads the modules. Is there a preferred way to distribute a new transport other than placing it in the Axis classes directory? Is there any reason why modules couldn't be

Re: WS-Addressing ReplyTo processing

Thanks for the response. Is it possible for an user to change Axis2 handling of ReplyTo on the service side? In particular I'd like another URI to be treated in the same way as the WSA defined anonymous URI which indicates that the response is returned on the existing connection. I've looked

WS-Addressing ReplyTo processing

The WS-Addressing specification states that if a ReplyTo header is included in a request message, then the reply message should be sent to the EPR specified in the ReplyTo header, not as a response on the original request connection. Does Axis2 handle this for a web service implemented with

Axis2 on J2ME

Can Axis2 run within a J2ME environment? Are there any expected problems or limitations running within this environment? Thanks Sick sense of humor? Visit Yahoo! TV's Comedy with an Edge to see what's

Logging, response code 500

I've had multiple instances where I attempt to invoke a web service on Axis2 and recieve a fault with response code 500. No exception is logged on the server, nor any other obvious additional information. Is there some way to enable logging on Axis2 so that it can log an exception or provide

Re: Axis1 style=message in Axis2?

the action. That should do it :) Ajith On 8/16/06, David Melgar [EMAIL PROTECTED] wrote: I'm still trying to figure out how to deploy a message style service WITHOUT having to declare each possible wsa:Action value which might be used on the invocation. Its a message style service... I dont want

Re: Axis1 style=message in Axis2?

On 26/07/06, David Melgar [EMAIL PROTECTED] wrote: Setting the message receiver to RawXMLMessageReceiver still appears to require actionMapping to determine which method

Re: Axis1 style=message in Axis2?

To axis-user@ws.apache.org cc Subject Re: Axis1 style=message in Axis2? Use the RawXMLMessageReceiver. On 7/25/06, David Melgar [EMAIL PROTECTED] wrote: I need to implement a message style web service in Axis2. In Axis1 wsdd, this would be a web service declared with service

Axis1 style=message in Axis2?

I need to implement a message style web service in Axis2. In Axis1 wsdd, this would be a web service declared with service name=xxx style=message How do I declare the equivalent web service in Axis2? In addition, I will expect that WS-Addressing headers will be sent and received. From reading