Gary Pinkham [
http://community.jboss.org/people/garyp] created the discussion
"Re: failed to create jaxb context"
To view the discussion, visit:
http://community.jboss.org/message/577397#577397
--------------------------------------------------------------
ok so i discovered a couple of facts... 1. when the unit test worked I had the Service
locator using a local version of the WSDL (c:\foo\bar\myservice.wsdl)... I had changed
this to the wsdl from the live running instance when I waned to deploy the client as a
library jar in the ESB Action.. This WSDL produced on the fly by JBossWS came out
different than the original that the Service and Clients we based on (top down service and
client generation).. Needless to say the client didn't match this (I kept getting a
service not found as the namespace and service names didn't match)..
I tried to change the Service's annotation to include a WSDL location for the original
WSDL file.. The service then failed to start (giving the same error about the namespace
and service names not matching)..
So at this point I'm not sure what exactly I did wrong.. I used JBossWS to generate
the Service from the WSDL file.. I then used JBossWS to produce the client from the same
exact WSDL file.. Having the client point to the file on disk seemed to work ok.. But
this only worked with absolute path.. not sure how to get it to work with relative paths
within the JAR file.. Suggestions?
thanks!
Gary
--------------------------------------------------------------
Reply to this message by going to Community
[
http://community.jboss.org/message/577397#577397]
Start a new discussion in JBoss Web Services Development at Community
[
http://community.jboss.org/choose-container!input.jspa?contentType=1&...]