DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=30187>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=30187

Can not evaluate params/variables from a "TraceListener" event during the 
transformation process.

           Summary: Can not evaluate params/variables from a "TraceListener"
                    event during the transformation process.
           Product: XalanC
           Version: 1.8
          Platform: Other
        OS/Version: Solaris
            Status: NEW
          Severity: Enhancement
          Priority: Other
         Component: XalanC
        AssignedTo: [EMAIL PROTECTED]
        ReportedBy: [EMAIL PROTECTED]


I am using the Xalan C++ API in a real-time financial application which need to 
apply XSLT transformations on XML input messages received on-the-fly.
On the process output, I get the transformed output XML.

In the XSLT stylesheet, I defined several templates which take input parameters 
(like function calls) and I also defined global XSL variables.

For security reasons, I need to log everything. I use the "XalanTransformer" 
object to make the transformation and I implemented the "TraceListener" object 
to log most of the parser/transformer events.


I am pretty happy with this but I have the following problem :

I did not find any way to display the parameters or global variables values 
during the transforming.

I know that a "StylesheetExecutionContext" object implements the "getVariable
()" and "getParamVariable()" methods which should allow to do this.

Unfortunately, the "StylesheetExecutionContext" provided in the "TracerEvent" 
and "SelectionEvent" only provide a "const" instance of 
the "StylesheetExecutionContext" object which help from calling the "getVariable
()" and "getParamVariable()" methods which are not "const".


=> The API does not allow to call "getVariable()" and "getParamVariable()" in 
a "TraceListener" callback event.

It would be a good enhancement for us if you allowed us calling these functions 
from a "TraceListener" event so we are able to log all the variable and 
parameters values during the transformation processes.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to