This page (revision-5) was last changed on 23-Apr-2022 17:05 by Harry Metske

This page was created on 23-Apr-2022 17:06 by Harry Metske

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
5 23-Apr-2022 17:05 3 KB Harry Metske to previous
4 23-Apr-2022 17:06 3 KB Harry Metske to previous | to last
3 23-Apr-2022 17:06 3 KB Harry Metske to previous | to last
2 23-Apr-2022 17:06 1 KB Harry Metske to previous | to last
1 23-Apr-2022 17:06 1 KB Harry Metske to last

Page References

Incoming links Outgoing links
Application Servers...nobody
Application Servers

Version management

Difference between version and

At line 37 added 27 lines
{{{
jta alternatives
Posted by: James Law on December 13, 2007 in response to Message #243691
I wonder what the future of the appserver is, given the fact spring + jpa (hibernate) gives one nearly everything
the appserver was supposed to provide, with a lot less complexity, and easier testability.
Where I work websphere is nothing more than an expensive connection pool... (which c3po probably does better :) )
Time Passx-
check out atomikos if you need XA without the appserver.
}}}
{{{
Believe it or not, but large financial organizations are actually moving away from Websphere towards Jetty
because they are more cost-effective that way.
It is do to with turnaround times, ease of testing and the transparency of the application environment.
How many months before Websphere became JDK5 compliant?
So yes, CTOs actually "get it". At least some of them do.
My personal opinion is that the ones clinging to a vendor to prop up their development are bound to fail.
There is no money in application servers any more, and the support you get is going to reflect that.
Geir
}}}
{{{
WebSphere is a real pain to work with.
}}}
This page (revision-5) was last changed on 23-Apr-2022 17:05 by Harry MetskeTop