Hi Simon, Yes, just using <binding.ws/> in the reference works.
But, if the components are defined in seperate composites, I get the following warnings (as I expected): WARNUNG: Component reference target not found, it might be a remote service: CrawlerComponent WARNUNG: Component reference target not found, it might be a remote service: SpecialCrawlerComponent Is this a current limitation? Bye, Daniel > Hi Daniel > > Disregarding the multiple bindings angle for a moment. For a > single remote binding, looking at you composite I think the > reference side should look like.... > > <reference name="crawlers" multiplicity="1..n" > target="CrawlerComponent SpecialCrawlerComponent"> > <binding.ws/> > </reference> > > And the service side should be as you have it, e.g. > > <service name="Crawler"> > <interface.java > interface="interfaces.Crawler"/> > <binding.ws uri=" > http://AFA-19393:8088/CrawlerComponent<http://afa-19393:8088/C > rawlerComponent>" > /> > </service> > > etc. > > Does that work? > > Simon >
