Bug 243581 - Provide an extension point for Processor specific extensions
Summary: Provide an extension point for Processor specific extensions
Status: RESOLVED FIXED
Alias: None
Product: WTP Source Editing
Classification: WebTools
Component: wst.xsl (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 enhancement with 1 vote (vote)
Target Milestone: Future   Edit
Assignee: wst.xsl-triaged CLA
QA Contact: David Carver CLA
URL:
Whiteboard:
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2008-08-08 09:21 EDT by David Carver CLA
Modified: 2010-04-28 17:13 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description David Carver CLA 2008-08-08 09:21:20 EDT
XSL Processors can define their own Processor specific extensions.   It would be nice to have a way that these could be made known to the XSL editor so that content assistance can be done.   A generic interface would need to be created, and then the extension point would excute the underlying processor specific api to retrieve the information and present it in a way that content assistance can use it.   This assistance should be available for elements, attributes, and xpath functionality.
Comment 1 David Carver CLA 2009-04-30 14:24:28 EDT
mass update to 3.1 target due to movement from wtp incubator to wtp source editing lost the original milestones.
Comment 2 David Carver CLA 2009-05-11 22:58:54 EDT
migrating prior 3.1 enhancements for future for further triage and planning.
Comment 3 David Carver CLA 2009-09-02 15:24:20 EDT
Assigning inbox items to triaged since these have all be triaged.
Comment 4 David Carver CLA 2010-04-28 17:13:56 EDT
This has actually been implemented through the Custom content assistance extension point.