Re: [Cruisecontrol-user] Re: XSLT Processor

[Ivan L. <Iva...@ya...>]

Hello Michael,

Saturday, April 22, 2006, 12:35:28 PM, you wrote:

>>>(I really am asking, I don't know enough about this yet to say if it'll really work)
>> 
>> It is already does, I simply droped Saxon into CC libs and started it.
>> Saxon provide transformer factory and now CC works with Saxon instead
>> of Xalan. No code need to be changed.
>> 
> But this works only as long as you are using XSLTs that could be 
> interpreted by both processors, right?
> I think the problems begin to start if you modify xslt with specific
> things that are not supported, e.g. XSLT 2.0 for Xalan.

> On the other hand and for the worries Jeffrey had about usage of Saxon:
> As far as I remember Saxon is the reference implementation for 
> XSLT-Recommendations, so I think it is rough tested and used.
How long have you been working with Saxon?
How many error have you come over?

How long I have been working with Xalan? - tried a few times
How many error I have come over? - just now, stupid - StackOverflow
for no reason, poor memory management and slow as ....

As I recall, current CruiseControl implementation simply does not
work, or I can't call 1+G of RAM and StackOverflow as normal
operation. It has been proven many times by many users.

As a user, I did my part and offer a solution that does not require any
changes to current codebase. This solution turns overburden memory
eating monster into proper application.

b.t.w. Have you tried my fix ? If not, give it a shot, using 5-10Mb
log file.

Honestly I don't understand what is this discussion about, the choice
is simple:
CC + Xalan + 6Mb log file = OutOfMemory, StackOverflow, etc...
CC + Saxon + 6Mb log file = 3-4sec processing time.

-- 
Best regards,
 Ivan                            mailto:Iva...@ya...