The TrAX design and implementation for XSLTC has changed since
the recent release. Please do not try to use the samples that
came with the release together with the current code. The old
implementation of the TrAX TransformerFactory was:
org.apache.xalan.xsltc.runtime.TransformerFactoryIm
In trying to run the sample code that comes with the xalan dist:
java JAXPTransletOneTransformation
Exception in thread "main"
javax.xml.transform.TransformerFactoryConfigurationError:
java.lang.ClassNotFoundException:
org.apache.xalan.xsltc.runtime.TransformerFactoryImpl
at
javax.xml.tr
Gordon,
> In the 2.2d6 release in the TransformerFactoryImpl, there is still a check
> for the "transletPool" system property. I am now confused on whether this
> is in use or not. I am using it to make sure that all my translets end up
> in the same directory (so the can be picked up in the cl
ent: Tuesday, July 17, 2001 8:36 AM
To: [EMAIL PROTECTED]
Subject: Re: Setting Package and directory properties in XSLTC
Hi Shane,
With TrAX the user should not have to deal with package names,
translet class names and output directories. With the new TrAX
design we wrap the translet class and aux
Hi Shane,
With TrAX the user should not have to deal with package names,
translet class names and output directories. With the new TrAX
design we wrap the translet class and auxiliary class definitions
inside the Templates object. The user will not even know what
the translet class name is (nor w
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 c
TED]>
> > >>Delivered-To: mailing list [EMAIL PROTECTED]
> > >>From: "G. Todd Miller - XML Tech Ctr - Development"
> ><[EMAIL PROTECTED]>
> > >>Subject: Re: Setting Package and directory properties in XSLTC
> &
t;list-post: <mailto:[EMAIL PROTECTED]>
> >>Delivered-To: mailing list [EMAIL PROTECTED]
> >>From: "G. Todd Miller - XML Tech Ctr - Development"
><[EMAIL PROTECTED]>
> >>Subject: Re: Setting Package and directory properties in
[EMAIL PROTECTED]>
>>list-post: <mailto:[EMAIL PROTECTED]>
>>Delivered-To: mailing list [EMAIL PROTECTED]
>>From: "G. Todd Miller - XML Tech Ctr - Development"
<[EMAIL PROTECTED]>
>>Subject: Re: Setting Package and
>>list-unsubscribe: <mailto:[EMAIL PROTECTED]>
>>list-post: <mailto:[EMAIL PROTECTED]>
>>Delivered-To: mailing list [EMAIL PROTECTED]
>>From: "Gordon Cooke" <[EMAIL PROTECTED]>
>>To: "xalan-dev" <[EM
I need to be able to set the packagename and destination directories, at
runtime, for all of the xsl documents that we compile. THe accessor methods
for the properties are defined as private. I am wondering if there is a
reason for this and what impact making them public would have. As it stands
11 matches
Mail list logo