dev@jax-ws.java.net

Re: Propagation of FI content negotiation

From: Jiandong Guo <Jiandong.Guo_at_Sun.COM>
Date: Tue, 25 Jul 2006 07:55:19 -0700

I believe RM also create a new Packet for RM protocol messages. So this
should also be a problem for them.

Thanks!

Jiandong

Paul Sandoz wrote:

> Hi,
>
> As i understand it the secure conversation pipe creates a new Packet
> for its pipe line from the Packet of the client request. Are there any
> other cases where this occurs?
>
> In the general case, should we propagate the content negotiation
> property? i.e.
>
> private Packet(Packet that) {
> that.copySatelliteInto(this);
> this.invocationProperties = that.invocationProperties;
> this.handlerScopePropertyNames = that.handlerScopePropertyNames;
> this.contentNegotiation = that.contentNegotiation;
> // copy other properties that need to be copied. is there any?
> }
>
> So in the case of secure conversation if the client enabled Fast
> Infoset then that would also get propagated to the secure
> conversation client.
>
> Given that the 'pessimistic' property will only result in FI being
> enabled iff the service is FI-enabled the propagation of this property
> will not affect the interoperablity with non-FI-enabled secure
> conversation services.
>
> Paul.
>