Hallo Robert,
RK did you file this as a bug report in bugzilla? I didn't find it there. I'll
RK file it now (we just ran into it and it's a nasty one to find). if you
RK already have please contact me so I can remove it.
RK robert
Vidur,
This looks in same ways similar to the problem that I
Hi guys,
sorry for this mail in german, wrong recipient!
It should go to Robert directly. (Hi robert!)
for all how are not able to read german, I added a english translation
as seperate mail..;)
Greetings, /Thomas
TH Ein weiteres hartes Problem, das hiermit zusammenhaengt, ist,
TH dass ab der
Unfortunately it is not always clear whether an object referred to by its
interface type is serializable. I am in the middle of fixing a load of
beans that returned Iterators, which worked fine on Orion 1.3.8. Of
course Iterator is an interface, and I discovered when I upgrade to Orion
1.4.3
did you file this as a bug report in bugzilla? I didn't find it there. I'll
file it now (we just ran into it and it's a nasty one to find). if you
already have please contact me so I can remove it.
robert
Vidur,
This looks in same ways similar to the problem that I reported a couple of
Vidur,
This looks in same ways similar to the problem that I reported a couple of
days ago.
That is, Orion 1.3.8 allowed non-serializable objects to be returned to
the client if running in the same JVM (which should of course not be
allowed).
1.4.3 on the other hand behaves differently -
is needed
My 2c,
JP
-Original Message-
From: Thomas Munro [mailto:[EMAIL PROTECTED]]
Sent: Viernes, 10 de Noviembre de 2000 10:56
To: Orion-Interest
Cc: Orion-Interest
Subject: Re: 1.4.4 OR Collection classes
Vidur,
This looks in same ways similar to the problem that I reported a couple
Hello,
Earlier today I had reported a problem with the Map class. There is
also a problem with the List class. When the CMP entity is retrieved
and the CMP List field is empty, it is returned to the client as null.
Both the Map and the List work fine under 1.3.8.
Vidur
