tags:

views:

55

answers:

4

I primarily use Tomcat and Glassfish for Java EE development at work, but was wondering if anyone knew of any small application servers like Cassini for ASP.NET that would make building and testing faster? I would still eventually deploy to one of our production tomcat/glassfish servers, but would prefer something that is simpler and quicker.

I am probably going to take jetty and geronimo for a spin, any others I should check out?

+2  A: 

jetty is good for testing, because it's very easy to start a jetty instance in your tests. if you're also concerned about faster development, then the choice of server is not the only factor.

there's also jonas and resin

Stefan De Boey
I will add these to my list to check out.
Casey
+2  A: 

You might want to check out JRebel which eliminates the need to do a redeploy on ~80% of the cases, making the development quicker.

Jeduan Cornejo
if you want to spend a lot of money of course
Stefan De Boey
that looks great, but I couldn't bring myself to spend money on it.
Casey
You get what you pay for :)
Jevgeni Kabanov
There's a 30 day test with no cost and you can get it for free if you are a contributor to an open source project
Jeduan Cornejo
+1  A: 

This may not answer your question directly, but you may want to consider alternative Framework/Server combinations.

Here are a few Java RAD stacks that I have used in the past and work very well when trying to achieve a rapid development -> build -> test loop:

Granted, these are not application servers in their own right, but each of them are frameworks/servers that can be used to achieve the results you are looking for. Roo and Play are both Java based, and Grails is Groovy based.

None of these solutions will work if you are looking for a plain container to deploy your application in to. These are more like all in one solutions.

Steve Levine
Good point. I have been wanting to do some Grails stuff for a while. Although, for right now, these solutions wouldn't work for me as I do need to deploy to a regular container at some point.
Casey
Both Roo and Grails produce AFAIK war files you can deploy on any regular containerPlay looks great for creating a RESTful-based application, and it is a strong competitor to Jersey on that regard, I'll keep an eye on it.
Jeduan Cornejo
+1  A: 

(...) but was wondering if anyone knew of any small application servers like Cassini for ASP.NET that would make building and testing faster?

You should have a look at this Short screencast on GlassFish v3 session redeployment that shows the session state preservation across redeployments in GlassFish v3. Combined with the "deploy-on-save" feature (vs build and redeploy) offered by the GFv3 IDE plugins for NetBeans or Eclipse, Java EE development is very productive (even if GlassFish is not the fastest to start but well, you don't have to start it that often).

I was a big fan of Jetty but I must say that I just love these two features and consider them as direct answers to your concerns.

Pascal Thivent
I will take a look at it but in my experience working a lot with V2 and a little with v3, it has to be restarted numerous times because of permgen issues. So, that would render any benefit useless in my opinion. But, I will give this a shot.
Casey
@Casey I don't have the same experience with GlassFish v3.
Pascal Thivent
@Jevgeni Kabanov Care to explain the downvote (it must be you since you left a comment in the same minute)? It's of course your right to downvote my answer but I don't think it deserves it (there is nothing wrong with it apart from the fact that I am not promoting **your** product) and you could at least have the decency to leave a comment (and to say you are biased).
Pascal Thivent
@PascalFair enough -- I think it's ridiculous that GlassFish guys are promoting a feature that every other container has had for years, including Jetty and Tomcat. The fact that they were missing session serialization between redeploys before is abhorrent, and the way they keep pounding it as if it's something groundbreaking is pure FUD. Jetty is an awesome container, from the ground up. I vote for it and against GFv3.
Jevgeni Kabanov
@Jevgeni 1. The Jetty plugin in Eclipse is far from perfect 2. Jetty 7 is currently an horrible mess 3. Tomcat, Jetty are not Java EE servers (as stated in the title of the question) 4. For Java EE development, GFv3 is great (and I have some practical experience in that field) 5. I'm not even mentioning the case of Java EE 6.
Pascal Thivent
Considering the original poster mentioned Tomcat I don't think there's any reason to exclude Jetty. As for the rest, you have your opinion, I have mine.
Jevgeni Kabanov