Hi. I noticed ServiceMix is also an OSGi based SOA environment including Spring and web service stuff. And I have a question about this.
Currently, we are developing OSGi-based desktop application something like Eclipse (for biologists). We are thinking about some of server-side usecases, but main target is the desktop. We need to add web service client feature for it because remote access to public biological databases are usually done by standard web technologies (SOAP, etc.). So, in most cases, it works as a client application. In that case, is ServiceMix kernel a good choice for the basis of such application? Thanks. Kei 2009/2/10 Guillaume Nodet <gno...@gmail.com>: > You should try CXF instead of the RI. Apache CXF is a JAX-WS > compliant and OSGi ready. > You will find some examples in the ServiceMix 4 distribution. Here are > a few pointers to the examples sources: > https://svn.apache.org/repos/asf/servicemix/smx4/features/trunk/examples/ > ServiceMix 4 is built on top of Felix and Spring-DM and adds a few > features. If you don't want the JBI stuff, you can start with > ServiceMix Kernel (http://servicemix.apache.org/kernel/index.html) and > deploy CXF bundles onto it instead of using the full ServiceMix 4 > distribution. > > On Tue, Feb 10, 2009 at 20:12, Keiichiro Ono <k...@ucsd.edu> wrote: >> Hi. >> >> I'm trying to use JAX-WS on OSGi environment (Felix and Spring-DM). >> Basically, I'm trying to write a web service client working on Spring >> DM. As far as I know, there is no OSGi-bundle version of JAX-WS >> implementations although API bundle is available from SpringSource >> repository. In this case, I think there are 3 options: >> >> 1. Wrap JAX-WS reference implementation by PAX-Construct. >> 2. Use Apache Geronimo implementation of JAX-WS. >> 3. Use gigantic OSGi bundle from GlassFish Enterprise Server v3 Prelude >> project. >> >> I tried 1, but it did not work because somehow. The stack trace >> indicates that the Sun's implementation is calling wrong method which >> does not exist. >> >> Caused by: java.lang.UnsupportedOperationException: Method not implemented. >> at java.net.URLStreamHandler.openConnection(URLStreamHandler.java:80) >> at java.net.URL.openConnection(URL.java:992) >> at >> com.sun.xml.ws.api.EndpointAddress.openConnection(EndpointAddress.java:211) >> at >> com.sun.xml.ws.transport.http.client.HttpClientTransport.createHttpConnection(HttpClientTransport.java:239) >> at >> com.sun.xml.ws.transport.http.client.HttpClientTransport.getOutput(HttpClientTransport.java:116) >> ... 38 more >> >> And so far, I could not solve this problem. So my question is, which >> option do you recommend if I need to use JAX-WS on OSGi? >> >> Thanks. >> Kei >> >> -- >> Keiichiro Ono k...@ucsd.edu >> >> Cytoscape Core Developer Team: http://www.cytoscape.org/ >> UCSD Bioengineering Ideker Lab: http://chianti.ucsd.edu/idekerlab/ >> >> _______________________________________________ >> general mailing list >> general@lists.ops4j.org >> http://lists.ops4j.org/mailman/listinfo/general >> > > > > -- > Cheers, > Guillaume Nodet > ------------------------ > Blog: http://gnodet.blogspot.com/ > ------------------------ > Open Source SOA > http://fusesource.com > > _______________________________________________ > general mailing list > general@lists.ops4j.org > http://lists.ops4j.org/mailman/listinfo/general > -- Keiichiro Ono k...@ucsd.edu Cytoscape Core Developer Team: http://www.cytoscape.org/ UCSD Bioengineering Ideker Lab: http://chianti.ucsd.edu/idekerlab/ _______________________________________________ general mailing list general@lists.ops4j.org http://lists.ops4j.org/mailman/listinfo/general
