I got similar issue as dpwr's, use Glassfish 3.1.1, and try the solution to
switch classloader as sahoo told, but not working
finally I just made a test to get ride of metro bundle with glassfish to use
jax-ws with jdk, it works for now:
1.start glassfish and add -Dcom.sun.xml.ws.monitoring.endpoint=false on
Configurations -> server-config ->add jvm option. refer
to(
http://stackoverflow.com/questions/4983731/how-do-i-disable-metro-on-glassfish)
2.stop glassfish
3,move these files to a backup directory (since I want to recover it if
anything wrong):
glassfish\modules\endoserd\
jaxb-api-osgi.jar
webservices-api-osgi.jar
glassfish\modules\
jaxb-osgi.jar
jaxr-api-osgi.jar
jaxrpc-api-osgi.jar
jsr109-impl.jar
metro-glue.jar
soap-tcp.jar
stax2-api.jar
webservices.security.jar
webservices-connector.jar
webservices-extra-jdk-packages.jar
webservices-osgi.jar
woodstox-core-asl.jar
4.add these to glassfish\osgi\felix\conf\config.properties , behind the
content that list under "endorsed-standard-packages="
don't forget to add ", \" to the last line you append to and add bellows in
another line, and start with a blank in each line.
com.sun.xml.internal.ws, \
com.sun.xml.internal.ws.addressing, \
com.sun.xml.internal.ws.addressing.model, \
com.sun.xml.internal.ws.addressing.v200408, \
com.sun.xml.internal.ws.api, \
com.sun.xml.internal.ws.api.addressing, \
com.sun.xml.internal.ws.api.client, \
com.sun.xml.internal.ws.api.fastinfoset, \
com.sun.xml.internal.ws.api.handler, \
com.sun.xml.internal.ws.api.message, \
com.sun.xml.internal.ws.api.message.stream, \
com.sun.xml.internal.ws.api.model, \
com.sun.xml.internal.ws.api.model.soap, \
com.sun.xml.internal.ws.api.model.wsdl, \
com.sun.xml.internal.ws.api.pipe, \
com.sun.xml.internal.ws.api.pipe.help, \
com.sun.xml.internal.ws.api.server, \
com.sun.xml.internal.ws.api.streaming, \
com.sun.xml.internal.ws.api.wsdl, \
com.sun.xml.internal.ws.api.wsdl.parser, \
com.sun.xml.internal.ws.api.wsdl.writer, \
com.sun.xml.internal.ws.binding, \
com.sun.xml.internal.ws.client, \
com.sun.xml.internal.ws.client.dispatch, \
com.sun.xml.internal.ws.client.sei, \
com.sun.xml.internal.ws.developer, \
com.sun.xml.internal.ws.encoding, \
com.sun.xml.internal.ws.encoding.fastinfoset, \
com.sun.xml.internal.ws.encoding.soap, \
com.sun.xml.internal.ws.encoding.soap.streaming, \
com.sun.xml.internal.ws.encoding.xml, \
com.sun.xml.internal.ws.fault, \
com.sun.xml.internal.ws.handler, \
com.sun.xml.internal.ws.message, \
com.sun.xml.internal.ws.message.jaxb, \
com.sun.xml.internal.ws.message.saaj, \
com.sun.xml.internal.ws.message.source, \
com.sun.xml.internal.ws.message.stream, \
com.sun.xml.internal.ws.model, \
com.sun.xml.internal.ws.model.soap, \
com.sun.xml.internal.ws.model.wsdl, \
com.sun.xml.internal.ws.org.objectweb.asm, \
com.sun.xml.internal.ws.protocol, \
com.sun.xml.internal.ws.protocol.soap, \
com.sun.xml.internal.ws.protocol.xml, \
com.sun.xml.internal.ws.resources, \
com.sun.xml.internal.ws.server, \
com.sun.xml.internal.ws.server.provider, \
com.sun.xml.internal.ws.server.sei, \
com.sun.xml.internal.ws.spi, \
com.sun.xml.internal.ws.streaming, \
com.sun.xml.internal.ws.transport, \
com.sun.xml.internal.ws.transport.http, \
com.sun.xml.internal.ws.transport.http.client, \
com.sun.xml.internal.ws.transport.http.server, \
com.sun.xml.internal.ws.util, \
com.sun.xml.internal.ws.util.exception, \
com.sun.xml.internal.ws.util.localization, \
com.sun.xml.internal.ws.util.pipe, \
com.sun.xml.internal.ws.util.xml, \
com.sun.xml.internal.ws.wsdl, \
com.sun.xml.internal.ws.wsdl.parser, \
com.sun.xml.internal.ws.wsdl.writer, \
com.sun.xml.internal.ws.wsdl.writer.document, \
com.sun.xml.internal.ws.wsdl.writer.document.http, \
com.sun.xml.internal.ws.wsdl.writer.document.soap, \
com.sun.xml.internal.ws.wsdl.writer.document.soap12, \
com.sun.xml.internal.ws.wsdl.writer.document.xsd
5. restart glassfish to see if anythign wrong (which works on my case)
6,deploy you bundle to test.(maybe you need use DynamicImport-Package if you
do not import som package explicitly)
since I do not published any webservice on glassfish(just have some osgi
bundle work as webservice client), and really do not have time to do further
test with that, so this may not really help.
I just make this test, and did not use it in production entironment yet.
Glassfish is really good and advanced, hope this issue could be solved and we
can use the metro inside it.
--
[Message sent by forum member 'leozhu']
View Post: http://forums.java.net/node/818465