incubator-yoko-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Glynn, Eoghan" <eoghan.gl...@iona.com>
Subject RE: WS-Addressing support in Yoko
Date Fri, 20 Apr 2007 13:57:02 GMT

Grandeo, thanks Darren for the quick confirmation.

Cheers,
Eoghan

> -----Original Message-----
> From: Darren Middleman [mailto:dmiddleman@gmail.com] 
> Sent: 20 April 2007 14:52
> To: yoko-dev@incubator.apache.org
> Subject: Re: WS-Addressing support in Yoko
> 
> Hi Eoghan,
> 
> You are correct, Yoko is simply using the 
> EndpointReferenceType to provide support for CORBA object 
> references.  We do not encode any additional policy
> 
> information/properties as ServiceContext info or in the 
> generated CORBA object reference.
> 
> Cheers,
> Darren
> 
> On 4/20/07, Glynn, Eoghan <eoghan.glynn@iona.com> wrote:
> >
> >
> >
> > Folks,
> >
> > I'm curious about the extent of WS-Addressing support in Yoko. This 
> > relates to a scenario in CXF whereby a policy might be usefully 
> > asserted in the WSDL for one binding but not another. The canonical 
> > example I had in mind was the <wsam:Addressing> policy 
> being asserted 
> > for the SOAP binding but not the CORBA binding. The 
> assumption being 
> > that there's no standard way of encoding the WS-A message 
> addressing 
> > properties (wsa:To, wsa:ReplyTo, wsa:MessageID, 
> > wsa:isReferenceParamater etc.) as part of a CORBA payload, 
> so it would 
> > only make sense to aggregate these properties in the SOAP case.
> >
> > However I was interested to see that Yoko includes a 
> > bank_ws_addressing demo. A quick look at the code suggests that the 
> > extent of WS-A support is really just the usage of the 
> > EndpointReferenceType, and not the encoding of the WS-A 
> properties on 
> > the wire. I'd be happy to be corrected on this point though, for 
> > example if the WS-A properties were encoded by Yoko as as 
> an IOP::ServiceContext or some-such.
> >
> > Cheers,
> > Eoghan Glynn
> > [CXF committer]
> >
> >
> 

Mime
View raw message