Tom,
We recently completed a brief paper titled "Theory and Practice of
Enterprise JavaBean Portability". The paper does not try to make a
comprehensive list of portability problems, but does present sources of
portability problems in EJB and illustrates them with some real examples.
These portability examples were found by using a model problem (or test
application) on different EJB servers.
This paper is not currently posted on the Web, but we are happy to make it
available to you and anyone else who is interested. If you are interested
please send me an email at [EMAIL PROTECTED]
John Robert
> -----Original Message-----
> From: A mailing list for Enterprise JavaBeans development
> [mailto:[EMAIL PROTECTED]]On Behalf Of Tom Valesky
> Sent: Friday, May 07, 1999 9:06 AM
> To: [EMAIL PROTECTED]
> Subject: EJB portability in real life
>
>
> One of my early concerns about the lack of a reference implementation for
> EJB was that it would result in divergent implementations, and that
> portability would be difficult or impossible to pull off. It's later now,
> and there are a few more implementations out there. I'm interested in
> hearing from folks that are developing shrink-wrapped EJBs (or any
> EJB solution that has to be runnable in more than one container) -- what
> have your experiences been with cross-container portability? Is it
> working out to be a non-issue? Is it hopeless? Or somewhere in between?
> ==================================================================
> =========
> Tom Valesky -- [EMAIL PROTECTED]
> http://www.patriot.net/users/tvalesky
>
===========================================================================
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".
