<?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 - Session Bean Method Placement Standards</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>Sat, 18 May 2013 10:04:46 -0400</pubDate>


    <item>

        <title>Re: method and class names</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=48465</link>

        

        
            <description><![CDATA[for the scenario you mentioned, since the return type is same, having a generic method which takes additional parameters or criteria would do there by making it a single bean/method.

Cheers,
Sridhar]]></description>
        

        <pubDate>Tue, 25 Mar 2008 20:03:27 -0400</pubDate>

        

        <jf:creationDate>Tue, 25 Mar 2008 20:03:27 -0400</jf:creationDate>
        <jf:modificationDate>Tue, 25 Mar 2008 20:03:27 -0400</jf:modificationDate>
        <jf:date>Mar 25, 2008</jf:date>
        <jf:author>sridhar r</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>to little info i guess</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=48465</link>

        

        
            <description><![CDATA[The examples i gave would have more responsibilities than just querying or as you stated getting but i tried to keep the example simple.  I can relate to your suggestion about pushing them to new 'module' because the facades in the example are pretty...]]></description>
        

        <pubDate>Wed, 20 Feb 2008 14:41:37 -0500</pubDate>

        

        <jf:creationDate>Wed, 20 Feb 2008 14:41:37 -0500</jf:creationDate>
        <jf:modificationDate>Wed, 20 Feb 2008 14:41:37 -0500</jf:modificationDate>
        <jf:date>Feb 20, 2008</jf:date>
        <jf:author>Michael Lee</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>method and class names</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=48465</link>

        

        
            <description><![CDATA[If the session beans acts just as a fascade - then I'd use just one bean which will encapsulate whole module - and I'd called methods just as a simple getters / setters (instead of queryAccount which is quite blind - maybe as finder method - but this is...]]></description>
        

        <pubDate>Wed, 20 Feb 2008 12:31:52 -0500</pubDate>

        

        <jf:creationDate>Wed, 20 Feb 2008 12:31:52 -0500</jf:creationDate>
        <jf:modificationDate>Wed, 20 Feb 2008 12:31:52 -0500</jf:modificationDate>
        <jf:date>Feb 20, 2008</jf:date>
        <jf:author>Yan  Falken</jf:author>
        <jf:replyCount>2</jf:replyCount>
    </item>


    <item>

        <title>Session Bean Method Placement Standards</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=48465</link>

        

        
            <description><![CDATA[I presents a simple question that may be mostly based on personal opinion rather than best practices.  Its difficult to explain without giving and example.  In my example i have two session beans CompanyManager and AccountManager.  Lets say i need a way...]]></description>
        

        <pubDate>Wed, 20 Feb 2008 10:11:05 -0500</pubDate>

        

        <jf:creationDate>Wed, 20 Feb 2008 10:11:05 -0500</jf:creationDate>
        <jf:modificationDate>Wed, 20 Feb 2008 10:11:05 -0500</jf:modificationDate>
        <jf:date>Feb 20, 2008</jf:date>
        <jf:author>Michael Lee</jf:author>
        <jf:replyCount>3</jf:replyCount>
    </item>



</channel>
</rss>

