There are a lot of issues. We need to have a sit-down design session with
Morten and Todd (soon!). I don't think we're quite ready to set a schedule
yet. In the meantime, I don't think you want to slow down the
stabilization of XSLTC.
-scott
Shane_Curcuru
@lotus.com To: [EMAIL PROTECTED]
cc: (bcc: Scott Boag/CAM/Lotus)
06/06/2001 Subject: Re: XSLTC DOMImpl class
10:53 AM
Please
respond to
xalan-dev
This sort of also begs the question: can we review the overall plan / rough
time schedule for merging the input 'sources' of XSLTC and Xalan? The
long-term plan is to keep both transform engines (Xalan=general purpose
transformer; XSLTC=translet generator) but to merge or use common inputs
and outputs and such.
I guess (and pardon the question if we've already answered it recently): If
we're close to getting rid of the specific XSLTC DOMImpl in favor of a
merged/normal one shared with Xalan, is it worth making significant changes
to it? Or will it be a couple of releases before we can do this, so we
might as well keep existing users happy for now?
- Shane
---- you [EMAIL PROTECTED] wrote ----
> hi all,
> is it possible to add a method 'clearDOM()' (if someone hasn't
> already done it) so that the DOMImpl class
> can be reused all the time??
- XSLTC DOMImpl class Marco . Mistroni
- Re: XSLTC DOMImpl class Morten Jorgensen
- Re: XSLTC DOMImpl class Shane_Curcuru
- RE: XSLTC DOMImpl class Scott_Boag
- RE: XSLTC DOMImpl class Marco . Mistroni
- RE: XSLTC DOMImpl class Marco . Mistroni
- RE: XSLTC DOMImpl class Marco . Mistroni
- Re: XSLTC DOMImpl class Tom Amiro
- RE: XSLTC DOMImpl class Marco . Mistroni
- RE: XSLTC DOMImpl class Marco . Mistroni
