I'm just wondering what is used in 2.0 instead of ResourceFilter found in Jersey 1.0
I have code to upgrade from 1.0 to 2.0. and can't find any replacement.
DynamicFeature (directly in JAX-RS 2.0) allows you to assign providers to resource methods in the similar way ResourceFilter does in Jersey 1.
See this article that explains the concepts.
Related
I can see in spring-jms.gradle that starting with 5.0.0, the dependency to the JMS API changed from 1.1 to 2.0.
However, my question is: does this mean that spring-jms 5.x actually requires the provider to implement JMS 2.0?
I cannot find a clear requirement for th JMS version in the spring documentation neither in the Javadoc of the main spring-jms classes (like #EnableJms). For other JEE APIs like servlet-api or JPA, spring documentation/javadocs make this clearer.
Today, I still use spring 4.x and want to upgrade to 5.x, however I use a JMS provider (Oracle AQ) that implements only JMS 1.1. I would like to be sure whether spring-jms may make use of specific JMS 2.0 features like JMSContext.
I believe it's backwards-compatible, so as long as you don't try to use any 2.0 features, you should be ok.
Why don't you just give it a try?
Spring 5 brings "Full Servlet 3.1 signature support in Spring-provided Filter implementations" according to The "What's New in Spring 5"
But what does this feature mean? Is there any new Servlet 3.1 signature support added in spring 5?
You can get a hint of what this means from some issues from Spring JIRA like the one here and here. Basically the Spring filter implementation ( typically used in Spring security) obviously used ServletRequest/ServletResponse parameters in doFilter method which were not fully Servlet 3.1 API compliant. With Spring version 5 the support has been complete in contrast to previous version where it was incremental ( or as a bug fix)
I am using Spring Boot 1.4 with Thymeleaf 3.
What syntax is used? OGNL or SpEL?
Appendix A lists no Thymeleaf parameter to configure.
If you are using the spring-boot-starter-thymeleaf it configures automatically the integration of Thymeleaf with Spring, using the SpringTemplateEngine and the SpringStandardDialect.
That means the active variable expression language is SpEL. It also provides other integration features. The links point to the 2.1 version documentation, but I think it's the same in the 3.0 version.
When giving links to spring docs it would be best to link the 3.0 ones, but googling isn't quite productive with them (yet). Is there some "shortcut" (like for java core classes)? For example:
"spring factory-method 2.5.6" gives the docs about 2.5.6, but "spring factory-method 3.0" doesn't give anything from 3.0.
If you know the name of the chapter (after seeing it in the 2.5.6 results), you can add it to the search terms, like "spring factory-method 3.0 IoC Container" it works.
spring factory-method 3.0.x results in a link to the newest reference documentation. Is it what you want?
For javadoc, if the first result is for 2.5.6 / 2.0.x, you can open it and change the URL from:
/2.0.x/api/...
to
/3.0.x/javadoc-api/...
For example try:
http://static.springsource.org/spring/docs/2.0.x/api/org/springframework/beans/factory/FactoryBean.html
http://static.springsource.org/spring/docs/3.0.x/javadoc-api/org/springframework/beans/factory/FactoryBean.html
I see some are using Jersey w/ Spring. With Spring 3.0 there are now annotations available to make RESTful APIs directly in a controller. Why should I consider using Jersey w/ Spring?
Jersey pros:
comes with specifications JSR 311
reference implementation for JSR 311
Restlet and RESTeasy are other implementations for JSR 311
better tooling (at least on Netbeans)
it is integrated with Spring and Guice
EDIT
A (very nice) Comparison of Spring MVC and JAX-RS
Spring 3 is backwards compatible so you can use Jersey.
What you get is not tying your application to a propietary API.