I guess the issue is resolved. If you see very weird error with XSP compilation - scream now, before release!
It was the combination of several smaller bugs and feature additions in Cocoon accumulated into this problem, like: not recycling what should be recycled, exception obfuscation (thanks to SAXException!), and recently added source resolution feature. Vadim > -----Original Message----- > From: Berin Loritsch [mailto:[EMAIL PROTECTED]] > Sent: Friday, January 25, 2002 11:16 AM > To: [EMAIL PROTECTED] > Subject: Re: Update: SHOWSTOPPER: XSPs do not compile... > > Vadim Gritsenko wrote: > > > No, it is slightly more complex then this :( > > > > XSP compilation works *perfectly* until MRUStore purges cached > > Logicsheets (done with the help of crawler). When you try to compile XSP > > after this, XSP engine re-creates logicsheets (and, btw, forgets to > > assign a logger for them), and for some reason logicsheets are being > > applied twice, in the order (when accessing simple.xsp): request.xsl, > > log.xsl, capture.xsl, xsp.xsl (here the result is valid!), log.xsl, > > capture.xsl, xsp.xsl. The net result is 8 bytes or so... > > > ooh, that's bad. > > I have noticed that on occasion, Cocoon will try to process the same > request twice for the same request. Could this have anything to do with > the Servlet Container, or have we gotten too compex for ourselves and > need to simplify? > > > -- > > "They that give up essential liberty to obtain a little temporary safety > deserve neither liberty nor safety." > - Benjamin Franklin --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
