<?xml version="1.0" encoding="UTF-8"?>











<rss version="2.0" xmlns:jf="http://www.jivesoftware.com/xmlns/jiveforums/rss">



<channel>
    <title>Support Forums: Message List - Opinion: One big Service class or several small classes?</title>
    <link>http://www.theserverside.com</link>
    <description>Most recent forum messages</description>
    <language>en</language>
    
        <generator>Jive Forums Silver 5.5.30 (www.jivesoftware.com)</generator>
    
    <pubDate>Tue, 21 May 2013 07:56:29 -0400</pubDate>


    <item>

        <title>Opinion: One big Service class or several small classes?</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=23705</link>

        

        
            <description><![CDATA[<div class="jive-quote">I don't agree with generating the service layer, because that's you're</div>...]]></description>
        

        <pubDate>Thu, 05 Feb 2004 10:24:46 -0500</pubDate>

        

        <jf:creationDate>Thu, 05 Feb 2004 10:24:46 -0500</jf:creationDate>
        <jf:modificationDate>Thu, 05 Feb 2004 10:24:46 -0500</jf:modificationDate>
        <jf:date>Feb 5, 2004</jf:date>
        <jf:author>Juozas Baliuka</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>Used several facades in our project</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=23705</link>

        

        
            <description><![CDATA[Hey Matt,...]]></description>
        

        <pubDate>Wed, 04 Feb 2004 19:42:59 -0500</pubDate>

        

        <jf:creationDate>Wed, 04 Feb 2004 19:42:59 -0500</jf:creationDate>
        <jf:modificationDate>Wed, 04 Feb 2004 19:42:59 -0500</jf:modificationDate>
        <jf:date>Feb 4, 2004</jf:date>
        <jf:author>Pascal Forget</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>Opinion: One big Service class or several small classes?</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=23705</link>

        

        
            <description><![CDATA[<i>I generally create service interfaces (and hard impls) which address one use case or a set of related use cases</i>...]]></description>
        

        <pubDate>Wed, 04 Feb 2004 03:17:02 -0500</pubDate>

        

        <jf:creationDate>Wed, 04 Feb 2004 03:17:02 -0500</jf:creationDate>
        <jf:modificationDate>Wed, 04 Feb 2004 03:17:02 -0500</jf:modificationDate>
        <jf:date>Feb 4, 2004</jf:date>
        <jf:author>Henrik G?ttig</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>Opinion: One big Service class or several small classes?</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=23705</link>

        

        
            <description><![CDATA[The challenge is that of vertical partitioning. Or partitioning vertical slices of business functions in to logical groupings. In my experience this is more difficult, and just as (more?) important than the typical horizontal software layering...]]></description>
        

        <pubDate>Wed, 04 Feb 2004 01:31:09 -0500</pubDate>

        

        <jf:creationDate>Wed, 04 Feb 2004 01:31:09 -0500</jf:creationDate>
        <jf:modificationDate>Wed, 04 Feb 2004 01:31:09 -0500</jf:modificationDate>
        <jf:date>Feb 4, 2004</jf:date>
        <jf:author>Clinton Begin</jf:author>
        <jf:replyCount>1</jf:replyCount>
    </item>


    <item>

        <title>Layered Services</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=23705</link>

        

        
            <description><![CDATA[I like to hedge my bets with this kind of thing. I usually define a &quot;default&quot; or generic service, with some kind of customization logic allowing me to replace it with a class-specific service where necessary. I use the target class as a...]]></description>
        

        <pubDate>Tue, 03 Feb 2004 16:15:30 -0500</pubDate>

        

        <jf:creationDate>Tue, 03 Feb 2004 16:15:30 -0500</jf:creationDate>
        <jf:modificationDate>Tue, 03 Feb 2004 16:15:30 -0500</jf:modificationDate>
        <jf:date>Feb 3, 2004</jf:date>
        <jf:author>Paul Strack</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>Layered Services</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=23705</link>

        

        
            <description><![CDATA[I find it can be useful to layer services. The front layer contains classes corresponding to use cases, the back layer contains classes which co-ordinate persistence, messaging, any other external interfaces....]]></description>
        

        <pubDate>Tue, 03 Feb 2004 15:51:34 -0500</pubDate>

        

        <jf:creationDate>Tue, 03 Feb 2004 15:51:34 -0500</jf:creationDate>
        <jf:modificationDate>Tue, 03 Feb 2004 15:51:34 -0500</jf:modificationDate>
        <jf:date>Feb 3, 2004</jf:date>
        <jf:author>Michael Mahemoff</jf:author>
        <jf:replyCount>1</jf:replyCount>
    </item>


    <item>

        <title>Opinion: One big Service class or several small classes?</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=23705</link>

        

        
            <description><![CDATA[I like to group related use cases into delegates/facades as well. These usually represent an interface to more finely-grained service managers (session beans, etc.), though not on a 1-1 basis unless the requirements for a project will remain reasonably...]]></description>
        

        <pubDate>Tue, 03 Feb 2004 14:55:02 -0500</pubDate>

        

        <jf:creationDate>Tue, 03 Feb 2004 14:55:02 -0500</jf:creationDate>
        <jf:modificationDate>Tue, 03 Feb 2004 14:55:02 -0500</jf:modificationDate>
        <jf:date>Feb 3, 2004</jf:date>
        <jf:author>John Owen</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>Opinion: One big Service class or several small classes?</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=23705</link>

        

        
            <description><![CDATA[<i>I generally create service interfaces (and hard impls) which address one use case or a set of related use cases</i>...]]></description>
        

        <pubDate>Tue, 03 Feb 2004 14:31:20 -0500</pubDate>

        

        <jf:creationDate>Tue, 03 Feb 2004 14:31:20 -0500</jf:creationDate>
        <jf:modificationDate>Tue, 03 Feb 2004 14:31:20 -0500</jf:modificationDate>
        <jf:date>Feb 3, 2004</jf:date>
        <jf:author>Alef Arendsen</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>Opinion: One big Service class or several small classes?</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=23705</link>

        

        
            <description><![CDATA[<i>I generally create service interfaces (and hard impls) which address one use case or a set of related use cases</i>...]]></description>
        

        <pubDate>Tue, 03 Feb 2004 14:21:15 -0500</pubDate>

        

        <jf:creationDate>Tue, 03 Feb 2004 14:21:15 -0500</jf:creationDate>
        <jf:modificationDate>Tue, 03 Feb 2004 14:21:15 -0500</jf:modificationDate>
        <jf:date>Feb 3, 2004</jf:date>
        <jf:author>Alef Arendsen</jf:author>
        <jf:replyCount>1</jf:replyCount>
    </item>


    <item>

        <title>Opinion: One big Service class or several small classes?</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=23705</link>

        

        
            <description><![CDATA[I generally create service interfaces (and hard impls) which address one use case or a set of related use cases. These service objects do their work via other service objects, and also via a number of Mapper/DAO objects (defined as interfaces with hard...]]></description>
        

        <pubDate>Tue, 03 Feb 2004 13:37:36 -0500</pubDate>

        

        <jf:creationDate>Tue, 03 Feb 2004 13:37:36 -0500</jf:creationDate>
        <jf:modificationDate>Tue, 03 Feb 2004 13:37:36 -0500</jf:modificationDate>
        <jf:date>Feb 3, 2004</jf:date>
        <jf:author>Colin Sampaleanu</jf:author>
        <jf:replyCount>3</jf:replyCount>
    </item>


    <item>

        <title>Opinion: One big Service class or several small classes?</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=23705</link>

        

        
            <description><![CDATA[It's all about your application requirements. If the number of business operations is fairly small and somewhat closely related, a single business facade is appropriate IMO. Of course, this does by no means result from some Spring limitation: Spring...]]></description>
        

        <pubDate>Tue, 03 Feb 2004 12:42:16 -0500</pubDate>

        

        <jf:creationDate>Tue, 03 Feb 2004 12:42:16 -0500</jf:creationDate>
        <jf:modificationDate>Tue, 03 Feb 2004 12:42:16 -0500</jf:modificationDate>
        <jf:date>Feb 3, 2004</jf:date>
        <jf:author>Juergen Hoeller</jf:author>
        <jf:replyCount>2</jf:replyCount>
    </item>


    <item>

        <title>Opinion: One big Service class or several small classes?</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=23705</link>

        

        
            <description><![CDATA[Matt Raible has opened up a discussion on designing your service classes, specifically persistence services. He talks about the en-vogue approach &quot;Single Manager&quot; versus 1 Manager for each DAO or the like....]]></description>
        

        <pubDate>Tue, 03 Feb 2004 11:18:41 -0500</pubDate>

        

        <jf:creationDate>Tue, 03 Feb 2004 11:18:41 -0500</jf:creationDate>
        <jf:modificationDate>Tue, 03 Feb 2004 11:18:41 -0500</jf:modificationDate>
        <jf:date>Feb 3, 2004</jf:date>
        <jf:author>Dion Almaer</jf:author>
        <jf:replyCount>11</jf:replyCount>
    </item>



</channel>
</rss>

