XSL Executor API should ensure extensibility of XSLT Execution action.
XSL Executor API will be similar to Java Executor API. Each XML document will
have associated XSL Executor instance (XML node's property). Default
implementation will be JAXP XSL Executor.
FOP support could be realized as another XSL Executor implementation. Cocoon
framework uses XML document to describe sequence of transformations. I can
imagine Cocoon XSL Executor implementation which will support this Cocoon Map
Let these are considered while planning next release.
Target milestone was changed from not determined to TBD
Public contact may be introduced.
Google showed nothing about the "Java Executor API" in netbeans.org. Was the API renamed or made redundant?