service-layer

I have a repository layer that is responsible for my data-access, which is called by a service layer. The service layer returns DTOs which are serialized and sent over the wire. More often than not, services do little more than access a repository and return whatever the repository returns. But for that to work, the repository has to return an instance of that DTO. Otherwise, you would first have to map the data layer object that the repository returns to a DTO in the service layer and return that. That just seems wasteful. On top of that, if creation of the DTOs happens in the service layer,

I looked at the example on http://solitarygeek.com/java/developing-a-simple-java-application-with-spring/comment-page-1#comment-1639 I'm trying to figure out why the service layer is needed in the first place in the example he provides. If you took it out, then in your client, you could just do: UserDao userDao = new UserDaoImpl(); Iterator users = userDao.getUsers(); while (…) { … } It seems like the service layer is simply a wrapper around the DAO. Can someone give me a case where things could get messy if the service layer were removed? I just don’t see the point in having the service layer

I have been developing enterprise applications for many years using .Net My apps usually have a domain model containing entities mapping to SQL DB tables. I use a Repository pattern, Dependency injection and a service layer. Recently we started working on MVC 3 projects and we had a debate where to put which logic. I came accross thin Controller / FAT Model architecture and was wondering how the service layer would fit in Option 1 - Model talks to services Controller is thin, calls methods on the models. The models "know" how to load themselfs from the DB and talk to repositories or services.

I'm creating an MVC website and also intend to create a web API for use both within the website and potentially by third parties. From the MVC controllers I'll be calling into a service layer which will contain business logic, act on domain models, perform validation, make infrastructure external service calls etc. The service layer in turn will call into repositories for any database interactions. Now, I like the look of ServiceStack and intend on using it for the Web API - it seems more mature than the ASP.NET MVC 4 Web API . My question is, should I have the ServiceStack API call into my

I maintain a web application that have a page with the JSF tag <f:event . I have rewrote a method in a service class for it to throw a business exception. However, when the business exception is thrown, it isn't caught in managed bean and the exception is showed on the page. Seems that my code try/catch doesn't work. In XHTML: <f:event listener="#{resourceBean.init(enrollment)}" type="preRenderView" /> Listener method in Managed Bean: private boolean canCreateResource; public void init(Enrollment enrollment) { (...) try { canCreateResource = resourceService.canCreateResource(enrollment); }