What is the "Where to Start" page?
This page gathers a list of features of XQDT and the place in the project where this feature is implemented or where the developer should first look and start understanding and debugging the functionality.
Feature table
XQDT features
| Feature name
|
Feature description
|
Infrastructure provided by
|
Plug-ins involved
|
Need to implement
|
Sample implementation
|
| New XQuery Processor Type
|
- A new XQuery processor type (called "interpreter" in DLTK terms) allows you to define you own logic for:
- execution environment (local, like in Zorba or Saxon; or remote, like MarkLogic Server)
- processor validation (e.g. only allow executables called zorba.exe to be added as the Zorba processor type)
- launching configuration (e.g. add custom launching parameters to your processor type upon execution)
|
DLTK
|
- org.eclipse.wst.xquery.launching
- org.eclipse.wst.xquery.launching.your_own_plugin
|
-
XQDTInterpreterInstallType
-
XQDTInterpreterInstall
- add the
org.eclipse.dltk.launching.interpreterInstallTypes extension point in "your_own_plugin" and provide a reference to your implementation of XQDTInterpreterInstallType
|
-
ZorbaInstall
-
XQDTInterpreterInstall
|
| Semantic Checker
|
- After the syntax check is complete without errors, a particular XQuery processor is allowed to report other errors in the XQuery code. E.g. function not available, namespace not declared, variable not defined, or even more complex problems that a particular processor may detect.
|
XQDT
|
- org.eclipse.wst.xquery.core
- org.eclipse.wst.xquery.launching
|
-
ISemanticValidator
-
AbstractLocalInterpreterSemanticValidator
- your IInterpreterInstall needs to implement
ISemanticValidatingInterpreterInstall and provide an instance of your defined ISemanticValidator
|
-
ZorbaSemanticValidator
-
MarkLogicSemanticValidator
|
