We decided not to go with Hibernate as a persistence layer (to my disappointment) and to choose Scaffold Access/StorageBean approach instead.
Reading on this list I found an email by Ted Husted saying that he was (maybe still is?) not happy with the StorageBean deployment.
So my question is what should I do? I quite like the Scaffold data access layer and more importantly my DBA trusts it too.
I'd prefer to go with StorageBeanBase, but in this case I should make minor modifications to the Scaffold code (which I will give back to the community of course). The other option is the Access approach, but it is deprecated and it is not nice to compile an application with lots of warnings.
The modifications I have to introduce in the StorageBeanBase are:
replace all calls to
StatementUtils.executeUpdate(null,etc);
with:
StatementUtils.executeUpdate(getResource(),etc);
and add a static String resource=null; with getters and setters
that can be overriden by subclasses. This is motivated by tha fact that I have tables located in many different schemas/db hosts and want ConnectionAdaptor to return the right connection for that schema/db host.
Thank you, Umberto
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
