[ https://issues.apache.org/jira/browse/TUSCANY-1286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Sebastien Delfino updated TUSCANY-1286: -------------------------------------------- Fix Version/s: (was: Java-SCA-1.0) Java-SCA-Next Moving to SCA-Next as these JIRAs are not likely to be fixed by 1.0. > InterfaceContract is not correctly set for a component service if the > component is implemented by a composite > -------------------------------------------------------------------------------------------------------------- > > Key: TUSCANY-1286 > URL: https://issues.apache.org/jira/browse/TUSCANY-1286 > Project: Tuscany > Issue Type: Bug > Components: Java SCA Assembly Model > Affects Versions: Java-SCA-Next > Reporter: Raymond Feng > Assignee: Jean-Sebastien Delfino > Fix For: Java-SCA-Next > > > Hi, > I ran into an issue with the following assembly: > ComponentA is implemented by Composite1. Composite1 defines a > CompositeService Service1 which promotes ComponentB.Service1. Only > Component.Service1 has a java interface defined. > From the debugger, I observed that the CompositeUtil resolves the > InterfaceContract in the sequence below: > 1) > ComponentA.Service1.setInterfaceContract(Composite1.Service1.getInterfaceContract()); > > // At this moment, it's null > 2) > Composite1.Service1.setInterfaceContract(ComponentB.Service1.getInterfaceContract()); > > // This is good for Composite1.Service1 but it doesn't pop up to > ComponentA.Service1 > As a result, ComponentA.Service1 still has a null InterfaceContract. > Thanks, > Raymond -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]