Good day, I've had discussions with people that think JAX-RS should be used as a replacement for technologies like EJB, for making n-tier solutions. Some of my main concerns about that would be...
- JAX-RS is mainly a structured approach to solving the problem, and does not use OOD very well. - Having stateless remote calls is fine for certain types of data, but I've found stateful technologies remove a lot of boilerplate stuff. Combined with good OOD, the savings are even better. JAX-RS is intended to be stateless, so you'd be required to pass all of the state information on each call. That requires a lot more thought, planning, and I think it's more prone to development errors, etc. I know TomEE supports JAX-RS as well as EJB, JAX-WS, etc. But, if EJB is better for enterprise software, I'd like to be able to articulate it. Or, perhaps JAX-RS is best, and I'd like to be able to articulate that. What sorts of other criteria would you use, in choosing a solution? Thanks.
