I find out on
http://aleung.github.io/blog/2010/03/11/Study-of-the-issue-that-CXF-can-t-run-on-GlassFish/
: Because in GlassFish the Metro library is in system classpath, so its
META-INF/services/javax.xml.ws.spi.Provider will be loaded precede over
CXF’s. That’s why Metro will always be used as JAX-WS implement no
matter CXF exists or not.
I also tried the steps explained in
http://cxf.apache.org/docs/application-server-specific-configuration-guide.html#ApplicationServerSpecificConfigurationGuide-Glassfish
for specific configuration for Glassfish classloadet, but all these were
unsuccessful, I still get the same exception:
org.apache.cxf.service.factory.ServiceConstructionException: Failed to
create service.
Darko
On 16.9.2013. 12:59, Freeman Fang wrote:
Hi,
I believe this is caused by other stax impl was loaded first, check if there's
any other stax impl in container class loader.
－－－－－－－－－－－－－
Freeman(Yue) Fang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://fusesource.com | http://www.redhat.com/
Twitter: freemanfang
Blog: http://freemanfang.blogspot.com
http://blog.sina.com.cn/u/1473905042
weibo: @Freeman小屋
