[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[wtp-incubator-dev] Dependency on Validator framework - options going forward?
|
Hi guys,
About XSL validation. It seems there's a new proposal (bug 212196) to
look into overhauling the validation framework of WTP in general [1].
All idea, no code (?). I have no idea whether that is in scope for WTP
3.0 or not, or whether we should be making any assumptions based on
that. Dave, I know your gripes with the validators go beyond XSL, what
do you make of it?
But as I see it, we have three options for controlling the XSL validation:
A - Await and encourage a new framework in bug 212196 [1], and align
with this from the start.
B - Use the validator framework in place, but also push for bug 102882
(include/exclude paths, [2]) or bug 208448 (validator prefs at folder
level) and/or bug 187193
C - Make XSL validation "something else" outside the scope of WTP
validation (as Dave has suggested), more like a builder, with explicit
and very visible UI.
At any rate, I'm looking into writing a fast and accurate validator in
line with the requirements from bug 208836 (XSL Validation, [3]), which
will work well with dependency updates and "validate as you type"
functionality. I'm trying to make it independent of the choice outlines
above.
-Jesper
P.S: No CVS probs here, once I figured out how to stick with the
/cvsroot/webtools (and not add to that), AND stopped letting some
selected Working Set fool me into thinging the repo was empty.
[1]: https://bugs.eclipse.org/bugs/show_bug.cgi?id=212196
[2]: https://bugs.eclipse.org/bugs/show_bug.cgi?id=102882
[3]: https://bugs.eclipse.org/bugs/show_bug.cgi?id=102882
