Resending as the previous message triggered the spam alert and was rejected
From: Raymond Feng
Sent: Tuesday, July 22, 2008 10:12 AM
To: [email protected]
Subject: Re: Questions about feed-aggregator sample
Hi,
1) This is a service promotion that makes the AtomAggregator component
service public and further configure the binding to be ATOM (i.e., expose it
as an ATOM service). You can also inline the binidng.atom configuration
under the <component> element. There are differences between the two
configurations. For the promotion, the composite can be used to implement
another SCA component (implementation.composite for recursive
composition)and the promoted service becomes a service at the higher level
component. For the inline case, you just configure the binding.
2) All operations on the AlertsService interface can be called.
3) The @Remotable applies to the interface instead of the component impl
class. Please note AlertsService interface has the @Remotable.
Thanks,
Raymond
From: Willis C White
Sent: Tuesday, July 22, 2008 8:41 AM
To: [email protected]
Subject: Questions about feed-aggregator sample
I am trying to understand these lines in the FeedAggregator.composite file
<service name="rssSample" promote="RssAggregator">
<tuscany:binding.atom
uri="http://localhost:8083/rssAggregator"/>
</service>
<service name="atomSample" promote="AtomAggregator">
<tuscany:binding.atom
uri="http://localhost:8083/atomAggregator"/>
</service>
These services are not declared in the component stanzas and I don't see an
"@Remotable" in the AggregatorImpl.java.
1.How do these lines get wired to the java file?
2.What method to they call?
3.How is it that they talk to code out side of the domain without a
"@Remotable" annotation.
