GenericQueryManagers require a int type setter and getter in Bean.
Speaking of which ... to revisit an old topic ...
I need Rife's transaction support, which AFAICT is not available at
all to GQM's.
RIFE transaction support is available to everything DB-related. By
just called inTransaction on a DbQueryManager and providing a
TransactionUser, all the DB code that follows (also the GQM and CMF
code) will be wrapped in that transaction. It even supports nested
structures so that only only transaction will be used if there's
already one active.
More info here:
http://rifers.org/wiki/display/RIFE/Chainable+transactions
(I originally used GQM's in order to get the unique sequential ID's,
but I no longer need them, so it's time to make the switch.)
Make the switch to what? Regular query managers? Why?
Does the changeover start by
1) replacing calls to
GenericQueryManagerFactory.getInstance
(Datasource datasource, Class<BeanType> beanClass, String tableName)
with
new DbQueryManager(Datasource datasource)
2) and using the << .into("tablename")" >> method
3) and making sure that each table has a column with the "unique"
Constraint
--
Geert Bevin Uwyn bvba
"Use what you need" Avenue de Scailmont 34
http://www.uwyn.com 7170 Manage, Belgium
gbevin[remove] at uwyn dot com Tel +32 64 84 80 03
PGP Fingerprint : 4E21 6399 CD9E A384 6619 719A C8F4 D40D 309F D6A9
Public PGP key : available at servers pgp.mit.edu, wwwkeys.pgp.net
_______________________________________________
Rife-users mailing list
[email protected]
http://lists.uwyn.com/mailman/listinfo/rife-users
