Hi everyone, I'm working on a project that involves writing a new data adapter for Sesat to allow federation from an Endeca index (http://www.endeca.com/products-information-access-platform.htm). Mick has been helping me one-on-one with getting a local instance of Sesat up and running, but I'll direct my next question to all of you.
Endeca already has a Java API, so the makeup of the search command will be similar to SolrSearchCommand and its related components. However, rather than adding the Endeca libraries and our search command into the project and building them together, we'd like to be able to compile our search command and config externally so it can be dropped into a Sesat deployment. Ideally, we'd be adding a jar in the Tomcat container and (through the existing naming lookup) referring to the classes in the modes.xml of our skin. Is this possible? The nuances of the build process are still a mystery to me, so I'm not sure how modular the search commands are. Could someone also give me more details on the lookup between modes.xml and the search configuration classes? Mick had mentioned there is a naming lookup from the *-command element names to the configuration classes, but we haven't been able to find it. Thanks in advance for any answers or general advice you can give me! -VJ _______________________________________________ Kernel-development mailing list [email protected] http://sesat.no/mailman/listinfo/kernel-development
