Here's a cut-paste from the spec:
12.3.1 Handler Configuration APIs
If a JAX-RPC runtime system has its own implementation specific handlers, the JAX-RPC
runtime system is not required to expose its internal handlers to the service client
developer. This enables a JAX-RPC runtime system to separate user-configured handlers
from its internal handlers.
If I was writing something that comprised of more than one service, one way would be to remind each service provider to put the handler chain
declaration in their config.xml. This is what I want to avoid/bypass. If there is some way I can tell the runtime that all messages
(irrespective of the services that they were intended for) need to be processed by these handlers? i.e. I want to make these "internal
handlers" and not service-specific.
Thanks
Sang Shin wrote:
> Pratibha Gupta wrote:
> >
> > You have described on the mailing list how to define handlers for a
> > particular service. Suppose I wanted to write global handler
> > chains i.e. handlers that would process all messages irrespective of the service they were intended for (in addition to the service's own
> > handlers). I think the spec calls them "internal handlers". How and where do I define these handler chains?
> >
> > Thanks,
> > Pratibha
>
> (I am not working in JAX-RPC group. So these are my
> personal interpretation of the spec.)
>
> The spec says the following:
>
> "A handler chain is registered per service endpoint, as
> indicated by the qualified name of
> a port. The getHandlerChain returns the handler chain for
> the specified service
> endpoint. ..."
>
> So for now, it seems you can set chain of handlers only per
> service
> basis.
>
> --
>
> ---------------------------------------------
> Sang Shin sang.shin_at_sun.com
> Strategic Market Development (781) 442-0531(Work)
> Sun Microsystems, Inc. (781) 993-1136(Fax)
>
> http://www.plurb.com/misc/xml/brandeis-xml-2001.html#bio
> http://www.plurb.com/misc/te/SangSchedule.html
> ---------------------------------------------