The XSL tooling plugin uses a resolverExtension to accomplish something similar. You may be able to find pointers there.
IIRC, it is the core plugin. Mind you, they will be cases where you can't find a project, in case a resource is loaded directly from the file system, e.g. with File > Open -Jesper On 21/11/2012, at 17.04, Martin Lippert <lipp...@acm.org> wrote: > Hey! > > A while ago I asked this question, which is still open on my end and I am > still hoping to find some help here. Any idea? That would be really really > great! > > Thanks! > -Martin > > > > On 15.06.12 15:51, Martin Lippert wrote: >> Hey! >> >> We have implemented project-specifc XSD resolution for the Spring IDE, >> but are still suffering from a few cases where we don't get any >> information about the project for which the XSD should be resolved. And >> I would love to hear from you whether this is possible at all, and what >> I maybe need to take a look at in this case. >> >> We have implemented the extension point: >> org.eclipse.wst.common.uriresolver.resolverExtensions >> >> with stage=postnormalization >> >> But that doesn't seem to always give us the necessary information to >> which project this resolving belongs to. And I am not sure whether the >> webtools allows us to fully implement this. >> >> Any pointers and help highly appreciated! >> -Martin > _______________________________________________ > wtp-dev mailing list > wtp-dev@eclipse.org > https://dev.eclipse.org/mailman/listinfo/wtp-dev _______________________________________________ wtp-dev mailing list wtp-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/wtp-dev
