java-ee-web-profile

I am working on building a REST api. My question is, when using Jersey, what are the differences between my services building and returning a Response object or returning the the bean or collection. I am only concerned with successful calls, I am throwing appropriate exceptions for errors and exceptional situations. Here is a example: @Produces(MediaType.APPLICATION_JSON) public Response search(FooBean foo){ List<FooBean> results = bar.search(foo); return Response.ok(results).build(); } vs. @Produces(MediaType.APPLICATION_JSON) public List<FooBean> search(FooBean foo){ List<FooBean> results =

I was trying to understand how the Web Services work and I came across this tutorial Now, I've seen spring being used in enterprise applications and always wondered where the main method was and how everything worked? And whenever I would go to spring tutorial they'll start with beanFactory and Contexts and what not, all in a main java method and from there just keep getting beans as required. This is totally different from what I see in the applications. Can someone tell me how exactly does spring work in this case. What is the sequence of calls. I guess there will be some hidden main method

What is the difference between a Java EE Web Profile certified server (like JOnAS) and a Java EE Full Platform certified server (like JBoss AS)? Here is nice image which explains it. Web profile is a subset of Java EE and it's purpose is to allow developers to create more lightweight applications which can be used inside simple servlet container (like Tomcat or Jetty). Future In late 2017, Oracle gave responsibility for Java EE to the Eclipse Foundation . Future versions after Java EE 8 will be known as Eclipse Enterprise For Java (EE4J) . Or Project EE4J . Or maybe EE.next . Or Jakarta EE .