> Hello,
> I found out where I get the exception from. It is because I am using the
Evaluator with an XObjectPtr in scope which I am not allowed to do.
>
> So you are saying there isn't any easy way to set the Node Value using
Xalan. Why is there a setNodeValue( ) present then?

Because the XalanDOM classes describe an abstract set of base classes that
anyone can implement to provide transformation input to the processor.  It
just happens that our default implementation does not allow mutation of the
tree.  There is no reason why someone couldn't create an implementation
that would allow modification.

Dave

Reply via email to