Those jars are only reqruired if you are using the compiled version of Xalan.
We don't use that as we always use the interpretive version since this is the one you need for debugging (the compiled version can't be debugged).
As for speed, the interpretive version is also faster than the compiled version if you perform a transformation exactly once (which we do).
We could ship those jars if there is any demand for using the compiled version (though it should produce the same results as the interpretive version, but this can't be guaranteed I guess).
----- Original Message ----
From: David M Williams <david_williams@xxxxxxxxxx>
To: wtp-incubator-dev@xxxxxxxxxxx
Sent: Monday, 4 August, 2008 1:56:27 PM
Subject: [wtp-incubator-dev] what about distributing bcel and jcup_runtime?
I know these bundles are optional, but required for certain compile functions to work in XSL.
Is there no reason to distribute them with our XSL tooling? Anything faster? Anything more 'production' ready?
Just required for debugging? Just required for server side deployment?
I just last night noticed we were not distributing them, but have a vague, long-ago memory that we were supposed to.
Should we add them to the feature to
make sure they get pulled in?
Thanks,
