Expected app behaviour on encountering a changed IDL type on unchanged typecode within the >>=-operator

Hi altogether.

I have a (low-priority) question about the >>= -operator just to get things clear in my mind: Suppose I have a structure or sequence of anything with a known typecode which reaches my app within an Any and I try to extract it via the forementioned operator. If I would try to extract anything else with a different typecode this operator simply would return false; if the typecode fits and the extraction from the Any could be done it returns true and everything is fine.

Now suppose the definition of the contained data within the Any was changed (via IDL) but my app was compiled with an old IDL information. Clearly in this case we have broken the rules concerning this interface. But how will my app behave now ? How is my app suggested to cope with this kind of mistake ?

Initially I supposed my app to throw some kind of MARSHAL-exception, which indeed it does. But I found that during the subsequent stack-unwinding it causes a so-called >DAMAGE after normal block< which also causes other parts of the app to malfunction and run in GPFs. At the result of all this the app itself is no longer approachable and can only be killed.

Is this app-damaging expected to occurr in this case or are there any issues concerning (UN)MARSHAL-exceptions? 

(BTW: I used OB422 in "old-wstring-compatibility mode" under windows, whereby the data type is expected to have a (w)string component where another simple data type resides now).

Thanks for your comments in advance.

Greetings
Frank Gierschner
Development


REALTECH

REALTECH system consulting GmbH
Industriestraße 39c
69190 Walldorf
Germany

Tel.: +49.6227.837.306
Fax: +49.6227.837.291 / 9306
mailto:[email protected]
http://www.realtech.com

_______________________________________________
OB-Users Mailing List - [email protected]
http://mail.ooc.nf.ca/mailman/listinfo/ob-users
Visit our support FAQ before you send a message.
http://www.orbacus.com/faq/support.html