2005/9/13, Nico Klasens <[EMAIL PROTECTED]>: > Hello Developers, > > Yes, you are reading it correctly, I want to remove something almost > everyone in the community is using. I have some good reasons for this. > > For a very long time, there is support for j2ee datasources in mmbase. > The jdbc module tries to implement the same functionality as these > datasources, but does not have what it takes to be a real connection pool.
There are numerous good pooling jars around. and I think supporting data sources Is very good. Adding support for data source does not necessary mean that you need to use jndi or whatever sun calls it today so I don't understand how you can remove jdbc.xml I will vote -1 if it is not possible to run MMBase outside of a container. What do you propose for that? I'd be very very happy with any way to start mmbase MMBase.setDataSource() sounds great to me! > Another advantage is that the web > application does not have environment settings which makes it much > easier to deploy to a different server. This is actually false, the only thing you add is an extra layer of configuration options and problems. not only your database setting and mmbase settings must match , but also the jndi names in the server.xml (in tomcat) and names in the web.xml configuration(int tomat) and the name used in the application. and if you want to run 2 mmbases on one server the checkout the mess. Also we do provide database specific storage strategies and table creation, currently I think this is based on the jdbc driver name. How is that going to work if your hack passes? _______________________________________________ Developers mailing list [email protected] http://lists.mmbase.org/mailman/listinfo/developers
