Hello there,
Resin is a servlet container that includes also an
EJB container, so everything fits in quite nicely and if you are going to put both pieces in the same machine, local calls are also very performant, as Tomcat bundled with JBoss I guess. I found it easier to install and to manage, but anyway everybody has their own tools and as long as it works.... ;).
The problem with EJB was that porting things was not very easy, so we moved away from it and we are using now Hibernate and a basic servlet container. Still Resin as it is quite good also alone. But I have some of my apps in a web provider that uses Tomcat and they also have no problems... well, they do
, but that's because it is a shared host with many other people and they bust the JVM every now and then, hehehe :roll:
And yes, I'm also a friend of the KISS principle, much more important to follow when traffic raises as the less things that can go wrong, the better. I don't really like putting layers over layers of software just for the sake of it, as you loose a bit of control with every layer you add.
We also use the servlet controller approach with the presentation separated from the business logic, even though we use XSL for the view and Hibernate and session POJOs for the logic. The framework has been working nicely since 1999, it started with different technologies for the logic of course, so we have it quite debugged ;).
I'm glad to hear the optimistic approach is working fine. Unfortunately for me my users would kill me if this approach failed and a message was assigned to some other user, for example, so I had to opt for the conservative approach (foreign keys + synchronization). Well, I always do so that was not a problem :P.
Nice talking to you and again, glad to hear the problem was solved. Lord knows that kind of problems can turn your hair gray quite quickly ;)
[originally posted on jforum.net by GreenEyed]
