Dynamic component/outbound wire for CompositeContext.locateService needed ?

2007-01-24 Thread Rick
While investigating TUSCANY-862 with some local modification for other 
issues, I got as far as getting the message flowing (hello) to the 
reference however the Axis2TargetInvoker.createOperationClient only 
expects an OMElement and the message is still the Java String 
(world).  Talking briefly to Raymond he explained that the Databinding 
interceptor won't get inserted cause the locateService does have a real 
SCA component with an outbound wire behind it and thus won't add the 
Databind inceptor.  I'm kind of left wondering how we can support this 
case.  Should there be a dynamic (virtual) component created for this 
case and out bound wire produced ?


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Dynamic component/outbound wire for CompositeContext.locateService needed ?

2007-01-24 Thread Jim Marino


On Jan 24, 2007, at 1:13 PM, Rick wrote:

While investigating TUSCANY-862 with some local modification for  
other issues, I got as far as getting the message flowing (hello)  
to the reference however the  
Axis2TargetInvoker.createOperationClient only expects an OMElement  
and the message is still the Java String (world).  Talking  
briefly to Raymond he explained that the Databinding interceptor  
won't get inserted cause the locateService does have a real SCA  
component with an outbound wire behind it and thus won't add the  
Databind inceptor.  I'm kind of left wondering how we can support  
this case.  Should there be a dynamic (virtual) component created  
for this case and out bound wire produced ?


I don't think there needs to be a component - just an outbound wire  
from the proxy with the appropriate interceptor.


Jim


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]