On Fri, Oct 1, 2010 at 4:49 PM, Raymond Feng <enjoyj...@gmail.com> wrote: > That sounds right. > > Raymond Feng > Sent from my iPhone > > On Oct 1, 2010, at 7:33 AM, Yang Lei <yl.yangle...@gmail.com> wrote: > >> I have my own webservices binding implementation in my OASIS hosting >> environment. I noticed when reference target is defined, service and >> reference side will share the share InterfaceContract instance. My service >> side and reference side are using (forced to use) different databinding. >> This object sharing cased me trouble running some of the OASIS spec >> compliance test as the databinding on the service side messed up, as >> reference side will be configured later than service side. >> >> I fixed the issue by making my reference side of binding clone the >> InterfaceContract before reset the databinding. However I would like to >> understand if it is correct behavior to share the same interfaceContact >> instance between service side and reference side... >> >> Appreciate thoughts and comments. I encountered the issue on JCA_11003 and a >> couple of other test cases under JCA and POJO. >> -- >> Thanks. Yang. >
Agreed. In OASIS, for references with targets, we copy the binding model from the service and I expect this is where the same interface contract gets pulled across. I'll check but we need the fix in Tuscany if you're happy to create a JIRA/patch? Simon -- Apache Tuscany committer: tuscany.apache.org Co-author of a book about Tuscany and SCA: tuscanyinaction.com
