|Re: Plans for URIResolverExtension for public consumption? [message #147169 is a reply to message #145805]
||Wed, 16 November 2005 06:14
| Craig Salter
Registered: July 2009
Steve Speicher wrote:|
> Here's a high-level summary of what I'm trying to do:
> I want to be able to associate an XML file with a plugin contributed
> XML Schema, using resource metadata. I want validation and content
> assist to use my contributed schema instead of the XML Catalog or
> xsi:schemaLocation. I'm doing this because I don't want to change the
> XML file (to include specific schemaLocations) the user has but enable
> them to validate it and edit it using alternate schemas. I also don't
> want to contribute it to the XML Catalog as it would affect too many files.
> I was going to do this by simply using the extension point
> org.eclipse.wst.common.uriresolver.resolverExtensions to do this but
> this doesn't appear to be public (still verifying if it will support my
> scenario as well).
> - Am I approaching the problem in the correct way?
> - Will the uriresolver.resolverExtension extension point become public?
> I see 2 bug reports for public APIs in WTP: 110275
> <https://bugs.eclipse.org/bugs/show_bug.cgi?id=110275> Publish APIs for
> WST in WTP 1.0 and 112281
> <https://bugs.eclipse.org/bugs/show_bug.cgi?id=112281> Declare XML
> Catalog Extension Point API for WTP 1.0.
> Thanks in advance,
> Steve Speicher
Yes, I think you're using the right approach. We're aren't planning on
making the URIResolver API public in WTP 1.0 since we're not convinced
that we have designed the API correctly at this point in time (any
feedback would be appreciated). I'm hoping we can make the URIResolver
public API in the WTP 1.5 time frame.
thanks for posting
Powered by FUDForum
. Page generated in 0.01904 seconds