Re: mlw, perhaps you should learn about J2EE before sticking your foot in your mouth?
xx <xxx@yyy.zzz> wrote in message news:<3F46443E. 9030309@yyy.zzz >...[color=blue]
> Actually, web applications and business logic applications are *very*
> simple indeed. It is the infrastructure behind the J2EE environments is
> very heavy duty and complex. Clustered SQL databases (obviously not
> written in Java), caching systems, and so on.
>
> The front end, load balanced, redundent, J2EE environments doing the
> business logic are very simple.[/color]
You sir, are a fool who obviously has no idea what you're talking
about. That "infrastruc ture in the backend" which you admit is very
heavy duty and complex is partly of J2EE. I would suggest actually
learning about Java before making an ass of yourself in public.
J2EE is a specification for a comprehensive middleware system, not
simply a single application or set of applications running on a single
web application server on the "front end". J2EE is somewhat inherently
complex because it was meant to be distributed in nature (anyone who
has ever tried to master EJBs can testify to this). As such it has
multiple components, most of which are not on the "front-end", like
JMS for messaging, JNDI for accessing naming services, RMI-IIOP for
communication between the distributed objects, etc, etc. The less
complex apps use the more well-known components, such as servlets and
JSP pages (which are nearer the "front-end", and which is what most
people - including ignorant know-it-alls like you - typically
associate with "J2EE").
For example, we have implemented large scale n-tier clusters of J2EE
application servers that rely on clustered EJBs to provide very high
reliability and availability for users (a financial institution).
This is not something you put together in one single afternoon, nor
can it be in any way considered "simple". There is some price (in the
form of complexity) to be paid for enabling such high
reliability,sca lability, and availability.
And do you even know what "clustered" sql databases are?
xx <xxx@yyy.zzz> wrote in message news:<3F46443E. 9030309@yyy.zzz >...[color=blue]
> Actually, web applications and business logic applications are *very*
> simple indeed. It is the infrastructure behind the J2EE environments is
> very heavy duty and complex. Clustered SQL databases (obviously not
> written in Java), caching systems, and so on.
>
> The front end, load balanced, redundent, J2EE environments doing the
> business logic are very simple.[/color]
You sir, are a fool who obviously has no idea what you're talking
about. That "infrastruc ture in the backend" which you admit is very
heavy duty and complex is partly of J2EE. I would suggest actually
learning about Java before making an ass of yourself in public.
J2EE is a specification for a comprehensive middleware system, not
simply a single application or set of applications running on a single
web application server on the "front end". J2EE is somewhat inherently
complex because it was meant to be distributed in nature (anyone who
has ever tried to master EJBs can testify to this). As such it has
multiple components, most of which are not on the "front-end", like
JMS for messaging, JNDI for accessing naming services, RMI-IIOP for
communication between the distributed objects, etc, etc. The less
complex apps use the more well-known components, such as servlets and
JSP pages (which are nearer the "front-end", and which is what most
people - including ignorant know-it-alls like you - typically
associate with "J2EE").
For example, we have implemented large scale n-tier clusters of J2EE
application servers that rely on clustered EJBs to provide very high
reliability and availability for users (a financial institution).
This is not something you put together in one single afternoon, nor
can it be in any way considered "simple". There is some price (in the
form of complexity) to be paid for enabling such high
reliability,sca lability, and availability.
And do you even know what "clustered" sql databases are?
Comment