cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Torsten Curdt" <tcu...@dff.st>
Subject xsp.xsl
Date Sun, 22 Jul 2001 10:02:21 GMT
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: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org


Mime
View raw message