no, including the xmnls Attribute in the binding definitio does not change the behavior. BTW, the tuscany-namespace has already been declared in the composite-element. -- Sebastian
-----Original Message----- From: Simon Nash [mailto:n...@apache.org] Sent: Monday, November 08, 2010 11:56 AM To: user@tuscany.apache.org Subject: Re: Meaning of ContributionWriteException? Millies, Sebastian wrote: > yes, it does: > > <sca:service name="StaticDataFactory"> > <sca:interface.java > interface="com.softwareag.ps.platform.sdohelper.StaticDataFactory"/> > <sca:binding.sca/> > <tuscany:binding.rmi host="localhost" port="8785" > serviceName="MRManagementStaticDataFactoryRMI"/> > </sca:service> > > and the exception disappears when I remove the RMI-Binding and stick to > binding.sca. > I do not understand why that should be so. Is it a limitation or bug in > Tuscany 1.6? > > Also, why should this marshalling error surface as a > ContributionWriteException > in my test case? > I suspect that the problem is caused by the XML namespace corresponding to the "tuscany" prefix not being available when the service definition is serialized. Please can you confirm this by changing the service definition to the following: <sca:service name="StaticDataFactory"> <sca:interface.java interface="com.softwareag.ps.platform.sdohelper.StaticDataFactory"/> <sca:binding.sca/> <tuscany:binding.rmi xmlns:tuscany="http://tuscany.apache.org/xmlns/sca/1.0"; host="localhost" port="8785" serviceName="MRManagementStaticDataFactoryRMI"/> </sca:service> Simon > -- Sebastian > > > -----Original Message----- > From: Simon Nash [mailto:n...@apache.org] > Sent: Friday, November 05, 2010 7:48 PM > To: user@tuscany.apache.org > Subject: Re: Meaning of ContributionWriteException? > > Millies, Sebastian wrote: >> Hello there, >> >> I am not using policies at the moment. >> I am on Tuscany 1.6. >> >> Here are two stack traces. Thanks for looking at it. I won't be able to >> supply more information >> at the moment, because I won't be in the office. If I can't solve the >> problem, I'll try to reduce >> it to something small. >> >> The ContributionWriteException only shows up in my Eclipse console when I run >> the test. The second stack trace seems to be the underlying cause, showing >> RMI marshalling problems. >> > There's an important clue in the second stack trace. The problem occurs when > trying to marshal a CallableReference using RMI. Does this callable reference > contain a Tuscany-specific binding? > > Simon > >> -- Sebastian >>
