Yes, that is what I was referring to. Thanks for fixing it. I'll give
it another try soon.
Chris
Morten Jorgensen wrote:
>Chris,
>
>Are you referring to the bug you filed? That bug was fixed today,
>meaning that there was a bug in XSLTC that it is not there anymore.
>So your configuration wa
Chris,
Are you referring to the bug you filed? That bug was fixed today,
meaning that there was a bug in XSLTC that it is not there anymore.
So your configuration was correct and there is nothing you need to
do other than download the latest CVS tree or wait for the next
release of Xalan.
Morten
I guess I must have had something configured wrong or something. While looking
for the source of the exception, I had stripped my testcase down to nothing
more than a stylesheet that imports another stylesheet that declares a variable
and I still got an exception. If I did not import the other
very time?
>
> -- bk
>
> >> -Original Message-
> >> From: Morten Jorgensen [mailto:[EMAIL PROTECTED]]
> >> Sent: Monday, December 10, 2001 1:36 AM
> >> To: [EMAIL PROTECTED]; Chris McCabe
> >> Subject: Re: State of XSLTC
> >>
> &
Does the TraX API still re-compile the translet every time?
-- bk
>> -Original Message-
>> From: Morten Jorgensen [mailto:[EMAIL PROTECTED]]
>> Sent: Monday, December 10, 2001 1:36 AM
>> To: [EMAIL PROTECTED]; Chris McCabe
>> Subject: Re: State of XSLTC
Chris,
> Is XSLTC anywhere near a state of being generally useful?
It is indeed.
> I was under the impression that it mostly works, but it seems
> that very basic stuff does not work.
I am not sure what you are referring to. XSLTC conforms to the
XSLT 1.0 and XPath 1.0 specs. There are about 1
Is XSLTC anywhere near a state of being generally useful? I was under
the impression that it mostly works, but it seems that very basic stuff
does not work. Is anyone using it successfully yet? Is there a
timeline of any kind that shows planned implementation schedules? I
would like to try
