|I dont have Oracle so I dont know these Problems ;-)))
|
|No, I didnt know that. The Problem was that the wired query in case of
|table does not exist caused a SQL error, which killed my transaction
|(marked rollback).
|
|Two possible ways to solve it:
|1. bring the transaction stuff into the jaws code and use two
|transactions for this operation (reuse the old code)
ah yes.... :)
well we should distinguish between "normal exceptions" (as in table exists)
and real excpetions... I assume you mean that the transaction rollback
decision can be overwritten in jaws, but I believe that some of the
container layer need to let this guy go through.
The more I think about it the more we need to type the exceptions (normal,
operation, system, application)...
|2. Use a general way to obtain the databases metadata and make a
|decission based on that. The j2ee spec (v1.3 section 9.2.2.3) says that
|a compatible driver has to implement that, so I thought Oracle does it
|in an professional way.
|
LOL!
marc
|Any ideas appreciated.
|
|regards
|Daniel
|
|
|
