dev@jax-ws.java.net

Re: Getting to WSDLBoundOperation from a message

From: Joseph Fialli <Joseph.Fialli_at_Sun.COM>
Date: Fri, 10 Feb 2006 10:12:02 -0500

Kohsuke Kawaguchi wrote:
>
> I think a lot of pipes want to get to a WSDLBoundOperation for the
> current message, so I think it's worth doing efficiently.
>
> Today the way it's done is most likely for each pipe to create a QName
> that represents the payload name, then do a map look up to get to
> WSDLBoundOperation.
>
> I think we should provide a method on Message that returns
> WSDLBoundOperation like this:
>
> class Message {
> WSDLBoundOperation getOperation(WSDLPort port);
> }
As long as PolicyMap.getOperationScope(Object) takes an instance
of WSDLBoundOperation, this method would be useful for WS-TX pipes.

-Joe
>
> Since the payload is read-only, we can cache the computed
> WSDLBoundOperation, avoiding multiple lookup.
>
> To do this we also need payload->op look up at WSDLBoundPortType. Arun
> told me that Vivek is planning to do this.
>
> Would this make sense? Or can someone think of a better way to do this?
>
> The only thing that I don't like about this is that it's likely many
> pipes will still have to look up their own map from WSDLBoundOperation
> to their own data structure.
>
>