hi,
I do like the idea of moving stuff that is not the 'core' business of
mmbase outside of mmbase and using things in ways the rest of the world
is using them. However I don't know anyting about the current database
implementation so for now I'll abstain:
Remove jdbc module from HEAD
[_] +1 (YEA)
[X] +0 (ABSTAIN )
[_] -1 (NAY), because :
[_] VETO, because:
Some questions/remarks on Michiels mail:
Michiel Meeuwissen wrote:
- We can ship a working mmbase with an hsql url.
I also really like that. But it'll be easier to ship a war using a j2ee
datasource won't it?
- You can easily try out another app-server you are not familiar with.
I don't mind this a lot: If you want to try a new appserver you probably
want to learn about it don't you? Learning how to configure its database
might be a nice part of the process ;-)
- Running stand-alone remains an option, also for junit tests
Is this really necessary? Isn't it easier to use a test-container? (I
still have to go and learn about the mmbase unittests, sorry)
Simon
_______________________________________________
Developers mailing list
[email protected]
http://lists.mmbase.org/mailman/listinfo/developers
