I thought i was using the latest version as I'd only installed it last week, but it turns out I'm using 1.5.0.
I guess that is where the problem stems from as I assume that the sample code I'm running through is 1.6.0 specific, but the cartridge is 1.5.0. The reason I say this is because the workflow.oaw does contain the entry hibernate.properties.file = 'hibernateCartridge.properties' Thanks for clarifying. I will download/install the latest version. I have to say I am quite impressed by what I have seen of oaw in general and the hibernate cartridge. I realise that this is probably more to do with the inner workings of hibernate or the model which is being used in the sample, than the cartridge itself, but do you have any thoughts or good examples of how to manage the saving of complex models into the database. For example I wrote a simple test script which instantiated and saved a book. This failed because of the not-null relationship with library. So I thought ok, if I create a library and add the book to it, when I save the library the book will be saved as well. It wasn't of course. I assume it is possible to model relationships such that this kind of save happens automatically, but I'm not sure whether in a real system that would be too restrictive. Do you have any thoughts or guidance which would help ? Thanks again -- View this message in context: http://www.nabble.com/Overriding-db-driver-settings-in-workflow-tp17675333s17564p17687580.html Sent from the Fornax-Platform mailing list archive at Nabble.com. ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ Fornax-developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fornax-developer
