Hi, I think using DOSGI in combination with discovery is the best way to solve this.
Take a look at http://cxf.apache.org/dosgi-discovery-demo-page.html for an example. Using this, there is no need for the client to know where to reach the server. Hope this helps! On Tue, Feb 2, 2010 at 3:25 PM, Heiko Waldschmidt < [email protected]> wrote: > Hallo, > > I want to connect to a determined remote Service. But don't want to > determine the address of this services by hard-coding it. How can I do > this outside the bundle? > > I want to implement a GetWeather-Service. This Service is running on 10 > Server. Only one of this Server has the Data a Client needs - because > Server A has the Weather Data for London, Server B for Berlin, etc ... > one Client needs the Data for Berlin and one for London. I don't want to > make differences in code - i want to configure to which > GetWeather-Service a Client connects. > > In your examples how DOSGi works with DS I found the following > service-description: > <service-descriptions xmlns="http://www.osgi.org/xmlns/sd/v1.0.0";> > <service-description> > <provide interface="org.apache.cxf.dosgi.samples.ds.AdderService" > /> > <property name="osgi.remote.interfaces">*</property> > <property name="osgi.remote.configuration.type">pojo</property> > <property > name="osgi.remote.configuration.pojo.address">http://localhost:9090/adder > </property> > </service-description> > </service-descriptions> > > There is an address where I can connect to a service. This address is > hard-coded. What can I do that Client A' connects with Server A and > Client B' with Server B. Is there a way to configure this dynamicaly? > Can the service-description file be outside the bundle? > > Greetings, > Heiko Waldschmidt > > Fraunhofer Institut für Windenergie und Energiesystemtechnik IWES > > Heiko Waldschmidt > Bereich Anlagentechnik und > Netzintegration > > Fraunhofer IWES > Königstor 59 > D-34119 Kassel / Germany > Tel: +49(0)561-7294-230 > Fax: +49(0)561-7294-200 > Email: [email protected] > http://www.iset.uni-kassel.de ( http://www.iset.uni-kassel.de/ ) > http://www.iwes.fraunhofer.de > > > Fraunhofer IWES Advancing Energy Systems. > > Der Institutsteil Kassel des am 01.01.2009 gegründeten neuen Fraunhofer > IWES ist aus dem ehemaligen Institut für Solare > Energieversorgungstechnik - Verein an der Universität Kassel e.V. (ISET) > hervorgegangen. > > -- Met vriendelijke groet, Alexander Broekhuis
