Hi Doug. Thank you for the quick reply. I'll try the bundles from metro. By the way, are there any specific reason to use 1.3.1 instead of Metro version 1.4 (latest)?
Thanks. Kei 2009/2/10 Douglas C. Grove <grov...@warpfactor.com>: > Hi Kei, > > Actually, there is ... I have done this and can provide the very > painful details.... Fortunately, once you know how, it is pretty easy. > > Central to successfully getting JAX-WS to work in an OSGi environment > are the current JAX jars. The out-of-the-box Sun JDK/JRE distribution > is not adequate. The distribution implementation makes classloader > assumptions that are not valid in an OSGi environment. > > Furthermore, the 1.3.1 release is actually an OSGi bundle, not simply a > set of jar files. > > Poke around: > > https://metro.dev.java.net/1.3.1/ > > for more information. > > So, to solve your problem.... I use maven for my builds. For JAX-WS > clients to work, I add: > > <dependency> > <groupId>com.sun.xml.ws</groupId> > <artifactId>webservices-rt</artifactId> > <version>1.3.1</version> > scope>runtime</scope> > </dependency> > <dependency> > <groupId>javax.xml</groupId> > <artifactId>webservices-api</artifactId> > <version>1.3.1</version> > <scope>compile</scope> > </dependency> > > > Both webservices-rt and webservices-api can actually be deployed as > bundles. > > Alternatively, you can use the Java Endorsed mechanism to over ride the > shipped JAX code. > > http://java.sun.com/javase/6/docs/technotes/guides/standards/ > > i.e.: > > ls -las jdk/jre/lib/endorsed/ > webservices-api-1.3.1.jar > webservices-rt-1.3.1.jar > > You'll probably want to update the jars for your server side as well as > for your OSGi runtime. > > Hope that helps, > > Doug > > > On Tue, 2009-02-10 at 11:12 -0800, Keiichiro Ono 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 >> > > > _______________________________________________ > 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
