Re: wsa:Action and WSDL
From: Lucien (*lucien*_at_MicrosoftAccount.com)
Date: 08/06/04
- Next message: Lucien: "Re: Calling an ASMX web service (with WSE 2.0) using SoapClient proxy"
- Previous message: casey chesnut: "ANN: article for calling WSE 2.0 from Compact Framework"
- In reply to: Fraser: "Re: wsa:Action and WSDL"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 6 Aug 2004 10:38:24 -0700
To clarify only the WseWsdl2 tool doesn't support at this point the
wsa:Action attribute and uses the soapAction instead. It probably will be in
future releases.
The WSDL generation is less trivial. We'd probably need a flag to indicate
you want wsa:Action binding since other products may choke on this (if they
don't support the binding).
"Fraser" <Fraser@discussions.microsoft.com> wrote in message
news:63E7A497-D7EC-4E8B-A587-B391B20C1F4B@microsoft.com...
> Lucien,
>
> thanks for sticking with this one. I am surprised that WSE2 can't auto-gen
a proxy from a WSDL and maintain the wsa:Action header binding, so thanks
for that 'heads up'.
>
> You are correct in the sense that I want to be able to associate a
different wsa:Action header binding with each of the possible response
outcomes for a single operation, but I was hoping I might be able to declare
them statically in the WSDL, each one associated to its corresponding
response message schema type.
>
> I agree that I can set these programmatically, and at this stage it might
be the way to go.
>
> Fraser.
>
> "Lucien" wrote:
>
> > Do I understand correctly that you want a non-static response action for
a
> > certain request action? I don't find anything in WS-Addressing that
> > illustrates that scenario and how this would be specified in WSDL (and
> > probably most app won't understand it anyway). In WSE you can set the
action
> > header on the response yourself so you could implement this scenario but
the
> > WSDL / proxy generation will not support this (for that matter
WS-Addressing
> > WSDL binding is not supported/understood in WSE 2.0 SP1).
> >
> > You may want to ask this question also in the WSDL newsgroup but I think
> > it's better to put that data in a different header (but don't take my
word
> > for it).
> >
> >
> > "Fraser" <Fraser@discussions.microsoft.com> wrote in message
> > news:A4F25933-C5A2-4B55-98AC-CF35AEB1B942@microsoft.com...
> > > Hi Lucien,
> > >
> > > I don't think I understand what you have said here :-
> > >
> > > - the wsa:Action header *is* meta data and *is* a header.
> > > - the wsa:Action header *is* used for the response in the
request/reply
> > pattern and signals the semantics for the response message via an
explicit
> > (or implicit) URI.
> > > - the response payload *may* (typically will) also indicate its
semantics
> > (often via the namespace), but it is often useful for routing info such
as
> > this to be accessible outside of the payload (sometimes our payloads are
> > encrypted).
> > >
> > > I may be mis-understanding you in some way (or perhaps WS-Addressing).
> > Please put me straight (on either/both :-) ?
> > >
> > > All I want to be able to do is ... where a [WSDL] operation has more
than
> > one possible response message, declare an explict wsa:Action header
value
> > for each.
> > >
> > > Fraser
> > >
> > >
> > > "Lucien" wrote:
> > >
> > > > Imo you should not use wsa:Action header in response to put metadata
on
> > the
> > > > message. Use headers instead (or in the soap:body depending on
> > scenario).
> > > >
> > > > "Fraser" <Fraser@discussions.microsoft.com> wrote in message
> > > > news:BEC9C0B9-9269-4AC6-AB76-9C02399F1E1E@microsoft.com...
> > > > > The WS-Addressing specs talks about an explict and implicit
binding
> > for
> > > > the wsa:Action header for input and output messages.
> > > > >
> > > > > Specifically in the case of an output I have a situation where
there
> > is
> > > > more than one possible response message for a given request and I
want
> > to be
> > > > able to indicate which response has been sent in the wsa:Action
header.
> > I
> > > > can see that the type associated with a output message [payload] can
be
> > > > described as a xsd:Choice, but is it possible to assign different
> > explicit
> > > > wsa:Action header values to each ?
> > > > >
> > > > > Cheers
> > > > >
> > > > > Fraser
> > > >
> > > >
> > > >
> >
> >
> >
- Next message: Lucien: "Re: Calling an ASMX web service (with WSE 2.0) using SoapClient proxy"
- Previous message: casey chesnut: "ANN: article for calling WSE 2.0 from Compact Framework"
- In reply to: Fraser: "Re: wsa:Action and WSDL"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
