I wrote a series of advanced articles that addresses portability between brands
of EJB servers and versions of the EJB specification. It was published in two
parts on JavaWorld. The articles offer a strategy that eliminates dependencies
on vendors and spec versions, while allowing your beans to leverage vendor
specific mechanisms such as JNDI access, JDBC access, etc. The strategy is
transparent to your beans and easy to implement, so that you can use the same
exact beans in any EJB container and it will automatically and dynamically
work. The articles are titled "Forward compatibility" which was a poor choice
because the work is more relevant to cross brand portability than forward
compatibility for many people.
Here is the article link:
http://www.javaworld.com/javaworld/jw-12-1999/jw-12-ssj-ejb1.html
--
Author of Enterprise JavaBeans
Published by O'Reilly & Associates
EJB FAQ
http://www.jguru.com/faq/EJB
EJBNow.com
http://www.ejbnow.com
"Louth, William (Exchange)" wrote:
> you said "Of course, your code and designed can be influenced by the EJB
> server you choose"
>
> This is the issue I am facing now. For the last 6 months I have been using
> the Inprise Application Server and recently took on some more work for a
> client who intends to use Web Logic 5. I loved working with the IAS because
> I did not have to do much of the work,it did not get in the way of my code
> i.e. no vendor specific code, and performance was great. Now with this
> client I have found that to achieve any sort of performance I must use
> properitary code i.e. isModified(), to lookup the jndi I must use vendor
> specific code in my beans. Things i took for granted are just not there like
> proper serialization of home references and so on. Now that I see the state
> of play I realize that in fact IAS 4.0 is properitary in this circumstances
> since my 100% non-specific vendor code will only run in one container....
> IAS 4.0. I am currently looking more into Gemstone and WebSphere and have
> found similar things...
>
> note I refer to ejb1.1 containers.
>
> William
===========================================================================
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".
