Hi we're on our way to upgrade to jetty 11 and have come across this issue - Jetty 11 needs servlet 5.0 while spark-java even upto 2.9.4 is still using servlet 3.0. I could not find any info related to this on the spark-java page. Does anyone have any information on the planned upgrade or such ?
There's been no work on spark-java to upgrade past Servlet 3.0.
There has been forks of spark-java for that though.
See
https://github.com/perwendel/spark/issues/1266
Related
I am trying to understand how Servlets 4 (Java EE 8) help us to gain the benefits of HTTP/2 by writing Hello World kind of application. I am aware that Java EE 8 is yet to be released.
Is there a way I can try these features on beta release of any servlet container like GlashFish?
Is there a pre release for developers to try out the Java EE 8 API?
Disclaimer: Once Java EE 8 and the Servlet API 4.0 (which supports HTTP/2) are under development, this answer may not be updated.
What's currently available (July 6th 2016)
At the time of writing, here are a few resources that you may find useful:
GlassFish 5 nightly builds (looks like it's a fork of GlassFish 4.1 and seems not to incoporate Java EE 8 components).
Java Servlet API 4.0 JAR (currently released as beta) available on Maven repositories.
Apache Tomcat 9 (not released as a final version yet), which supports the Servlet API 4.0.
Payara 5 (under development), which is a branch of the Payara project to be used for Java EE 8 features.
The JSR for the Java Servlet API 4.0 (currently available as an early draft).
More details about Java EE 8
Quoting the Java EE overview from Oracle website:
As the industry begins the rapid adoption of Java EE 7, work has begun on Java EE 8. With a survey that received over 4,500 responses, the community has prioritized the desired features for Java EE 8. In fact, the following JSRs have already been submitted:
JSR 366 - Java EE 8
JSR 367 - The Java API for JSON Binding
JSR 368 - Java Message Service 2.1
JSR 369 - Java Servlet 4.0
JSR 370 - Java API for RESTful Web Services 2.1
JSR 371 - Model-View-Controller 1.0
JSR 372 - Java Server Faces 2.3
JSR 373 - Java EE Management API 1.0
JSR 374 - Java API for JSON Processing 1.1
JSR 375 - Java EE Security API 1.0
The results of the survey can be seen in the following chart:
If you want to try out Servlet 4 with server push functionality (the new PushBuilder which allows the server to push data to the client), you need:
latest glassfish5 nightly build (http://download.oracle.com/glassfish/5.0/nightly/latest-glassfish.zip)
JDK > 1.8.0_131 + (latest one is _144 at the time of this writing)
make sure you access the servlet over HTTPS, HTTP/2 doesn't work without SSL apparently.
Check out a complete example here: https://en.kodedu.com/2017/04/first-look-http2-server-push-java-servlet-4-0-specification/
An important requirement when using Servlet 4 and the Server Push feature is that you must secure the connection and an able HTTPS. It is an extra step required when using HTTP/2 on the server and the client is a browser. Here is a blog post about how to set up HTTPS and Servlet 4.0.
Browsers vendors have implemented HTTP/2 over TLS and even though this is not a specification requirement it is required that you set up a secure connection.
I have a simple example of how to use Server Push in a servlet that should help get you started.
We have a legacy app which uses seam 1.1. Its deployed on websphere 7 which has JSF 1.2. So will it cause any problems? Are seam 1.1 and JSF 1.2 compatible?
Or do i need to upgrade the version of jboss seam which is compatible with jsf 1.2?
EDIT 1:-
The reason I am asking this question is that suddenly we are getting following erros
application E JSF1007: Duplicate component ID listForm:j_id_jsp_768167483_47:templateItems:j_id_jsp_768167483_77 found in view.
Another team has said that its because of the version mismatch of JSF being used in app and the JSf version supported by websphere 7 which is 1.2.
Yes, They both are compatible and will cause no problems.
I wanted to upgrade from Servlet 2.4 to Servlet 3.0. Currently we are using ESAPI in our application and would like to upgrade.
Latest ESAPI release depends on servlet-api-2.4.jar. Does ESAPI support Servlet 3.0?
I upgraded my application to support Servlet 3.0 and ESAPI seems to work. So it is backwards compatible.
Is there any way to use servlet 2.5 specification on WAS 8.0, by default he try to use 3.0 but the portal which I'm using doesn't support new servlet specification and I've to run it on lower version.
No, the only servlet container included in WebSphere Application Server 8.0 is the one that supports the Servlet 3.0 specification.
(If you have a specific backwards compatibility problem, you could post that, and someone might know how to workaround the issue.)
is jbos5.1.0 compatible with jdk6 and spring2.5.X.
I am also integraion acegi security and not spring security 3.0 as i am using spring 2.5.0?
IS jboss 5.1.0 comaptible with spribng3.0 andjdk6 ?
A few months ago, I've tried JBoss 5 with Spring 2.5.6 and couldn't deploy my application, because of this bug. The comments on the issue, mention the problem only happens with EJB, but my application didn't make use of EJB and it was packed as a war.
According to the JIRA, this was fixed in spring 3.0RC1, but I haven't tried it (for now, I gave up updating to a new version of JBoss).