I think that I recognize the comment as mine, and I certainly spent many happy hours debugging when I originally wrote it. However, someone else must have taken it back out. The problem with the null could have been there before, during, or after. How about a JIRA and we'll fix it?
On Mon, Sep 29, 2008 at 3:31 PM, Brendan Collins <[EMAIL PROTECTED]>wrote: > Hi, > > In moving from cxf 2.1.0 to 2.1.1 (or 2.1.2) I am encountering the > following problem: > > org.apache.cxf.wsdl.EndpointReferenceUtils.resolveResource() fails to > resolve schema imports because systemId is null when trying to resolve the > URI. > > > Interestingly the comment at the top of EndpointReferenceUtils reads as > follows: > > /** > * We want to load the schemas, including references to external > schemas, into a SchemaFactory > * to validate. There seem to be bugs in resolving inter-schema > references in Xerces, so even when we are > * handing the factory all the schemas, interrelated with <import> > elements, we need > * to also hand over extra copies (!) as character images when > requested. > * > * To do this, we use the DOM representation kept in the SchemaInfo. > This has the bonus > * of benefiting from the use of the catalog resolver in there, which is > missing from > * the code in here. > */ > > It looks like the code that this comment refers to was removed in 2.1.1, > and that code does in fact resolve my schema's correctly. > > Does anyone have any insight as to how I might fix this....I have looked at > my schema's trying to find issues with imports and have not found any > issues. Any suggestions? > > Thanks, > Brendan > > > > > > > > >
