Simon,

Thanks for responding.. replies below...

On Wed, Mar 25, 2009 at 11:09 AM, Simon Laws <[email protected]> wrote:

> This logic seems to be setting callback destination information into
> the forward message. So that the invoker code can handle callbacks
> properly. The URI from this callback reference will be copied back
> into the callback jms binding when the callback wire is cloned. If
> it's deferred to the transport service interceptor response processing
> I think that will be too late. So a new interceptor would seem to be
> the way to go.

OK, thanks.

> What does "MyOperationProperty" refer to? Are you really saying it would be...
>
> <tuscany:operationSelector.jmsUser propertyName="MyOperationProperty"
> operationName="MyChosenOperation"/>

I'm saying that my operation selector will expect to find the
operation name as the value of the user property identified by
@propertyName, (a lot like the JMS default oS will key off of JMS user
property 'scaOperationName').


>> As a separate but related issue, it appears from looking at the OASIS
>> spec that we interpreted the OSOA attr:
>> /binding.jms/operationProperties/@nativeOperation  incorrectly.  We
>> currently make use of this on a request from the reference side in
>> HeaderReferenceInterceptor.   When looking at the OASIS spec, where
>> @nativeOperation has been replaced by @selectedOperation, it's clear
>> that this is supposed to be a service side thing, which provides
>> another layer of metadata-based override to whatever oS has been
>> configured by the runtime.   (The only use on the reference side seems
>> to be wrt receiving callbacks).
>>
>> I'm thinking this should also be factored out so that every specific
>> oS implementation does not have to do this.
>
> Do you mean disable the reference side use of this for forward
> messages? Then we would need to instigate some service side processing
> to map selected operations to native operations?

Yes and yes.. that's how I read the OASIS spec, and I'm further
assuming that this happens on top (after) any potential specific JMS
oS, default or otherwise.

Scott

Reply via email to