cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Torsten Curdt" <tcu...@dff.st>
Subject RE: xsp.xsl
Date Mon, 23 Jul 2001 11:32:34 GMT
> > > Yes, there are side effects with logicsheets that use
> > > this.contentHandler.
> > 
> > Then we make them not to use it, too ;)
> > 
> > > I use the following construct to change the contentHandler :
> > > <xsp:logic>
> > >   ContentHandler oldHandler = this.contentHandler;
> > >   try {
> > >     this.contentHandler = otherHandler;
> > >     ...
> > >   } finally {
> > >     this.contentHandler = oldHandler;
> > >   }
> > > </xsp:logic>
> > 
> > ...I was just not sure if changing the contentHandler in
> > a multi thread environment is a good idea...
> > 
> > ..but if this is really ok - I'm also fine with that!
> > (Although a simple search and replace over logicsheets
> >  should be a bit cleaner - don't you think?)
> > 
> Unfortunately, search/replace won't be enough : some complex logicsheets
> (e.g. esql.xsl) split the generated code in sub-methods or inner
> classes. This would require more changes in these.

Well, anyway.. I am fine with your way :)

Thanks
--
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