Of the two, I'd say go with weblogic.
You might also look at iPlanet, the newest Netscape Application Server,
instead of either of those though.
I think that the solution model is the most important piece of the puzzle,
and IMHO, the approach to use is:
JSP's
JSP's useBean tag (simple JavaBeans now have a client side cache
of the server-side EJBs)
Servlet Mapping (you now have lots of little servers, i.e.,
servlets, that deal with specific EJB's)
Check out how the products handle this MVC type of approach.
The IDE (if you use one) should emit code that is portable across app
servers so you're not locked in to a single vendor. Search out areas of
your code that are vendor specific and write your own wrapper classes.
Scott Durrant
Human Genetics
University of Utah
[EMAIL PROTECTED]
On Fri, 16 Jun 2000, Fabrice Antoine wrote:
> Hello,
>
> I have to make a choice between WebSphere 3.0 and WebLogic 5.1 as
> general application server for my business ! Is there anyone that
> can help me making this choice ?
>
> Thanks
>
> Fabrice
>
> ===========================================================================
> 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".
>
>
===========================================================================
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".
