Andr? van Toly <[EMAIL PROTECTED]> wrote: > And i found some new errors after changing the > context of a builder in the JSP editors. I tried > to change the context of the builder 'chatter' > from 'system' into 'forum' in 'typedef'. After > the error message the builder appeared to be > inactive, after a restart it was active again > > ---Andre > > Sorry, an error happened > > Before start of result set > Stacktrace: > Before start of result set > at > > org.mmbase.storage.implementation.database.JDBC2NodeWrapper.drop(JDBC2NodeWrapper.java:308) > at > org.mmbase.module.core.MMObjectBuilder.drop(MMObjectBuilder.java:410) > at > > org.mmbase.module.corebuilders.ObjectTypes.deleteBuilderTable(ObjectTypes.java:475) > at > org.mmbase.module.corebuilders.ObjectTypes.commit(ObjectTypes.java:184)
This seems to be yet another problem, completely unrelated to Community or SearchQuery. It is probably be caused by the fact that you are trying to change a typedef node. It thinks you edited the XML, which it knows only to solve by dropping and creating the table again. This then, gives a NullPointer exception in JDBC2NodeWrapper. There might be 2 bugs here: 1. You did not change the XML, so why does it think so? Perhaps I ****** something up in taglib. I'll look into it asap (but perhaps only in the freeze) 2. Why does JDBC2NodeWrapper give a NPE on drop. This has something to do with new storage layer. If I were you, I would submit this as a high priority bug to the bugtracker (perhaps even 2) Michiel -- Michiel Meeuwissen Mediapark C101 Hilversum +31 (0)35 6772979 nl_NL eo_XX en_US mihxil' [] ()
