Hello,
There are a lot of question to ask before somebody answers that. There are
pros and cons of each.
Ideally(JEE) one would develop on a reference app(Tomcat, JONas) then deploy to
the App erver container one needs.
The bigger the app the less this is true, security, failover, clustering etc.
will require tweeking of deployment descriptors. All of these of course are
skillset costs also.
I will start the flame war with this, IBM has just released their new community
version of Websphere based on Apache Geronimo(theirs is called Gluecode), and
if you do actually deploy to external customers, those customers can purchase
support from IBM. Very important if you are a software company, not as
important if you are an internal dept. supporting your own. Try that with
Tomcat or JBoss.
Apache Geronimo will be a a JBoss killer and will soon become the new reference
app of choice. Web containers, EJB containers Message queues, etc. will just
be services that one can add to a Geronimo container.
Later,
--
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN">
<html>
<head>
<meta http-equiv="Content-Type" Content="text/html; charset=iso-8859-1">
</head>
<body><a href="http://jakarta.apache.org/tapestry/";><img
src="http://howardlewisship.com/images/no-struts.png"; width="200" height="154"
alt="Friends Don't Let Friends Code Struts" border="0"/></a>
</body>
</html>
---- twcrone@xxxxxxxxxxxxx wrote:
> Any opinions about Sun ONE as a J2EE server compared to WebSphere and BEA
> WebLogic?
>
> Thanks,
>
> --
> twcrone@xxxxxxxxxxxxx
> 859-278-9634
>
> ---------
> You may unsubscribe from this mailing list
> by sending a blank email addressed to:
> users-unsubscribe@xxxxxxxxxx
>
> --
> Find additional help by sending a blank email
> addressed to:
> users-help@xxxxxxxxxx
>
|
![http://howardlewisship.com/images/no-struts.png"](http://howardlewisship.com/images/no-struts.png"){kind=link}