-
Notifications
You must be signed in to change notification settings - Fork 93
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Validation needs additional <uri> catalog entry #217
Comments
@ralfhandl I have tried to debug the xml-resolver project but to be honnest with you, I'm a little lost -( I have tried to use your XML catalog with Eclipse WTP, but only completion is working, the validation doesn't work. It should be really cool if somebody could help us to know if catalog is valid or not. |
@angelozerr Strange. I'm also using Eclipse Photon with the editor from
The file <uri name="http://docs.oasis-open.org/odata/ns/edm" uri="platform:/resource/OData-TC/odata-csdl-schemas/schemas/edm.xsd"/>
<uri name="http://docs.oasis-open.org/odata/ns/edmx" uri="platform:/resource/OData-TC/odata-csdl-schemas/schemas/edmx.xsd"/> Validation and code completion both work fine with this catalog. |
@ralfhandl once build will be finished, please retry it. |
@angelozerr I assume you'll add some tests ;-) |
@angelozerr works fine with build #506, thanks! My catalog.xml now only contains |
Great! is there some other issues with XML catalog? |
@angelozerr no issues with XML catalogs any more, thanks! |
Test works, I close this issue. Thanks @Again @ralfhandl ! |
To make validation and completion work I currently need two catalog entries, e.g.
From the XML Catalog specification I would have expected to just need the
<uri>
entry because<public>
is intended for resolving external identifiers and expressly not for resolving XML namespace names:However with just a
<uri>
entry neither validation nor code completion are triggered.Note: this issue is of low importance as validation and completion work fine as long as the catalog contains these "duplicate" entries. Mentioning this in documentation on "how to write a catalog.xml" would be sufficient.
The text was updated successfully, but these errors were encountered: