Thanks for your reply, David.
In my case, it is very important that I keep a track of all the input and
outpout data.
I work on critical financial applications so we always need to keep some audit
information.
> As a quick work-around, you could always cast away const on the
> StylesheetExecutionContext
instance. I don't think we ever anticipated anyone would want or need to do
somethink like this,
and the StylesheetExecutionContext is const because opening up all of the
non-const functionality
isn't the safest thing to do.
Thanks for the trick. That is what I will do for the moment.
Do you think that evaluating params and variables into the TraceListener
callback can have serious
side effects on the transformation processus ?
> I would suggest you file a Bugzilla enhancement request for some way to get
> at variables in the
TraceListener calls.
I will do it !
Thanks a lot and congratulations for your very good work !
__________________________________
Do you Yahoo!?
Vote for the stars of Yahoo!'s next ad campaign!
http://advision.webevents.yahoo.com/yahoo/votelifeengine/
