Re: new issue: drop {direction} property from message reference components

I don't think we should close this issue until we have addressed how
the properties of the message reference component are filled in
automatically (when omitted in the syntax) using information from
the pattern.

For instance, suppose I run into a pattern I don't know. Then, per your
proposal, I'd build a component model containing some message reference
components whose direction is unknown, thus losing some of the
information present in the WSDL document.


Sanjiva Weerawarana wrote:
> The current draft component model has a {direction} property for
> message reference components [1]. I propose that we drop this 
> property as in reality message references do not have such a 
> property: the direction the message flows in is *completely*
> defined by the pattern of which this message is a part of.
> I had edited this out earlier but put it back in at the chair's
> suggestion that this is a substantial change and hence required
> WG approval. So, please approve removing this redundancy.
> Note that this DOES NOT affect the syntax at all. It will change
> the wording on <input> etc. to say that the direction of the
> message (from the pattern) must be consistent with the local 
> name of the EII ("input" etc.).
> Sanjiva.
> [1]

Received on Monday, 29 September 2003 19:14:28 UTC