>My personal feeling is that XSLTC's internal API should be
>deprecated (in 2.6.0?) given the difficulty of keeping two API's in
>sync.
+1. (Can I vote +2?)
We should be sticking with TRaX as much as possible. There will always be
some custom features, but those should be provided as general Xalan
capabilities rather than being specific to XSLTC. The only XSLTC-specific
operations should be the request that we run in XSLTC mode and the ones
involved in saving and loading translets as classfiles.
______________________________________
Joe Kesselman, IBM Next-Generation Web Technologies: XML, XSL and more.
"The world changed profoundly and unpredictably the day Tim Berners Lee
got bitten by a radioactive spider." -- Rafe Culpin, in r.m.filk
