On Thursday, Oct 30, 2003, at 16:28 Europe/Rome, Unico Hommes wrote:
Not all functionality of the Linotype SourceRepository is implemented. For instance I have not gotten to the versioning part yet.
ok
(And haven't
really thought out how this would best be done. (One idea is, continuing
with the WebDAV approach, to follow the Delta-V spec as a guide to
SourceRepository abstraction layer).
sounds like a good idea to me.
One other difference is is that I
don't use the Request and Part objects directly as input. But an
operation such as save() only gets called with two strings: input
location and output location that are both resolved via the
SourceResolver. This way you can use what you called at the GT 'pipeline
T-ing' in order to do some preprocessing. Or you could use the recently
added PartSource.
I'm not sure I follow you here, can you elaborate more on this?
Anyway from a flowscript it's as easy as:
importPackage(Packages.org.apache.cocoon.components.repository); var repo = cocoon.getComponent(SourceRepository.ROLE);
Cool, that's exactly what I wanted. Where does the polymorphism take place? at the cocoon.xconf level?
-- Stefano.
