Are there reasons or objections not to change
the access to the contenthandler in the xsp.xsl
from "this.contentHandler" to only "contentHandler"?
Then we could do a local redirect of SAX events:
...
contentHandler.startElement("", "item", "item", xspAttr);
{
AttributesImpl xspAttr = new AttributesImpl();
XMLConsumer contentHandler = ...;
contentHandler.startElement("", "item", "item", xspAttr);
}
It gives us the feature of redirecting SAX events
to other XMLConsumers. (This would be a real seamless
integration for the XForm and DOMObject implementation)
There should be no undesired side effects...
--
Torsten
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
