A regular scheme at companies that I have seen is running the tests in
Jetty and the production system on tomcat.
So I guess having the test in Jetty is some kind of best practice even
when tomcat is used later.
Trying to remove spring is something that many frameworks try nowadays.
The problem is that this usually means that they
code their own di stack. I don´t think that makes life much easier in
the end. If we manage to replace spring by something very simple
that works in pure java that would be a good idea. I can not judge
though how feasible this is.
Regards
Christian
Am 28.09.2010 03:44, schrieb Benson Margulies:
I finally got around to reading the survey.
I have a few observations about the obvious. We love jetty. Our users
do not. Our users love tomcat. We do not. One might feel motivated to
shift tests to tomcat, or add tests with tomcat ... except that we
don't get a lot of JIRum on plain tomcat.
The survey, on the other hand, reiterates the high pain level
associated with the big app servers that make it hard to get the
classpath right for CXF. I have no idea if we can do anything except
write more documentation.
More documentation would certainly be appreciated.
It looks like our close and personal relationship with Spring
continues to really inconvenience very few and serve the majority. I
wonder if we would want to invest energy in merely designing some
scheme to make Spring more removable to assist some volunteer in
working on it?
There are some WS-*'s that would make an impression.
Java-first issues sure attract the vocal if not the numerous.
--
----
http://www.liquid-reality.de
