> My impression is that JBoss is similar to Websphere as it > runs Java programs in a shared environment (like CICS runs > traditional compiled code programs).
Conceptually correct. All three create a idealized environment for applications to consume basic services like session management, data marshalling, etc. > Then, a discussion of Oracle AS starts raising its head. > Is there are things Oracle AS can do, that JBoss (or > Websphere) doesn't? The major differences are in *what* additional pre-provided services are present in each one. If your application is written to expect features and functions that are present by default in one of the application servers, then it will fail if those services aren't there. Obvious, but that's the major problem here -- it's technically possible to deploy an app written for WAS to Jboss, for example, but you'd have to chase down all the WAS stuff that the app uses, extract it from WAS, deploy it to Jboss, do all the testing over, and then deal with any errors that happen because some weirdness in WAS isn't the same as it's done elsewhere. So, the usual reasons for not running in uncertified environments. It's possible, but do you need the hassle? > Why would you use one over the other, and in what situations? See above. From a programmer's point of view, it's all about testing and initial capability. The value of WAS and Oracle AS is that they provide lots of convenient and useful programming widgets that you don't have to write yourself. Jboss does too, but they're *different* from the WAS or Oracle AS widgets. Rule of thumb I use: if you are in a hurry, or need to support an application written for a specific toolkit, use WAS or Oracle AS. If you're writing your own stuff, use Jboss. It's more portable and allows to move things if they don't perform well. > Different departments, different directions. Fortunately, you can create virtual machines to accommodate...8-) > But if it makes sense, perhaps I can make this one full copy > license for Websphere (assuming a lower total cost). Don't even try. It's a huge amount of work, and the vendors probably won't support you. ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
