On Sat, Aug 17, 2002 at 02:53:12PM -0400, David Allen wrote: <> > This is the same thing that was causing the insert bug in fproxy. > > When people pass (Metadata)null to the DocumentCommand constructor, > this is a very predictable result, since the constructor ends up > calling null.someMethod(). > > The question is this - *why* are people creating DocumentCommand > objects with null arguments? Is there a serious issue related to > creating new legitimate Metadata object to pass?
The "next" metadata object in the DocumentCommand actually has an important meaning (basically it indicates a redirect), which I why I couldn't use the original patch. It was just sloppy of me to try to get away with grabbing the settings from that metadata object (or maybe not to have documented the behavior in the first place). -- Oskar Sandberg oskar at freenetproject.org _______________________________________________ devl mailing list devl at freenetproject.org http://hawk.freenetproject.org/cgi-bin/mailman/listinfo/devl
