On Wed, Aug 24, 2011 at 10:51 AM, Mike Edwards <[email protected]> wrote: > On 23/08/2011 23:23, Simon Nash wrote: >> >> This sounds like the right approach. One small point is that the >> description >> talks about redeclaring fields and methods in the subclass. This is >> possible >> with methods, but it doesn't work for fields as this results in a separate >> field >> with the same name in the subclass which hides the superclass field. To >> expose >> a superclass field as a property in the subclass, the subclass would need >> to >> declare a subclass setter method that assigns to the superclass field. >> >> Simon > > Yes, agreed. > > This all makes subclassing more work, of course, but I see no alternative if > the subclass is going to be in control. > > > Yours, Mike. > > >
Thanks for doing this Mike. Just to be clear I believe the words "If there is no @Service annotation, then the implementation offers no services. " should be read in conjunction with the title of Case1. I.e it would be interpreted as "If there is no @Service annotation, but other other annotations are present, then the implementation offers no services. " Shall we put these words here [1]? Not much there at the moment but seems to be the logical place. [1] http://tuscany.apache.org/documentation-2x/sca-java-implementationjava.html Regards Simon -- Apache Tuscany committer: tuscany.apache.org Co-author of a book about Tuscany and SCA: tuscanyinaction.com
