OK - thanks for this explanation. I want to use a JAX-RPC handler in a non-service specific way, but can't make use of JAXRPCHandler class because of some problems noted in an earlier post to th is list.
I am going to try to come up with a patch for JAXRPCHandler and post it along with a bug report. -- Mark > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Thursday, December 11, 2003 11:44 AM > To: [EMAIL PROTECTED] > Subject: Re: intended purpose of JAXRPCHandler class ?? > > > > When deploying JAX-RPC handlers using via WSDD and the > <handlerInfoChain> > element, you can't decide _when_ your handlers will be > invoke. They will > always be invoked between the global chain and the > service-specific chain > (on the server side), or between the global chain and the transpot > specific chain (on the client side), resp. Furthermore, they > are always > service specific. > > Using JAXRPCHandler may have some drawbacks, since this class > seems to need > some fixes, but nevertheless you'll have the opportunity to > plug JAX-RPC > style handlers into any chain, like a transport-specific > chain for example. > > > > > Mark D. Hansen wrote: > > > Does anybody know what JAXRPCHandler is supposed to be used > for? After digging around in the source code, I finally > figured out how to deploy services using JAX-RPC handlers via > WSDD and the <handlerInfoChain> element. So, if > <handlerInfoChain> is the intended method for deployment of > JAX-RPC handlers, what is the class JAXRPCHandler used for? > > > > Thanks for any insights. > > > > -- Mark > > > > >
