> -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Michiel Meeuwissen > > BTW in StorageManagerFactory.java I found the following: > > // instantiate handler > try { > java.lang.reflect.Constructor constructor = > queryHandlerClass.getConstructor(new Class[] {Map.class}); > SqlHandler sqlHandler = (SqlHandler) > constructor.newInstance(new Object[] { disallowedFields } ); > log.service("Instantiated SqlHandler of type " > +queryHandlerClass.getName()); > > // Chained handlers, to be implemented later. > /* > Iterator iHandlers = > reader.getChainedHandlerClasses().iterator(); > while (iHandlers.hasNext()) { > Class handlerClass = (Class) iHandlers.next(); > constructor = handlerClass.getConstructor(new > Class[] {SqlHandler.class}); > queryHandler = (SearchQueryHandler) > constr2.newInstance(new Object[] {queryHandler}); > log.service("Instantiated chained > SearchQueryHandler of type " > + handlerClass.getName()); > } > */ > // initialize query handler. > queryHandler = new BasicQueryHandler(sqlHandler); > > } catch (NoSuchMethodExcept > > > So I think we can conclude that the 'new' (and default) > storage layer does not support chained handlers? > > This might be an issue, isn't it?
It sure is. It goes without saying that it should that it should support the options available for databases in the previous databaselayer. In addition, sqlhandlers and chainedhandlers are configurationoptions for one particular type of queryhandler only, i.e. SqlQueryHandler. They apply to databases but not storageproviders in general. The codesnippet above appears to be a hack to include the present SqlQueryHandler configuration options. Preferably a QueryHandler should be able to configure itself, honoring the fact that different QueryHandlers can have different configuration options. Rob van Maris Technical Consultant Quantiq xmedia & communication solutions Koninginneweg 11-13 1217 KP Hilversum T +31 (0)356257211 M +31 (0)651444006 E [EMAIL PROTECTED]
