Should I be doing my automapping in my service layer or at my controller? I like the Idea of Repository - Raw data IQueryable type stuff with full domain(type) objects.
I looked at the example on http://solitarygeek.com/java/developing-a-simple-java-application-with-spring/comment-page-1#comment-1639
While defining our application architecture (which contains both web UI and external web services) we stumbled upon our inability to find a common name for the topmost layer.
Take a class which has relations with a couple of other classes. The first class can be seen as the aggregate(root). Seen from the point of the service layer how would one best split the calls?
I\'m coding a zend framework application using the the standard mvc paradigm with an added service layer to take care of application/business logic. It seems quite popular to put your access control i
I have been reading up on DDD and I think I may be using services wrong or at least in a not so ideal way. My service classes tend to have quite a few instance variables containing repository referenc
I need to design a system which has these bas开发者_运维问答ic components: A Webserver which will be getting ~100 requests/sec. The webserver only needs to dump data into raw data repository.
In my project I have my Linq To SQL dbml file, A Repository Layer for each DB Table and a Service 开发者_如何学运维Layer for each Repository.
I have a function called GetUserByOpenId I don\'t want to be using this function at all Public Function GetUserByOpenID(ByVal claimedidentifier As String) As User Implements IUserRepository.GetUserBy
I\'m thinking about possible alternatives for our EJB based service layer and wondered if it would make sense to use just the service and database layer of Grails together with the Remoting Plugin or
加载中,请稍侯......