Slashdot Mirror

← Back to Stories (view on slashdot.org)

Apache Tomcat 4.0 Final Released

Posted by Hemos on from the meow-meow-roar dept.

A reader writes "The latest version of the Apache Java Servlet engine has been released. 'The 4.0 release implements the Servlet 2.3 and JSP 1.2 specifications.' Read more at The Apache Group's Jakarta site."

3 of 288 comments (clear)

  1. Hehe by JediTrainer · · Score: 3, Insightful

    Anybody else appreciate the irony that 4.0 Final is released while 3.3 is still in beta?

    I've been using Tomcat 3.2 in production for the last 6 months or so and it's been a wonderful servlet container. I can't wait to try out 4 in our testing environment!

    --

    You can accomplish anything you set your mind to. The impossible just takes a little longer.
  2. Re:Tomcat As the Anti.NET? by Lethyos · · Score: 3, Insightful

    Because Java still consistently sucks ass, drags ass, and is still up the ass of an almost-ran Microsoft (aka "Sun")?

    Point by point here, how does Java suck? Java is a great language for all kinds of tasks. The extensive API already available for it is a big plus, and it is, for all intents and purposes, truly cross-platform.

    Java is not as slow as most people claim. Like any programming language, performance is dependent largely on the programmer. A lot of programmers with poor skills use Java because they can focus on their tasks instead of building the tools to do said task. Here's an article on /. with more details about this. Also, pay attention to this article before yoiu make further claims that Java performance is bad. And of course, you could try actually coding something using the language. :P

    Sun has done a lot of good for the OSS community. If you'll notice OpenOffice, and well, Java is a great piece of code for the Linux world. I'd say that Sun != Microsoft. Get a clue.

    --
    Why bother.
  3. sigh by mikemulvaney · · Score: 2, Insightful

    Yet another non-Java developer trashing JSP's.

    I'll agree with you -- for pounding out web pages, it is much easier to do it in perl or php. But if that's all you want, then even perl and php are overkill. Why not just write static HTML pages?

    JSP is useful when you need to talk to Java components to get real work done. If you are a web designer, then don't use it. But if you are working on a big project, then the web interface is probably the least important part of the whole thing. Java provides a much richer set of tools than perl or php for creating reusable business components, and JSP provides an easy way to stick a front end on top of that.

    JSP scales a lot better than PHP/perl for mulitple developers, too. It sounds like you are more of a web designer than a programmer. JSP might make you feel unconfortable, because you wouldn't get to program as much, but the lines of responsibility are more clearly drawn. The guys in charge of the business beans would make up tags for you to use, and you could work on making the screens look pretty in Dreamweaver.

    So what can you do with JSP that you can't do with PHP, Perl, ASP, etc? Talk to Java. That's what we want to do.

    If you want to talk to a perl module, then use mod_perl or HTML::Mason. If you have COM objects, then use ASP.

    JSP is just a front end! The decision has already been made, long ago, to go with Java for all of its obvious business programming advantages.

    -Mike