[ https://issues.apache.org/jira/browse/TUSCANY-2256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gilbert Kwan updated TUSCANY-2256: ---------------------------------- Attachment: RequestWorkAsComposite.ppt Diagram to show the problem > Request scope service works as composite scope service > ------------------------------------------------------ > > Key: TUSCANY-2256 > URL: https://issues.apache.org/jira/browse/TUSCANY-2256 > Project: Tuscany > Issue Type: Bug > Components: Java SCA Core Runtime > Affects Versions: Java-SCA-Next > Reporter: Gilbert Kwan > Attachments: RequestWorkAsComposite.ppt > > > There are 3 components > - JComponent (composite scope) > - KComponent (stateless scope) > - LComponent (request scope) > When the composite runs, composite scope service JComponent kicks off a timer > by the @Init method. The timer triggers JComponent every second to invoke a > method that calls an operation on the reference to a stateless scope sevice > KComponent. KComponent calls a request scope service LComponent multiple > times. > We found that there was only one instance of LComponent be used and the state > was also preserved. Although it was declared as a request > scope service, it worked like as a composite scope service. (See the attached > powerpoint.) > The "SCA Java Annotations And APIs V1" specification line 292 to 293.says, > "... the lifetime of the request is implementation > dependent.". -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.