At 01:05 PM 5/7/99 +0000, you wrote:
>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?
Somewhere in between. I started this project using Weblogic's Tengah, and
now use a combination of EJB servers for development and production. Ran
into portability issues in three major areas
- Deployment descriptors - everyone has a different way of coding
deployment descriptors. Hopefully, spec 1.1's reliance on XML for
deployment descriptors will ease this
- Client login/authentication
- Initial bootstapping, location of EJB beans in JNDI. However, this may
be more of an Oracle 8i issue due to their use of session IIOP and how you
access their JNDI.
Perry Hoekstra - [EMAIL PROTECTED]
-------------------------------------------------
All that is Microsoft does not glitter,
Not all those who wander are lost;
The old AT&T Unix that is strong does not wither,
Deep roots are not reached by frost.
>From the ashes of Spec1170 a fire shall be woken,
A light from the shadows shall spring;
Renewed shall be the Unix OS that was broken,
Linux shall be king.
===========================================================================
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".
