- From: Michael Sokolov <msokolov@safaribooksonline.com>
- Date: Wed, 08 May 2013 09:45:21 -0400
- To: Florent Georges <fgeorges@fgeorges.org>
- CC: public-expath@w3.org
On 05/07/2013 02:23 PM, Florent Georges wrote: > On 14 April 2013 19:10, Michael Sokolov wrote: > > Hi Michael, > > >> I see there is a generic Component interface in servlex, but there >> doesn't appear to be any mechanism for plugging in an XQuery >> component provider other than Saxon. >> > I have worked on that recently: > > http://github.com/fgeorges/servlex/commit/b195ba1a46 > http://github.com/fgeorges/servlex/commit/d20b32a3ac > http://github.com/fgeorges/servlex/commit/3c7478cbca > http://github.com/fgeorges/servlex/commit/e174382462 > http://github.com/fgeorges/servlex/commit/729298d666 > http://github.com/fgeorges/servlex/commit/e13670a689 > http://github.com/fgeorges/servlex/commit/7eb499a98f > http://github.com/fgeorges/servlex/commit/f4f9074887 > > I *think* it should be possible to implement now the new interface > Processors for any other processor. This abstracts the operations > used in Servlex, in a processor-agnostic way, including an ad-hoc > abstract data model (sequence, item, etc.) This is the result of > several refactoring passes, and I tried to keep the interfaces as > simple as possible (only for what is actually used by Servlex). Any > feedback on this welcome! You've been busy, Florent. Thanks! It might take me a little while, but I will definitely attempt a connector for Lux at some point. -Mike
Received on Wednesday, 8 May 2013 13:45:55 UTC