Thanks a lot Toshiyuki.
Sanjesh
-----Original Message-----
From: Toshiyuki Kimura [mailto:[EMAIL PROTECTED]
Sent: Friday, April 04, 2003 11:26 AM
To: [EMAIL PROTECTED]
Subject: Re: Handler order
Hi Sanjesh,
I scanned the version on 1.1RC2 and the latest nightly build
of the code. Both codes include the following note;
/**
* Returns the configured HandlerRegistry instance for this Service
* instance.
*
* NOTE: This Service currently does not support the configuration
* of a HandlerRegistry! It will throw a
* java.lang.UnsupportedOperationException.
*
* @return HandlerRegistry
* @throws java.lang.UnsupportedOperationException - if the Service
* class does not support the configuration of a
* HandlerRegistry.
*/
public HandlerRegistry getHandlerRegistry() {
return registry;
}
Best Regards,
Toshi (Toshiyuki Kimura) <[EMAIL PROTECTED]>
R&D Headquarters
NTT DATA Corporation
----- Original Message -----
From: "Pathak, Sanjesh" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Saturday, April 05, 2003 12:17 AM
Subject: RE: Handler order
>
> Hi Toshiyuki,
>
> Thanks for the reply. What I want to do is display to the user the order
> of the handlers in request flow and response flow for a given service.
> As you suggessted in the code below I found the Service class
> (org.apache.axis.client.Service). I tried to use it's method
> getHandlerRegistry(). But I am still unsuccessfull. Please let me know
> if you find anything more on this. Thanks again.
>
> Sanjesh
>
> -----Original Message-----
> From: Toshiyuki Kimura [mailto:[EMAIL PROTECTED]
> Sent: Friday, April 04, 2003 6:53 AM
> To: [EMAIL PROTECTED]
> Subject: RE: Handler order
>
> Hi Sanjesh,
>
> Which are you talking about the JAX-RPC handler, or AXIS specified
> handler ? And what do you want to do with the programming.
>
> In case of JAX-RPC, the spec specifies a few Handler Configuration
> APIs, for example 'getHandlerRegistry', 'getHandlerChain'. I add a
> snippet of the code;
>
> .........*.........*.........*.........*.........*.........*.........*
> import javax.xml.rpc.handler.*;
> import javax.xml.namespace.*;
> import java.Util.*;
> :
> :
> HandlerRegistry hr = service.getHandlerRegistry();
> List hl = hr.getHandlerChain(new
> javax.xml.namespace.QName("qname"));
>
> for (int i=hl.size(); i>0; i--) {
> HandlerInfo hi = (javax.xml.rpc.handler.HandlerInfo)hl.get(i);
> Class handlerClass = hi.getHandlerClass();
> }
> .........*.........*.........*.........*.........*.........*.........*
>
> NOTE: The above code is just a sample programming. I didn't check
> whether it works well or not. And I'm not sure AXIS has
> implemented these APIs faithfully.
>
> Best Regards,
>
> Toshi (Toshiyuki Kimura) <[EMAIL PROTECTED]>
> R&D Headquarters
> NTT DATA Corporation
>
> -----Original Message-----
> From: Pathak, Sanjesh [mailto:[EMAIL PROTECTED]
> Sent: Friday, April 04, 2003 1:35 AM
> To: [EMAIL PROTECTED]
> Subject: Handler order
>
> Hi,
>
> I am trying to get handlers (and their order) that are there
> in the response flow, request flow and fault flow of a service.
> Does anyone know if there is a programmatic way or an API to get
> the order the of the handlers in response flow, request flow and
> fault flow of a deployed service?
>
> Sanjesh
>
> **********************************************************************
> This e-mail is the property of Enron Corp. and/or its relevant affiliate
> and may contain confidential and privileged material for the sole use of
> the intended recipient (s). Any review, use, distribution or disclosure
> by others is strictly prohibited. If you are not the intended recipient
> (or authorized to receive for the recipient), please contact the sender
> or reply to Enron Corp. at [EMAIL PROTECTED] and
> delete all copies of the message. This e-mail (and any attachments
> hereto)
> are not intended to be an offer (or an acceptance) and do not create or
> evidence a binding and enforceable contract between Enron Corp. (or any
> of its affiliates) and the intended recipient or any other party, and
> may not be relied on by anyone as the basis of a contract by estoppel or
> otherwise. Thank you.
> **********************************************************************
>
