Rickard �berg wrote:
> Hey
>
> Evan Ireland wrote:
> > So this part is clear. However what seems to be underspecified is
> > how these collections should be marshalled over the wire for
> > interoperability, in the case where 'find...' method returns a
> > collection. Perhaps it is assumed that the 'find...' method on the
> > Home interface will return an instance of java.util.Enumeration
> > that implements java.io.Serializable. However EJBObjects are
> > not required to implement java.io.Serializable. So how are we
> > supposed to implement a serializable enumeration of non-serializable
> > objects, in such a way as to allow the promised interoperability
> > over IIOP? I am not clear on this. Perhaps someone could enlighten
> > me.
>
> EJBObject implements Remote -> enumerations of stubs are returned.
So how does that help? I am not saying that I can't see how
to marshal collections of object references over the wire,
I am saying that classes that implement javax.ejb.EJBObject
are not required to be serializable, so it is not clear how
interoperability (say with another EJB vendor's client or a
CORBA/IIOP client) is supposed to work.
In our case, we pass a sequence of CORBA object references
over the wire. The server skeletons and client stubs do conversions
to and from java collection types. So I know how to achieve the
desired result in a single-vendor environment, but how to do it
while still providing interoperability remains a mystery to me.
Who knows if Moscone is going to address this?
Or perhaps this problem is already solved, and someone could
enlighten me.
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
