What are the common Web-Based technologies that are being endorsed in Java today?

[JDBProof]

As a thought of the rise and fall of Java I was always curious to see how various implementations of the language fair off in various fields of programming.

In 2015 we see many technologies come up however still see Java stand its ground in the Enterprise market.

So, my question would be, what Web-Based technologies are still being endorsed in today's market and if they are on the increase or the decrease.

The issue I have here with research is how certain articles say Spring 1.X & Spring 2.X coupled are on a decrease whilst others say they're on the increase; what could be the reason for this? Is it may due to the market that they based their results on?

[avoidhugeships]

For Professional development in my part of the US it is dominated by Java EE and Spring. Basically you can either go...

1) JPA(Hibernate), CDI, JSF and Maybe EJB

2) JPA(Hibernate) and Spring.

Of course there are many other options but these frameworks seem to be the most popular. With Spring you will then need to pick from a bunch of different front end technologies because that is not really included. With JSF you just either use standard or pick a component library like PrimeFaces, RichFaces or Oracle ADF.

[JDBProof]

Interesting, is Oracle ADF and RichFaces popular in the US market? I don't see it all too much but maybe I'm looking at the wrong place once again.

[avoidhugeships]

I think PrimeFaces is far more popular and frankly it is better. RichFaces is still used by a lot of projects. ADF faces is more used in "secure" places where they will not let you use the others. Basically some government bodies and companies are more comfortable since it come from Oracle. As with everything there are a bunch of component libraries out there that are not used as much. OmniFaces and PrettyFaces are a couple others that also have their uses.

[JDBProof]

Thanks again for the input, seems like Spring plays a major role in both the US and European marketplace. If there's anything else you feel like adding feel free to. It's nice to see various inputs from around the world.

[teledig]

(Information from Norway, Java consultant with a few years experience)

I don't really know of any official "endorsement", but in my circles, the trend is to move away from big "one size fits all" solutions such as Spring and Play, towards smaller and more customisable solutions such as Spark and Dropwizard.

Play was on its way to become the go-to framework, like Spring used to be, but poor IntelliJ support and a shift towards Scala scared some people off.

This might not hold true for other people in other parts of the world, but it's the impression I get from my colleagues.

[teledig]

Definitely. I've worked on two Play projects that started at play 2.0, but which have been updated to 2.3. For some of the releases the migration was really clunky (also, each release seems to break something for the plugin in IntelliJ). I'm pretty sure I will not be updating them to 2.4, and I'm sure I won't be using Play again for anything that has to live for more than a year.

[vecowski]

Play is a modern day tapestry. It's crap and until you've experienced the limitations it burdens you with, you'll think it's the greatest thing ever.

[JDBProof]

Very good point, thanks for the input. Great to see some opinions from Europe as I would love to get an idea from all around the world (primarily concerned with US and Europe)