2) Which class should i extend?
You should - initially - not extend classes (due to us being in a freeze we should at least attempt to give the impression that we are restraining ourselves). You should create a new resource file (xml) with properties to configure the storage layer for Oracle.
3) Can i create my own namespace and put the classes into that? (so i can compile a jar agains the oracle jar's, and it can be distributed in an easy wasy(at this moment))
I personally am not in favor of code that is Oracle-specific. As I mentioned before, I would like to see a more generic approach.
Oracle-specific classes would lead again to the horrible confusion of code we had for the support classes (in which case we likely have to make a class for every other version).
For your own home-brewn project (or the sandbox cvs) that's fine, but for the CVS HEAD I prefer more generic classes.
If you intend to make a database-with-views class that is generic and not Oracle-specific, than that may eb interesting. You should in hat acse likely extend it from: org.mmbase.storage.implemenation.database.DatabaseStorageManager
I'm aware of this, but would i run into problems, i'd prefer extending the class first so that the original 1.7 code can stay in it's place and the oracle modifications can be distributed in let's say a seperate class. A second step would be to change the class that i extended in such a way that the extending class will be no longer needed(say in an 1.7.1).
My goal will not be to create an with-views-database at first, but more to get Oracle going and get some feeling with these classes :D
<idea>
Maybe a specific class which is responsible for retrieving / storing large objects? Testcase could be to do this with the save-to-disk type of fieldhandling
This very small class could be in cvs
<idea>
4) Which resources do i have to modify or is it easier to place such files in the config directory for development?
You should make a resource oracle.xml that needs to be placed in org.mmbase.storage.implementation.database.resources
Placing it in classes/org/mmbase/storage/implementaion/database/resources/ does also work?
5) Is the make.flax.happy system property known to 1.7? (http://www.mail-archive.com/[EMAIL PROTECTED]/msg02734.html) This way i can use the jar from 1.7 rc)
No, but I personally won't mind if you add it.
Okay, and i assume that i can make this -small- change without an hack proposal :)
I shall take the following steps:
- adding <property name="storagemanagerfactory">oracle</property>
- adding class oracle that extends org.mmbase.storage.implementation.database.DatabaseStorageManagerFactory (without overriding anything)
- refer to oracle.xml by adding <property name="database">oracle</property> (shouldnt it read /org/mmbae/storage/implementation/database/oracle?)
- create an oracle.xml
