[news.eclipse.webtools] Re: XSLT extensions

[Dave Carver <d_a_carver@xxxxxxxxx>]

One of the items I'm looking into is adding an Extension point to allow adopters to add their own XSLT extensions for content assist. 

Processor Specific extensions bug is here:

https://bugs.eclipse.org/bugs/show_bug.cgi?id=243581

And general Content Assistance extensions are here:

https://bugs.eclipse.org/bugs/show_bug.cgi?id=259721

Now, you can look at the  org.eclipse.wst.xsl.ui.internal.StructuredTextViewerConfigur ationXSL and see where it invokes the XSLContentAssistProcessor.   What you could do is extend this the StructuredTextViewerConfigurationXSL class, to add in your content assitance Processor as well as keep the existing processor class.  You would then need to create your own Editor extension point that use your StructuredTextViewerConfigurationXSL.

However, with this said, I would encourage you to look at enhancing the existing code to provide a general ContentAssistance extension point and have XSLContentAssistProcessor leverage that.  The existing content assitance could then be contributed through extension point, and adopters could add their own.

Content Assistance is best implemented by extending the AbstractXSLContentAssistRequest class.   This is what all of the current content assitance classes do.  You can find everything in org.eclipse.wst.xsl.ui.contentassist.

If you do implement the extension point route, please consider contributing it back, and I'll make sure that I devote some time to getting it into a build.