Hi Darren,
Yes, i also noticed this issue, actually we do include the ws-addr.xsd
in your common-xsd.jar,
and i think we should use the we had in your jars instead of access the
xsd from the remote site.
Some site maybe block your access from the program (not from the
browser) or it might block the ip from some countries. so remote access
is really not stable.
I think we should log an issue and fix it asap.
James
Darren Middleman wrote:
Hi,
I have a question about some issues we are seeing in Yoko regarding the
resolving of remote schemas via CXF.
To implement CORBA object reference support, we are mapping these to
EndpointReferenceTypes on the CXF side of things. This requires us to
import the addressing schema, which we have been doing as follows:
<xs:import namespace="http://www.w3.org/2005/08/addressing";
schemaLocation="http://www.w3.org/2005/08/addressing/ws-addr.xsd";>
Occasionally (though more so recently), we are seeing issues when running
CXF WSDLtoJava on such a schema where we receive a WSDLException which
indicates that it was unable to resolve the addressing schema. For example,
Caused by: javax.wsdl.WSDLException: WSDLException (at
/wsdl:definitions/wsdl:types/xs:schema): faultCode=OTHER_ERROR: Unable to
locate with a locator the schema referenced at
'http://www.w3.org/2005/08/addressing/ws-addr.xsd' relative to document base
'file:/x1/continuum/working-directory/214/src/test/resources/wsdl/NestedObjRef.wsdl'
Note that this doesn't happen all the time, it can fail once and then when
a build is re-tried, it will succeed. Also, when the build is reporting
that it can not resolve the remote schema (consitently), if I try using
the addressing URL in a browser, I am able to resolve the schema in the
browser.
Does anyone have any thoughts on why this is happening with remote URLs
and what the best way to work around this is, other than having a local
copy of the schema and using it in the schemaLocation?
I also noticed that the CXF demo which uses EPRs uses the schema location
'/schemas/wsdl/ws-addr.xsd', which I assume comes from the common-schemas
JAR, but I'd like to stay away doing things this way in Yoko.
Thanks,
Darren
