Team,
this is a demo on factoring out reading & writing of parameters. As I
started to write about it, a number of sensible changes came to my
mind. I will write in more depth about it when they are done.
For those that still like to have a peek at it, these changes are
a) Rename KeyAttributeHelper to AutoIncrementHelper and don't
inherit from AccessHelper.
b) determine if AutoIncrementHelper is needed by an additional
attribute in the database descriptor rather than default to
it.
c) Then, AccessHelper can vanish, leaving just AttributeHelper
In short, what is is?
I'd like to put parameter reading & writing into components, so that
high level components can be independant from where the parameters are
stored.
In addition I wanted to split the handling of autoincrement columns in
RDBMSs out of the database actions. While doing so, I hope to have
added some features to them like table-sets and more advanced handling
of actions that target multiple rows.
There's a sample in scratchpad/webapp/mount/mod-db. Move that mod-db
directory to cocoon/mount/mod-db and point your browser to
http://localhost:8080/cocoon/mount/mod-db/user-list
In the mid term I'd like those components be declared in sitemap.xmap
alongside all other other components. The component handling in
ModularDatabaseAction is clumsy, not 100% compliant with "Developing
with Avalon" and I messed up contextualization. But then when sitemap
does this for me I would have to go through it anyway, remove most of
it and clean up the rest :-)
Stay tuned. I will be back with a more detailed RT on this when a - c
are done.
Chris.
--
C h r i s t i a n H a u l
[EMAIL PROTECTED]
fingerprint: 99B0 1D9D 7919 644A 4837 7D73 FEF9 6856 335A 9E08
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
