Well, since it is not mandatory in EJB 2.0, it's really not too late. :-) The problem is, from my point of view, I could imagine that in a next spec, let's say EJB 3.0, this could become mandatory. I suppose this because if they would not intend to act this way, they would not tell in detail how to do this, since it would be hard to find a vendor that implements this just as good will. From my point of view, the "not mandatory" means here: "not mandatory NOW".
We should keep this in mind, I could imagine that interoperability becomes a central point in the next version of the spec, and it's good to know what's coming up before it's there. -------- Original Message -------- Subject: Re: Container-Interoperability (04-Okt-2001 13:34) From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] > I took a look to the chapter 19 from the EJB 2.0 specs. Interoperability > becomes > a true concern (it's not too late ;) ). > It seems that interoperability is not mandatory. But if the vendor wants to > be > interoperable it has to implement what's described in this chapter. > > Just to sum up: > - RMI/IIOP 1.2 is required. > - Serializable EJB utility objects (Handles, Iterator, Collection) must > use > HandleDelegate class (spi). > - Transaction context must conform to the CosTransaction:: > PropagationContext > - Transactions are coordinated at the client side TransactionManager. > (interesting for some clustering functions!) > - Naming must be COSNaming compliant. > - Security is built on top IIOP over SSL. > - Security principal is derived from the connection identity. > > Regis > > On 04 Oct 2001 09:41:44 UT > [EMAIL PROTECTED] wrote: > > I just found this document describing the interoperability between EJB 2.0 > > containers. Seems that EJB 2.0 / J2EE 1.3 makes it mandatory for containers > > that the protocol of the interposition classes is standardized, basing on > > IIOP: > > > > http://java.sun.com/j2ee/sdk_1.3/techdocs/release/ReleaseNotes.html#15815 > > > > ---- > > To unsubscribe, send email to [EMAIL PROTECTED] and > > include in the body of the message "unsubscribe jonas-users". > > For general help, send email to [EMAIL PROTECTED] and > > include in the body of the message "help". > > ---- > To unsubscribe, send email to [EMAIL PROTECTED] and > include in the body of the message "unsubscribe jonas-users". > For general help, send email to [EMAIL PROTECTED] and > include in the body of the message "help". > > To: [EMAIL PROTECTED] > [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] ---- To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "unsubscribe jonas-users". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
