On 8/26/11 12:59 PM, Sebastian Sickelmann wrote: > Am 26.08.2011 08:32, schrieb Peter Jones: >> Public fields like RemoteException.detail, ill-advised as they may have >> been, cannot be removed (would break binary compatibility). > Sorry for that. It was more a reflex (remove "evil" public fields) than a > real problem with this. Breaking this would breaking binary compatibility but > can this be a real show-stopper for not fixing this?
Breaking binary compatibility is bad, bad, really, really bad. cheers, dalibor topic -- Oracle <http://www.oracle.com> Dalibor Topic | Java F/OSS Ambassador Phone: +494023646738 <tel:+494023646738> | Mobile: +491772664192 <tel:+491772664192> Oracle Java Platform Group ORACLE Deutschland B.V. & Co. KG | Nagelsweg 55 | 20097 Hamburg ORACLE Deutschland B.V. & Co. KG Hauptverwaltung: Riesstr. 25, D-80992 München Registergericht: Amtsgericht München, HRA 95603 Komplementärin: ORACLE Deutschland Verwaltung B.V. Hertogswetering 163/167, 3543 AS Utrecht, Niederlande Handelsregister der Handelskammer Midden-Niederlande, Nr. 30143697 Geschäftsführer: Jürgen Kunz, Marcel van de Molen, Alexander van der Ven Green Oracle <http://www.oracle.com/commitment> Oracle is committed to developing practices and products that help protect the environment
