My backend classes have a global configuration file. The file is passed in sitemap:
<map:transformer name="mytrans" src="myTransformer"> <configdir>work</configdir> <configfile>myconfig.cfg</configfile> </map:transformer>
The configuration is passed by transformer to backend classes, because my backend classes don't have any clue where to get configuration from. So I have to pass this via transformer.
From what I see you only need to separate the "connect to backend" logic from the cocoon specific interfaces generator and transformer. It allows higher reuse as you can access it directly from flow, no need to go through a superflouos pipeline.
Will have to think about it ;-)
With a non-Cocoon-specific component you would of course have no access to the sitemap (though there might be solutions). You could move the config to cocoon.xconf then.
Joerg
What about a SQLTransformer? ;-)
I don't like it for exactly that reason. And would not use it.
I don't like it, too. See discussion about where to hold business logic.
Have not read the thread until now - it's so long and cluttered :)
Joerg
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
