| Summary: | [SSE] Unify the SSE model with the DLTK model | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Gabriel Petrovay <gabipetrovay> |
| Component: | WTP Incubator | Assignee: | Gabriel Petrovay <gabipetrovay> |
| Status: | CLOSED FIXED | QA Contact: | XQDT <xqdt> |
| Severity: | blocker | ||
| Priority: | P1 | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
Gabriel Petrovay
We just need to make sure that we can provide an alternative XQuery model independent from DLTK (and loose all DTLK benefit). My proposal is to have XQDT features built on top of our own model API (like IASTNode and sub interfaces), and have at least one implementation of this API based on DLTK. Does this make sens? ModelBuilder now works off a set of XQuery-specific AST interfaces. A default non-DLTK implementation is provided. Also added an visitor abstract class, and an accept method in IASTNode (which is not implemented yet). This is now closing. See the child bug for firther work: Bug 336736 |