I would suggest looking into the approach I am taking. We store a lot
of configuration information in a repository that sort of resembles JDK
1.4 preferences. To integrate this with Cocoon I wrote my own source
resolver. So I can put prefs://somestring as the location. The source
resolver then determines where the data catalog actually resides and
sets the resolver's systemid to a value that is unique for that
location. Now, your resolver is free to pretty much do whatever you
like. It can dynamically create the catalog from multiple sources or
whatever needs to be done.
Ralph
K Sramko wrote:
Thats exactly my problem: I can't say, where the location of the catalogue is,
because is it's written in a database. I can't even say, how much catalogues
I have for a transformer. And the data in the catalogues can change as well
as the location an nubmer of catalogues. I looked into the docs and found the
mentioned import-actions, so I knew how to get the location of a catalogue
dynamicly. But I haven't a solution for my second problem: the number of
catalogues. The only thing, my boss toled me, maybe we could create a one
catalogue out of the the others, to refer to just one file. But if you have a
any solution, pleas give me a hint.
thx,
Kiril
