|
| Re: XML schemes provision [message #214044 is a reply to message #214036] |
Tue, 20 May 2008 13:38   |
Eclipse User |
|
|
|
Originally posted by: dcarver.starstandard.org
Walter Brunauer wrote:
> Hi!
>
> I just started using WTP (I am currently on 3.0 M7) and I managed to
> provide my own XML schemes (i.e. namespace names) to the XML catalog
> within the preferences via the
> org.eclipse.wst.xml.core.catalogContributions extension point. However,
> this does not suffice the requirements I have to cover within my
> application. Two questions:
>
> 1. Is there any way to (maybe programmatically) provide different
> schemes or different versions of the same schemes per project? If so, do
> I need any specific nature or other properties for such projects?
You will need to create a custom URIResolver or a Content-Type Describer
that handles the loading of the particular schema that you need loaded
at runtime. One such example is in the XSL Tooling incubator project
in the org.eclipse.wst.xsl.core plugin project.
>
> 2. Is there any chance to tell the XML editor to still look for XML
> schema definitions in the provided entries within the XML catalog, if
> e.g. a "xsi:schemaLocation" schema location reference in the XML file
> itself cannot be resolved directly? Right now, there seems to be no
> fallback mechanism in place...
I think your best bet is to go with a Custom Resolver.
|
|
|
|
Powered by
FUDForum. Page generated in 0.01471 seconds
] 
Search
Help
Register
Login
Home
