Well, I've sort of solved the problem but still haven't figured out exactly why it was happening to begin with. If I get chance this weekend I'll maybe kick up the debugger and see if I can't track down what was going on.
Rich On Tue, Jul 29, 2008 at 11:37 PM, Niclas Hedhman <[EMAIL PROTECTED]> wrote: > On Wednesday 30 July 2008 13:57, Richard Wallace wrote: > > Yup, that's it exactly. > > So, the Render phase calls some set() somewhere?? Perhaps a concern that > kicks > in and do something. Well, that is the most logical question, although I > wouldn't totally exclude bug in Qi4j. > > If you can trace down where such thing happen and it happens in Qi4j Core, > then great and we appreciate it. If you don't have the time and need this > fixed quickly, then the obvious work-around is to discard() instead of > complete()... > > You should probably also learn that there is a system > property "qi4j.compacttrace", that you perhaps should set to "off" to get > the > full story in any stack traces that you may encounter in this pursuit. > > > Cheers > -- > Niclas Hedhman, Software Developer > > I live here; http://tinyurl.com/2qq9er > I work here; http://tinyurl.com/2ymelc > I relax here; http://tinyurl.com/2cgsug > > _______________________________________________ > qi4j-dev mailing list > [email protected] > http://lists.ops4j.org/mailman/listinfo/qi4j-dev >
_______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
