What's new in Servlet 3.1? - Java EE 7 moving forward

https://blogs.oracle.com/arungupta/entry/what_s_new_in_servlet

by Garbage • 14 years ago

30 26 14 years ago

blogs.oracle.com

lampe• 14 years ago

I worked on a bigger JavaEE project with serverlets and all the other things...

after doeing things like: "someurl".toURI.toURL; to get a valid url and some other stuff that i really dont wanne start with...

I just refuse do code something for the web with Java and Servlets and RMI or Beans or Java Technologie X...

now i code in Javascript and ruby and iam so much happier as a developer :)

eranation• 14 years ago

I like Play framework as an statically typed alternative, doesn't have most of the things we like less about Java, feels like RoR / Django, but is still statically typed (and supports Scala which I think is much more fun than Java once you get passed the "Scala is complicated" myth)

eropple2• 14 years ago

Scala may be "more fun", but, personally, I still have reservations about it being used in-the-large and I think calling the observation that Scala is, yes, complicated a "myth" is unnecessarily dismissive. You may not find it as such, but the language's kitchen-sink approach to features does have its drawbacks; I find that part of it manageable but that doesn't mean it's not complicated, it means I can deal with it.

I'm more concerned about legibility of Scala code. I've been using Scala in anger for about two years now and I still find myself writing what seems to me to be idiomatic Scala code that I have a lot of trouble reading three days later. (Play makes this worse, I find, because of the way that objects are exposed into your scope--these objects are super handy, but tracking down where they're coming from and what they're doing produces nontrivial cognitive load.)

meaty• 14 years ago

To be honest, it scales up pretty well lines of code-wise. You just need to break it up into smaller apps.

sgt3• 14 years ago

I'm afraid to say this, but you sound exactly like someone with very little experience when it comes to large scale enterprise systems (your "serverlets" sums it up).

Java EE is extremely powerful if you can wield its power, and obviously a good understanding of object oriented programming and design patterns is critical in order to make systems that are rock stable, safe (container managed transactions comes to mind) and scalability.

I think you'll see my point once you start working on larger problems. It's not random that many really big enterprise projects (such as banking software) are based around Java EE, and not Ruby on Rails.

Note that I am not trying to be overly negative - it's just that I see this kind of argument all the time, usually from people with no real enterprise experience.

espinchi2• 14 years ago

I tend to think everyone is writing web Python or Ruby servers backed with some NoSQL database, that expose a RESTful interface to a fancy HTML5 client that leverages some cool JS framework.

At my workplace, we have this debate going on about what to do with our GUIs (that are used only internally). The alternatives are 1) keep them in Java Swing, 2) progressively rewrite components in Java FX 2, 3) go web. These are operational GUIs that talk RMI with our Java servers (which we won't rewrite).

What's your take on this decision? Do you think it is shortsighted to stay in the Java world for the GUI side, or am I being overly optimistic when I say we should just start over in web technologies?

kodablah• 14 years ago

I think you have to weigh the importance of the internal application and it's need for a rewrite. It just may not be worth it. If you do, I would recommend web, but you'd still have a significant JVM-based-language backend I'd assume since you have to use RMI as your communication protocol. I personally would not do JavaFX because you aren't really stepping up enough to make the rewrite worth it.

lmm• 14 years ago

If it ain't broke don't fix it. Why do you want to replace them? Is the development burden of maintaining them in Swing really that high? Would it make life easier to have the UI be available on the web? If either of these is a "yes" then make the case on those grounds; "everyone is writing..." is a terrible reason for doing something.

In any case I see no point rewriting them in Java FX, that would just be replacing one dying technology with another.

traxtech• 14 years ago

The question should be "why do you want to go away from java swing ?" What are the problems/limitations you encounter ? If there's no serious reasons to change, why change ? (well, there's the fun to rewrite all, the fun to learn technologies, but from a business standpoint, that's not reasonable)

espinchi2• 14 years ago

One argument for going web is recruitment: the pool of active developers that know Java, Swing and Spring is shrinking.

Also, the size of the developer community in the Java/Swing world versus that in web technologies is not even comparable when it comes to sharing knowledge and open-source components. (I work for a lab, so many open-source licenses are compatible for us.)

And, sure... it would be so much fun!

RyanZAG5• 14 years ago

I'd recommend taking a look at GWT - it is pretty much for your exact situation and works very well for that. You will still need to convert from Swing to HTML elements, but if you have done any sort of separation between UI logic and Swing itself, this is usually not too bad.

This way you can swap over your existing java apps to one of those fancy HTML5 clients you're talking about. ;)

sgt3• 14 years ago

I would advise against GWT, after two separate projects - it starts off simple, but then as the project grows the more you regret basing everything around GWT in the first place. This guy will definitely not save time doing it the way you suggested.

shaydoc• 14 years ago

I have gone completely decoupled web html/css/ javascript client architecture talking to restful services, with support for web sockets thrown in too.

Enable your server side for rest and go web.

edwinnathaniel3• 14 years ago

As much as I'd like to move completely out of Java just because I like the idea of using VIM or lightweight editor with Python/Ruby to fit the ideology of a young hacker with 13" MBP, I've got to be honest with myself that the Java ecosystem provides the most complete and most mature tools (SCM, IDE, etc), libraries, and frameworks to do almost every single tasks out there.

Even with the price of verbosity. Tough proposition...

What's new in Servlet 3.1? - Java EE 7 moving forward

Related Stories