Ok, so each time an instance of the SCA component that uses
MyServiceImpl as its implementation is created a new instance of
MyExternalObject will also be created. As it stands this component
implementation has stateless scope so this will happen when each
message arrives, I.e. each call to getMy
Yes.
Regards
Raman
-Original Message-
From: Simon Laws [mailto:simonsl...@googlemail.com]
Sent: Wednesday, 24 February 2010 3:13 PM
To: user@tuscany.apache.org
Subject: Re: singleton references in SCA service
So you have a component implementation like...
@Service(MyService.class
So you have a component implementation like...
@Service(MyService.class)
class MyServiceImpl implements MyService {
private MyExternalObject myExternalObject;
public MyServiceImpl(){
myExternalOject = new MyExternalObject();
}
public void myMethod (){
...
}
and
suggestions with this approach.
Regards
Raman
-Original Message-
From: Malisetti, Ramanjaneyulu
Sent: Tuesday, 23 February 2010 7:58 PM
To: user@tuscany.apache.org
Subject: RE: singleton references in SCA service
I tried @Scope composite. Nope.
Regards
Raman
-Original Message
I tried @Scope composite. Nope.
Regards
Raman
-Original Message-
From: Hatfield, Dan [mailto:dan.hatfi...@hp.com]
Sent: Tuesday, 23 February 2010 7:42 PM
To: user@tuscany.apache.org
Subject: RE: singleton references in SCA service
Refer to the @Scope SCA annotation
Refer to the @Scope SCA annotation.
From: Malisetti, Ramanjaneyulu [ramanjaneyulu.malise...@ca.com]
Sent: Tuesday, February 23, 2010 9:05 AM
To: user@tuscany.apache.org
Subject: singleton references in SCA service
We have SCA based service implementation class
