Spring Quickly Question/REST

[Charles O'Leary]

RestEasy Or Jersey?  With option does the book cover mostly?

[Laurentiu Spilca]

Hi Charles. Thanks for the question. We'll use REST directly with Spring, which behind the scenes uses Jersey.

[Charles O'Leary]

Laurentiu Spilca wrote:We'll use REST directly with Spring, which behind the scenes uses Jersey.

I think Red Hat JBoss EAP 7.X bundles RESTEasy 3?  If so, would there be an advantage to reconfigure things for Jersey?

[Laurentiu Spilca]

Correct me if I'm wrong. Isn't that an application server? In this case, we jumped into another subject that goes away from using Spring MVC for that. In that case, you'd probably use CDI directly and then yes, you really on what the AS provides you for JSON deserialization. If you write a Spring app, then you don't need an application server but only a servlet container (which is more light). In this case, you really on what you configure with Spring.

[Charles O'Leary]

Laurentiu Spilca wrote:Correct me if I'm wrong. Isn't that an application server?

Yes, it is.

Laurentiu Spilca wrote:In this case, we jumped into another subject that goes away from using Spring MVC for that. In that case, you'd probably use CDI directly and then yes, you really on what the AS provides you for JSON deserialization. If you write a Spring app, then you don't need an application server but only a servlet container (which is more light). In this case, you really on what you configure with Spring.

Please help me understand.  I cannot control my employer's use of an application server.  Because my employer uses an application server, then as developers, we would be better off not using Spring?  Spring is the new direction that management is now mandating.  We also run a ton of existing EJBs.

[Laurentiu Spilca]

Hm. That would be difficult. Practically you can create war files with Spring and run them in an application server. However, in software development what you practically do is not necessarily what you should do. Now, the fact that Spring is the management's choice is good. To run your Spring apps in an application server is not what I would recommend. What I would recommend you is decouple parts of your app step by step and run them individually. Use Spring Boot which comes with preconfigured servlet container and convention over configuration. Try to progressively get rid of the application server and aim to a service oriented architecture where each app is independent. In the future this will give you a lot of opportunities, from deployment to work management. Of course, I don't expect it to be an easy job. But it is possible. I've seen it done more than once

[Charles O'Leary]

Laurentiu Spilca wrote:Hm. That would be difficult. Practically you can create war files with Spring and run them in an application server. However, in software development what you practically do is not necessarily what you should do. Now, the fact that Spring is the management's choice is good. To run your Spring apps in an application server is not what I would recommend. What I would recommend you is decouple parts of your app step by step and run them individually. Use Spring Boot which comes with preconfigured servlet container and convention over configuration. Try to progressively get rid of the application server and aim to a service oriented architecture where each app is independent. In the future this will give you a lot of opportunities, from deployment to work management. Of course, I don't expect it to be an easy job. But it is possible. I've seen it done more than once

Okay, this is likely why management has slated only our new and upcoming apps for Spring and Spring Boot.  Thanks for the detailed explanation.