It's a good question.
If you ask me (you did :) EJB is particularly well suited for "application"
that run on the web. I.e. not necessarily "web applications" with all HTML
front end but "distributed applications" with the whole distributed objects
shebang.
j2ee includes the servlet/jsp thingy (and all the derivative publishing
frameworks out there, coocoon, xmlc, bla bla bla) and that means they become
"web applications".
I agree the terminology can be missleading
marc
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of
> [EMAIL PROTECTED]
> Sent: Monday, August 07, 2000 12:38 PM
> To: jBoss Developer
> Subject: Re: [jBoss-Dev] Some questions
>
>
> Yes, I am WAY behind on reading my mail. ;-P
>
> Question: Can someone enlighten me on whether J2EE is useful
> outside of web applications? It seems that many companies are
> moving to Java on their webserver (and rightly so, IMHO), but
> what about the minority of us developing standalone Java
> applications? JMS, of course, could be useful, but are there any
> other J2EE technologies that could be applied to standalone
> apps? Or is J2EE intended to be a framework for developing
> web apps? (If so, I hate the name...)
>
> TIA,
> Russ
>
>
>
>
