T.R | Title | User | Personal Name | Date | Lines |
---|
1388.1 | | LEMAN::DONALDSON | Froggisattva! Froggisattva! | Mon Mar 24 1997 05:52 | 12 |
| Tomas,
I'd be interested in the answer to your question too. Just
an indication of intent. But in any case...
...although OBB doesn't do it, you can. Just trap the ev error
after each OBB call and then throw the exception. Somewhere
else you can catch it. If you're doing this on the server then
you should at the outer limit of you're program (in the method
or its associate) 'raise' whatever exception is necessary.
John D.
|
1388.2 | At least not in the Bryce timeframe, don't know of long-term plans | VAXCPU::michaud | Jeff Michaud - ObjectBroker | Mon Mar 24 1997 23:53 | 9 |
| I don't believe there are any plans for it. The problem I
recall is that not all our supported platforms support
exceptions. And on some of those that do, there was another
subset of platforms that didn't support a shared library that
was loaded on the fly to throw exceptions.
Nina or Peter I believe did the investigation was we were looking
at supporting C++ exceptions in the IIOP bindings/ORB, and can
give a better answer as my knowlege is all 2nd hand.
|