Hello,
we've written a small tool which imports data into the MMBase backend
using the RMMCI interface. The last couple of weeks I've noticed that
while committing some data into the backend, exceptions are raised in
various classes of the bridge-package. This is especially true when
calling the commit()-method on org.mmbase.bridge.Node.
When browsing the source of the Node-interface, I was more than
surprised to find out that some of the most crucial methods, such as
commit() and delete(), don't expicitly throw any exceptions. You must
assume that any class calling these methods is *very* much interested in
anything going wrong while storing data into the backend. In our case,
the tool is doing some transactionallly based stuff which must
atomically commit as a whole. Currently, our tool doesn't have any clue
when things blow up on the MMBase-side.
A good fix for this is to let these methods throw a custom exception
which wraps any exception which is thrown in the underlying code. What
is your opionion on this?
Regards,
Dirk Kemper
--
ing. D. Kemper - Softwareontwikkelaar
First8 - http://www.first8.nl
Email: [EMAIL PROTECTED]
Mobile: +31 (0)6 152 175 94 / Phone: +31 (0)24 348 35 70
_______________________________________________
Developers mailing list
[email protected]
http://lists.mmbase.org/mailman/listinfo/developers
