Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "XSL Tools Requirements"
(→Launching) |
(→Launching) |
||
| Line 5: | Line 5: | ||
==Launching== | ==Launching== | ||
* {{bug|213855}} - XSLT shouldn't rely on JDT to function, particularly for XSL Launching configurations as every XSL transformer extension could have a differen requirement to launch. Potentially the XSL transformer could be non-java based. | * {{bug|213855}} - XSLT shouldn't rely on JDT to function, particularly for XSL Launching configurations as every XSL transformer extension could have a differen requirement to launch. Potentially the XSL transformer could be non-java based. | ||
| + | * - Launching should be able to run either a simple pipeline or a more complex pipeline using [http:///www.xproc.org/ XProc] as the configuration language. An [http://yax.sourceforge.net/ yac] is an example of an xproc processor. | ||
==Debugging== | ==Debugging== | ||
Revision as of 10:19, 27 December 2007
What should the initial requirements be for XSL Tools 1.0 release. Note that not all ideas will necessarily make it into the first release. Please use this page to make your suggestions as well as enter an enhancement request in the Web Tools Incubator component. If you do make a bug/enhancment request, please put the bug number here and link to it as well.
XSL Tool Features Requests
Launching
- bug 213855 - XSLT shouldn't rely on JDT to function, particularly for XSL Launching configurations as every XSL transformer extension could have a differen requirement to launch. Potentially the XSL transformer could be non-java based.
- - Launching should be able to run either a simple pipeline or a more complex pipeline using XProc as the configuration language. An yac is an example of an xproc processor.