Eduard Witteveen <[EMAIL PROTECTED]> wrote: > Pierre van Rooden wrote: > >We cannot remove these methods from the bridge, as they have been in use > >for over two years. > >Obviously when adding _new_ methods we don't need to add extra > >shortcuts, but we cannot remove the old methods. > Cant be the new classed / interface's be placed inside a different > directory? > Lets say a org.mmbase.api / org.mmbase.bridge2? (i'd say make it all > classes) The bridge would than be the extending / scripting part of the api.
We are not planning a new layer near the bridge. We are only busy making the current bridge interfaces (and corresponding basic implementations) more powerful. I think some of the more exotic legacy-ish functions as for example the createQuery version of getList(String, String.. few times more .., boolean (or so)), will not be placed in the bridge, but in a utility static class org.mmbase.bridge.util.Queries or so. I think bridge must remain to be a set of interfaces because alternative implementations are imaginable. (RMMCI, core2) > Btw: is there any check to see if a new jsp / other code is using an old > version of the bridge?(since this would be such a check) I do not understand. You can check if jsp is using a newer version of the bridge, if it does not compile against an older version. Michiel -- Michiel Meeuwissen Mediapark C101 Hilversum +31 (0)35 6772979 nl_NL, eo, en_US mihxil' []()
