aspose file tools*
The moose likes OO, Patterns, UML and Refactoring and the fly likes More about Separated Interface Pattern and layered design Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of EJB 3 in Action this week in the EJB and other Java EE Technologies forum!
JavaRanch » Java Forums » Engineering » OO, Patterns, UML and Refactoring
Bookmark "More about Separated Interface Pattern and layered design" Watch "More about Separated Interface Pattern and layered design" New topic
Author

More about Separated Interface Pattern and layered design

Rajesh Khan
Ranch Hand

Joined: Oct 16, 2011
Posts: 230
So far I believe the following is an example of a separated interface pattern.



Some questions regarding Separated interface pattern and n layered design.
I have read that the job of the service layer is to provide services to the business layer. Theoretically Are domain objects
suppose to be available to the other layers or are they just suppose to be available to the service layer ?
Rajesh Khan
Ranch Hand

Joined: Oct 16, 2011
Posts: 230
Since i was told that Domain objects are not allowed to have methods or functionalities in a different thread as this would oppose the single responsibility principle a lot has been clarified. The only question that remains is why would the interface have any relation at all with the domain objects then ?
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: More about Separated Interface Pattern and layered design
 
Similar Threads
Cyclic class
Interface
Why public?
Java beginner- interface
Separated interface Pattern and factory