> Victoria Vitaver wrote: > > And to figure out which bits of it arnt compiling I just comment things > > out until I get it to compile again. This surely is not the most optimal > > method of debugging, especially since I'm quite sure lucene at some > > stage does know EXACTLY why my xsp (or rather _xsp.java at that stage) > > is not compiling.
See the pipeline that shows the XML returned from the XSP I just posted to the other thread. As long as that returns something, you can check what is happening by adding tags to the XML: </xsp:logic> <language-yes/> <language><xsp:expr>language</xsp:expr></language> <language-check><xsp:attribute name="doc"><xsp:expr>docLanguage</xsp:expr></xsp:attribute></language-check> <xsp:logic> Add just a tag to know whether an IF works. Add a tag with a value or a tag with attributes to check your variables. solprovider --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
