<?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 - Get J2EE architecture and design answers</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>Fri, 24 May 2013 15:04:44 -0400</pubDate>


    <item>

        <title>Exception Handling</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=30911</link>

        

        
            <description><![CDATA[<blockquote>Exception handling could be a lot simpler with a few rules like the following<br><ul><li><br>1. If the exceptions are recoverable use checked exceptions<br></li><li><br>2. If they are not recoverable use exception classes that extend from...]]></description>
        

        <pubDate>Mon, 20 Feb 2006 18:55:35 -0500</pubDate>

        

        <jf:creationDate>Mon, 20 Feb 2006 18:55:35 -0500</jf:creationDate>
        <jf:modificationDate>Mon, 20 Feb 2006 18:55:35 -0500</jf:modificationDate>
        <jf:date>Feb 20, 2006</jf:date>
        <jf:author>Phillip Henry</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>Exception Handling</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=30911</link>

        

        
            <description><![CDATA[<blockquote>In an good exception handling design what the client gets will always be generic exception and not the specific runtime exception that has occured.</blockquote>Yes you are right. But I was referring to messages displayed to the user and not...]]></description>
        

        <pubDate>Tue, 08 Mar 2005 04:59:42 -0500</pubDate>

        

        <jf:creationDate>Tue, 08 Mar 2005 04:59:42 -0500</jf:creationDate>
        <jf:modificationDate>Tue, 08 Mar 2005 04:59:42 -0500</jf:modificationDate>
        <jf:date>Mar 8, 2005</jf:date>
        <jf:author>Anirban Ray</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>cnt - rollback</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=30911</link>

        

        
            <description><![CDATA[actually maybe the solution is obvious...<br><br>1. following the ejb spec and suggested pattern at the top of this thread so your method rolls back and throws an application exception.<br><br>2. when you want the method to NOT abort the enclosing...]]></description>
        

        <pubDate>Sun, 23 Jan 2005 05:35:25 -0500</pubDate>

        

        <jf:creationDate>Sun, 23 Jan 2005 05:35:25 -0500</jf:creationDate>
        <jf:modificationDate>Sun, 23 Jan 2005 05:35:25 -0500</jf:modificationDate>
        <jf:date>Jan 23, 2005</jf:date>
        <jf:author>paul strachan</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>cmt and rollback</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=30911</link>

        

        
            <description><![CDATA[I like this approach (method rolls back on application error) but I wish I could have the transaction set as Required (for all methods) and optionally on the fly execute the desired method with RequiresNew semantics.<br><br>(ie tell the container on the...]]></description>
        

        <pubDate>Sun, 23 Jan 2005 05:09:00 -0500</pubDate>

        

        <jf:creationDate>Sun, 23 Jan 2005 05:09:00 -0500</jf:creationDate>
        <jf:modificationDate>Sun, 23 Jan 2005 05:09:00 -0500</jf:modificationDate>
        <jf:date>Jan 23, 2005</jf:date>
        <jf:author>paul strachan</jf:author>
        <jf:replyCount>1</jf:replyCount>
    </item>


    <item>

        <title>Exception Handling</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=30911</link>

        

        
            <description><![CDATA[&quot;Also ensure to maintain proper error messages at a meta-level so the unchecked exceptions do not look generic to the client. &quot;<br><br>In an good exception handling design what the client gets will always be generic exception and not the...]]></description>
        

        <pubDate>Tue, 18 Jan 2005 16:56:48 -0500</pubDate>

        

        <jf:creationDate>Tue, 18 Jan 2005 16:56:48 -0500</jf:creationDate>
        <jf:modificationDate>Tue, 18 Jan 2005 16:56:48 -0500</jf:modificationDate>
        <jf:date>Jan 18, 2005</jf:date>
        <jf:author>asdfgf asdfgf</jf:author>
        <jf:replyCount>1</jf:replyCount>
    </item>


    <item>

        <title>Exception Handling</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=30911</link>

        

        
            <description><![CDATA[Exception handling could be a lot simpler with a few rules like the following<br><br>1. If the exceptions are recoverable use checked exceptions<br>2. If they are not recoverable use exception classes that extend from RuntimeException<br><br>This fits...]]></description>
        

        <pubDate>Tue, 11 Jan 2005 02:29:46 -0500</pubDate>

        

        <jf:creationDate>Tue, 11 Jan 2005 02:29:46 -0500</jf:creationDate>
        <jf:modificationDate>Tue, 11 Jan 2005 02:29:46 -0500</jf:modificationDate>
        <jf:date>Jan 11, 2005</jf:date>
        <jf:author>Anirban Ray</jf:author>
        <jf:replyCount>3</jf:replyCount>
    </item>


    <item>

        <title>The worse of two evils?</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=30911</link>

        

        
            <description><![CDATA[<blockquote>You are going to have to handle rollbacks yourself. This means you need to get in the habit of writing code in your session facades (your topmost layer of code in your EJB container) that catches application exceptions, calls...]]></description>
        

        <pubDate>Sun, 09 Jan 2005 13:09:41 -0500</pubDate>

        

        <jf:creationDate>Sun, 09 Jan 2005 13:09:41 -0500</jf:creationDate>
        <jf:modificationDate>Sun, 09 Jan 2005 13:09:41 -0500</jf:modificationDate>
        <jf:date>Jan 9, 2005</jf:date>
        <jf:author>Mncedisi Kasper</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>WAS advertisment/howto cocktail</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=30911</link>

        

        
            <description><![CDATA[&quot;Try to withdraw $200000 from bank account, get NSF exception, then application logic may decide to withdraw as much as account has. So, there is no reason here for automatic transaction&quot;<br><br>Will the second call to withdraw amount less than...]]></description>
        

        <pubDate>Fri, 07 Jan 2005 14:39:13 -0500</pubDate>

        

        <jf:creationDate>Fri, 07 Jan 2005 14:39:13 -0500</jf:creationDate>
        <jf:modificationDate>Fri, 07 Jan 2005 14:39:13 -0500</jf:modificationDate>
        <jf:date>Jan 7, 2005</jf:date>
        <jf:author>asdfgf asdfgf</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>Client should catch any exceptions</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=30911</link>

        

        
            <description><![CDATA[&quot;try/catch(TicketPurchaseException)<br><br>anyway, why not just use:<br><br>try/catch(Exception)<br>&quot;<br><br>I would vote for something like this on the client side.<br><br>...<br>try {<br>&nbsp;businessTier.purchaseTicket(...);<br>} catch...]]></description>
        

        <pubDate>Fri, 07 Jan 2005 12:20:23 -0500</pubDate>

        

        <jf:creationDate>Fri, 07 Jan 2005 12:20:23 -0500</jf:creationDate>
        <jf:modificationDate>Fri, 07 Jan 2005 12:20:23 -0500</jf:modificationDate>
        <jf:date>Jan 7, 2005</jf:date>
        <jf:author>Todd Murray</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>Client should catch any exceptions</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=30911</link>

        

        
            <description><![CDATA[<blockquote>After all, if there is a marshalling exception, the client will not be able to tell the user what the real error was anyway.</blockquote><br>This is a very good technical reason for catching any and all exceptions on the service side that I...]]></description>
        

        <pubDate>Fri, 07 Jan 2005 03:39:03 -0500</pubDate>

        

        <jf:creationDate>Fri, 07 Jan 2005 03:39:03 -0500</jf:creationDate>
        <jf:modificationDate>Fri, 07 Jan 2005 03:39:03 -0500</jf:modificationDate>
        <jf:date>Jan 7, 2005</jf:date>
        <jf:author>Justin Mahoney</jf:author>
        <jf:replyCount>1</jf:replyCount>
    </item>


    <item>

        <title>Keeping the client simple</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=30911</link>

        

        
            <description><![CDATA[I agree that the client shouldn't have knowledge of DAOExceptions; I'm not suggesting that a client should be expected to catch these.<br><br>What we've done is have EJB clients at a minimum use try/catch(Exception) to catch any possible...]]></description>
        

        <pubDate>Fri, 07 Jan 2005 03:24:25 -0500</pubDate>

        

        <jf:creationDate>Fri, 07 Jan 2005 03:24:25 -0500</jf:creationDate>
        <jf:modificationDate>Fri, 07 Jan 2005 03:24:25 -0500</jf:modificationDate>
        <jf:date>Jan 7, 2005</jf:date>
        <jf:author>Justin Mahoney</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>Client should catch any exceptions</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=30911</link>

        

        
            <description><![CDATA[<blockquote>Why should the client even know that DAOExceptions exist?  What if the backend business throws IOExceptions, SAXExceptions, YouNameItExceptions.</blockquote><br>Correct.  The client may not even have access to the class file for the exception...]]></description>
        

        <pubDate>Fri, 07 Jan 2005 03:18:16 -0500</pubDate>

        

        <jf:creationDate>Fri, 07 Jan 2005 03:18:16 -0500</jf:creationDate>
        <jf:modificationDate>Fri, 07 Jan 2005 03:18:16 -0500</jf:modificationDate>
        <jf:date>Jan 7, 2005</jf:date>
        <jf:author>Reg Whitton</jf:author>
        <jf:replyCount>2</jf:replyCount>
    </item>


    <item>

        <title>Client should catch any exceptions</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=30911</link>

        

        
            <description><![CDATA[Why should the client even know that DAOExceptions exist?  What if the backend business throws IOExceptions, SAXExceptions, YouNameItExceptions.  Should the client know and deal with each of these?  Every time the back end business changes the client has...]]></description>
        

        <pubDate>Thu, 06 Jan 2005 16:48:00 -0500</pubDate>

        

        <jf:creationDate>Thu, 06 Jan 2005 16:48:00 -0500</jf:creationDate>
        <jf:modificationDate>Thu, 06 Jan 2005 16:48:00 -0500</jf:modificationDate>
        <jf:date>Jan 6, 2005</jf:date>
        <jf:author>Todd Murray</jf:author>
        <jf:replyCount>4</jf:replyCount>
    </item>


    <item>

        <title>Client should catch any exceptions</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=30911</link>

        

        
            <description><![CDATA[I think allowing DAOExceptions to propagate up to the client is preferable. Simply wrap any service calls with try/catch(Exception), then use the catch block to expose any generic failure message you wish to the client. This allows clients to gracefully...]]></description>
        

        <pubDate>Thu, 06 Jan 2005 11:35:33 -0500</pubDate>

        

        <jf:creationDate>Thu, 06 Jan 2005 11:35:33 -0500</jf:creationDate>
        <jf:modificationDate>Thu, 06 Jan 2005 11:35:33 -0500</jf:modificationDate>
        <jf:date>Jan 6, 2005</jf:date>
        <jf:author>Justin Mahoney</jf:author>
        <jf:replyCount>5</jf:replyCount>
    </item>


    <item>

        <title>WAS advertisment/howto cocktail</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=30911</link>

        

        
            <description><![CDATA[<blockquote>Bobby Woolf: I think this is rather inconsistent, that system exceptions cause automatic rollback while application exceptions specifically do not. An exception has been thrown so should you really commit the transaction (which is the...]]></description>
        

        <pubDate>Wed, 05 Jan 2005 20:54:12 -0500</pubDate>

        

        <jf:creationDate>Wed, 05 Jan 2005 20:54:12 -0500</jf:creationDate>
        <jf:modificationDate>Wed, 05 Jan 2005 20:54:12 -0500</jf:modificationDate>
        <jf:date>Jan 5, 2005</jf:date>
        <jf:author>Michael Jouravlev</jf:author>
        <jf:replyCount>1</jf:replyCount>
    </item>



</channel>
</rss>

