Thanks Torsten. Yes, that helps somewhat. > I think you should be able to extend JdbcDataSource ....
Right, and your comments on how to do that make sense. > and use that datasource type instead of the jdbc one in your xconf. The word "use" is where things get a little murky, and another detail from me may help clarify. We use SQL-Transformer. (We love SQL-Transformer!) It takes a sitemap parameter like so: <map:parameter name="use-connection" value="myDatasourceName"/> How can I cause myDatasourceName to match an instance of my new datasource class? It seems that I will need my MyDatasource to go into the same "datasources" set as all the ones defined in cocoon.xconf using the <jdbc> tag under <datasources>. Can I do this using a regular <component> tag (at the top level of cocoon.xconf, under <cocoon>, not under <datasources>), with a certain role? (What role? Is there more to it than having the right role on the component?) Or by defining, say, <sc_jdbc> to be a cocoon.xconf tag that goes under <datasources>, and is bound to the classname of my datasource? (Where would I do that?) -- View this message in context: http://www.nabble.com/Securing-JDBC-credentials-that-are-stored-in-cocoon.xconf-tp15600542p15601858.html Sent from the Cocoon - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
