DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7181>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7181 esql:group behaves erratically ------- Additional Comments From [EMAIL PROTECTED] 2002-03-19 16:26 ------- Hello all, Unfortunately, <esql:error-results/> has no effect, no exception is thrown, nor do any warnings or errors appear on the cocoon logs... So I guess we're back to step nr.1 ... Let's get to the basics: the ESQL logicsheet is fat. ("politically correct" term: overweighted). I tried to implement some basic grouping functionality but I'm progressing very slow because I have very little knowledge of what happens in relation to the grouping code. So I pop a few calls off my brain stack and start to examine the (obviously outdated) exsl.xsd, to learn what a "correct" esql page looks like, only to find that the whole XMLSchema for ESQL needs to be rewritten: it simply consists of ONE rule (everything's nested)! So, without documentation, noone else can really understand, let alone debug the logicsheet! I assume that very few people use <esql:group> right now, so my guess is that it would be a good idea to rollback the changes, define a good solid schema for esql, and THEN proceed to the actual implementation... (ahhh, good'ol'Open Source!) I can help in redefining the schema and the corresponding documentation. Would this be OK with you? Elias p.s. I attach the cocoon2 sample db as an Access .mdb file for your convenience... I apologize to all non-Window$ users... --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
