Re: question on writing a new JMS opSelector

2009-03-25 Thread Simon Laws
snip.. > >> What does "MyOperationProperty" refer to? Are you really saying it would >> be... >> >> > 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

Re: question on writing a new JMS opSelector

2009-03-25 Thread Scott Kurz
Simon, Thanks for responding.. replies below... On Wed, Mar 25, 2009 at 11:09 AM, Simon Laws 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 b

Re: question on writing a new JMS opSelector

2009-03-25 Thread Simon Laws
Hi Scott Comments in line. snip... > Realizing that we had needed to wait until operation selection took > place to run this logic, I was thinking about moving this to > TransportServiceInterceptor.invokeResponse().   I would assume it's > reasonable to assume that the app did not modify the orig

question on writing a new JMS opSelector

2009-03-25 Thread Scott Kurz
I was looking at adding an operationSelector to use any user-specified "user property" (not just 'scaOperationName') to hold the operation name. It seems the one oS we currently have, OperationSelectorJMSDefaultServiceInterceptor, has some callback destination stuff in it which should ideally be f