I just wanted to initiate a discussion about a change.
We have development environment working with Jetty 7 which provides
better productivity.
We agree on that we should support container which is being used for
development.
This means, may be next release Mifos support using Jetty 7 instead of
asking to upgrade to Tomcat 7.
if you have comments/suggestion etc, then this thread is the place.
Cheers,
Udai
------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
Udai
There appears to be no technical reason why this shouldn't happen. If
anything, Jetty appears to be a better choice than Tomcat.
I recommend that two things are considered:
- The version used in a production system should be the one delivered with
the LTS version of Ubuntu, not necessarily the newest and shiniest version.
- Take advantage of the change to make Mifos secure by default by making
HTTPS the default, at least. I have been concerned for some time that
personal and financial information is sent over the Intarwebs unprotected.
And that the recommendation is to turn off Tomcat security.
Regards
Graeme
The reason for upgrading the container to Tomcat 7 or Jetty 7 is
Servlet 3.0 specs on which Michael has created a more productive
development environment, and there are possibility of getting lower
level modularity using Servlet 3.0 specs.
The next release (possible LTS) of Ubuntu (11.04 Natty) is still behind.
http://packages.ubuntu.com/ca/natty/jetty
So, we might not be able get in sync with Ubuntu until they get to
Jetty 7. But, this is definitely a good point to keep in mind.
Thanks,
Udai
Ryan,
If we moved to Jetty, We would recommend using Jetty to Mifos users,
and to have better support they would have to switch to Jetty.
AFAIK Mifos does not have any tomcat specific settings so Mifos is
insulated from container specific things. It should not be difficult
to move to Jetty in production environment, and hopefully we will
document the settings required (if any).
In theory, one should be able to run Mifos on Jetty currently when we
are supporting Tomcat, and it should be same for Tomcat if we will
start supporting Jetty.
The important point is that we will upgrade to either Tomcat 7 or
Jetty 7 in upcoming release. Because if we will be moving to Jetty for
development environment we would like to recommend the same container
for production.
This is not Tomcat-specific, the code and config follows the Java
servlet spec.
> http://mifosforge.jira.com/wiki/display/MIFOS/Tomcat+Compression
This is Tomcat-specific. But Jetty can do this:
http://docs.codehaus.org/display/JETTY/GZIP+Compression
> http://mifosforge.jira.com/wiki/display/MIFOS/Maximising+Browser+Caching
This is not Tomcat-specific, for the same reasons as the transaction
monitor.
Note: the transaction monitor and cache settings servlet filters are in
head:
application/src/main/java/org/mifos/servlet/filters/MifosAccessLogFilter.java
application/src/main/java/org/mifos/servlet/filters/MifosResponseHeaderFilter.java