Are we planning to provide TrAX-ized ways to set these
xsltc-specific properties? (Sorry if I missed an
earlier conversation about this) These sound like
perfect items to get set through
TransformerFactory.setAttribute(String attrName,
Object value) calls. That way, someone's properly
written code will work on any TrAX processor
(presuming you catch any IllegalArgumentExceptions
that denote the particular impl doesn't support that
property).
This would be good for testing too, since any tests
written to the TrAX interfaces will (mostly) work on
either xalan or xsltc. I.e. for a conformance test
driver, we could have it attempt to always set these
attributes on the TransformerFactory. If we happen to
be testing xsltc, these will take effect. If we
happen to be testing xalan, these'll throw
IllegalArgumentException, which we'll ignore. In
either case, the overall result (or the
conf/output/file.out) file should be the same for
both.
(i.e. even though this test doesn't specifically
validate the dir-setting features, there are plenty of
other bits of functionality that are common between
the processors, presuming we can address all this
stuff through TrAX).
OK, I haven't had enough coffee yet: am I making any
sense?
- Shane
---- you Morten Jorgensen <[EMAIL PROTECTED]>
wrote ----
No, you can't. Not after the re-design of our TrAX
support.
But, the org.apache.xalan.xsltc.compiler.XSLTC class
has a
set of public methods that can be used to set the
package
name, translet class name, output directory and such:
setClassName(String className);
setDestDirectory(String absolutePathName);
setPackageName(String packageName);
setJarFileName(String archiveName);
Morten
=====
<eof aka="mailto:[EMAIL PROTECTED]";
humor="Du sublime au ridicule il n'y a qu'un pas." />
__________________________________________________
Do You Yahoo!?
Get personalized email addresses from Yahoo! Mail
http://personal.mail.yahoo.com/
