[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Collection-problem [Re: opp bug?]
On Sunday, December 10, 2000, at 04:55 PM, Falko Braeutigam wrote:
> Guys, serializing just an inner class (without the outer one) never works in
> Java. We have to provide a solution for mentioned collection problem but in
> general the problems of serializing inner classes are not caused by ozone.
> The semantics of inner classes is different from C++ where this might work.
>
> Also, I cannot state in the docs that iterators not work in ozone. This
> wouldn't be true. It _is_ true that there is an architectural difference
> between ordinary Java object and database objects, which causes problems when
> returning ordinary iterators from database objects. But I _did_ try to explain
> this in the docu already. But the developer itself is never a good docu writer.
> I asked for help with this very often...
It doesn't matter if it's a Java or ozone limitation, developers can't use it.
You can't return the following things from a database object:
* java.util.Enumeration, java.util.Iterator
* java.util.Collection
* Everything else that is not serializable
Simple, clean, understandable.
btw there is also no documentation or example on how to create a non-empty constructor database object.
For example, the correct Java signature for a single String would be "(Ljava/lang/String;)", but ozone only accepts "java.lang.String", I don't know how to supply a second parameter (an int for example).
andy
--
Description forthcoming.