snip.... > > Yes, I was thinking along the following lines: Suppose you have a > component which must be COMPOSITE scope for reasons of its own. As > it happens, when you developed it this component would be accessed > only by one client at a time, so you never bothered to make it threadsafe. > Now the deployment context changes and suddenly the component gets hit > with concurrent requests. Wouldn't it be nice if there were a way > to declare this component as "non-concurrent" (or whatever) > in its configuration file (the composite.xml) instead of having > to change the code to make it threadsafe? The Tuscany runtime > would so be made responsible for blocking concurrent access. >
We don't have that in the runtime at the moment. It's not a feature described by the SCA specifications. If it were required it could potentially be support using a policy implementation. I.e. a handler on a service wire able to synchronize incoming messages ensuring that only one is processed at a time through a particular component. Simon -- Apache Tuscany committer: tuscany.apache.org Co-author of a book about Tuscany and SCA: tuscanyinaction.com
