|
|
Posted by Erwin Moller on 12/17/92 11:54
Vincent Delporte wrote:
> On Mon, 31 Jul 2006 17:43:13 +0200, Erwin Moller
> <since_humans_read_this_I_am_spammed_too_much@spamyourself.com> wrote:
>>For example: It is easy to let JSP-pages communicate with each other. In
>>PHP you'll need sessions or database, while J2EE can share (references to)
>>objects that are in-process/memory.
>
> Is it because of JSP, or because J2EE uses an application server? In
> that case, it's not JSP itself that explains, but the fact that PHP
> users don't (can't?) use an application server and rely on code pages
> instead. Am I wrong?
Hi Vincent,
J2EE is just a container in which Sun putted a lot of stuff, JSP/Servlets
just being one of them.
But JSP/Servlets DO expect an ApplicationContext and more to run anyway.
So I think the question if it is JSPs behaviour or it comes from the
applicationserver is not relevant. Servlets are designed to run in that
environment.
You just cannot run a servlet outside of that context.
It wouldn't even compile.
>
>>I don't know if J2EE will die, last year a few headhunters tried to get me
>>back into J2EE (which I refused, alltough it pays well).
>>That means that (at least in Europe) not enough people have J2EE skills
>>these days.
>
> Maybe they're moving to .Net.
I am afraid many do. :-/
But lets face the facts: M$ did a real good stealingjob (again) when
'inventing' their dotnet stuff.
Regards,
Erwin Moller
Navigation:
[Reply to this message]
|