> >In this way you can have partially initialized objects that only pull in > >the pieces it thinks it needs... While this is a vendor-specific > >optimization, it is mapped into the weblogic deployment descriptor, so it > >does not make your code any less portable (although you won't have these > >optimizations on another product, unless they have something similar). > > > > No offense, but to me "vendor-specific optimization" is euphemism for > non-portability. Another vendor's implementation simply won't match > weblogic's. Unless it gets in the spec (and all vendors agree to > implement), it's not standard. Therein lies my concern about the emerging > standard.
This is not always a portability issue. There are many instances where vendor-specific optimization is "hidden behind" the standard's API. It is also possible to design your code such that vendor-specific optimizations can be hidden behind your own APIs. tim. =========================================================================== 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".
