<?xml version="1.0" encoding="UTF-8"?>
<GoodreadsResponse>
	<Request>
		<authentication>false</authentication>
		    <method><![CDATA[]]></method>
	</Request>
	
<book>
  <id>347733</id>
  <title><![CDATA[J2EE Design Patterns]]></title>
  <isbn><![CDATA[0596004273]]></isbn>
  <isbn13><![CDATA[9780596004279]]></isbn13>
  <image_url>http://photo.goodreads.com/books/1173938506m/347733.jpg</image_url>
  <small_image_url>http://photo.goodreads.com/books/1173938506s/347733.jpg</small_image_url>
  <description><![CDATA[Architects of buildings and architects of software have more in common than most people think. Both professions require attention to detail, and both practitioners will see their work collapse around them if they make too many mistakes.  It's impossible to imagine a world in which buildings get built without blueprints, but it's still common for software applications to be designed and built without blueprints, or in this case, design patterns.    A software design pattern can be identified as &quot;a recurring solution to a recurring problem.&quot; Using design patterns for software development makes sense in the same way that architectural design patterns make sense--if it works well in one place, why not use it in another?  But developers have had enough of books that simply catalog design patterns without extending into new areas, and books that are so theoretical that you can't actually do anything better after reading them than you could before you started.    Crawford and Kaplan's <em>J2EE Design Patterns</em> approaches the subject in a unique, highly practical and pragmatic way. Rather than simply present another catalog of design patterns, the authors broaden the scope by discussing ways to choose design patterns when building an enterprise application from scratch, looking closely at the real world tradeoffs that Java developers must weigh when architecting their applications. Then they go on to show how to apply the patterns when writing realworld software.  They also extend design patterns into areas not covered in other books, presenting original patterns for data modeling, transaction / process modeling, and interoperability.     <em>J2EE Design Patterns</em> offers extensive coverage of the five problem areas enterprise developers face:&lt;ul&gt;  &lt;li&gt;Maintenance (Extensibility)&lt;/li&gt;  &lt;li&gt;Performance (System Scalability)&lt;/li&gt;  &lt;li&gt;Data Modeling (Business Object Modeling)&lt;/li&gt;  &lt;li&gt;Transactions (process Modeling)&lt;/li&gt;  &lt;li&gt;Messaging (Interoperability)&lt;/li&gt;&lt;/ul&gt;  And with its careful balance between theory and practice, <em>J2EE Design Patterns</em> will give developers new to the Java enterprise development arena a solid understanding of how to approach a wide variety of architectural and procedural problems, and will give experienced J2EE pros an opportunity to extend and improve on their existing experience. ]]></description>
  <work>
  <best_book_id type="integer">347733</best_book_id>
  <books_count type="integer">1</books_count>
  <desc_user_id type="integer" nil="true"></desc_user_id>
  <id type="integer">338023</id>
  <media_type nil="true"></media_type>
  <original_language_id type="integer" nil="true"></original_language_id>
  <original_publication_day type="integer">24</original_publication_day>
  <original_publication_month type="integer">9</original_publication_month>
  <original_publication_year type="integer">2003</original_publication_year>
  <original_title>J2EE Design Patterns</original_title>
  <rating_dist>total:2|5:0|4:1|3:0|2:1|1:0|</rating_dist>
  <ratings_count type="integer">2</ratings_count>
  <ratings_sum type="integer">6</ratings_sum>
  <reviews_count type="integer">9</reviews_count>
  <text_reviews_count type="integer">0</text_reviews_count>
</work>

  <average_rating><![CDATA[3.00]]></average_rating>
  <ratings_count><![CDATA[2]]></ratings_count>
  <text_reviews_count><![CDATA[0]]></text_reviews_count>
  
  <url><![CDATA[http://www.goodreads.com/book/show/347733.J2EE_Design_Patterns]]></url>
  <link><![CDATA[http://www.goodreads.com/book/show/347733.J2EE_Design_Patterns]]></link>
  <authors>
    <author>
    <id>135300</id>
        <name><![CDATA[William Crawford]]></name>
    <image_url><![CDATA[http://www.goodreads.com/images/nophoto/nophoto-U-200x266.jpg]]></image_url>
    <small_image_url><![CDATA[http://www.goodreads.com/images/nophoto/nophoto-U-50x66.jpg]]></small_image_url>
    <link><![CDATA[http://www.goodreads.com/author/show/135300.William_Crawford]]></link>
    <average_rating>3.80</average_rating>
    <ratings_count>5</ratings_count>
    <text_reviews_count>1</text_reviews_count>
  </author>
    <author>
    <id>189045</id>
        <name><![CDATA[Jonathan Kaplan]]></name>
    <image_url><![CDATA[http://www.goodreads.com/images/nophoto/nophoto-U-200x266.jpg]]></image_url>
    <small_image_url><![CDATA[http://www.goodreads.com/images/nophoto/nophoto-U-50x66.jpg]]></small_image_url>
    <link><![CDATA[http://www.goodreads.com/author/show/189045.Jonathan_Kaplan]]></link>
    <average_rating>3.84</average_rating>
    <ratings_count>70</ratings_count>
    <text_reviews_count>11</text_reviews_count>
  </author>
  </authors>
    <reviews start="1" end="9" total="9">
      <review>
  <id>78190948</id>
    <user>
    <id>2956955</id>
    <name><![CDATA[Ruben]]></name>
    <location><![CDATA[Brussels, 02, Belgium]]></location>
    <link><![CDATA[http://www.goodreads.com/user/show/2956955-ruben]]></link>
    <image_url><![CDATA[http://photo.goodreads.com/users/1258558865p3/2956955.jpg]]></image_url>
    <small_image_url><![CDATA[http://photo.goodreads.com/users/1258558865p2/2956955.jpg]]></small_image_url>
  </user>
    <book>
  <id type="integer">347733</id>
  <isbn>0596004273</isbn>
  <isbn13>9780596004279</isbn13>
  <text_reviews_count type="integer">0</text_reviews_count>
  <title>
    <![CDATA[J2EE Design Patterns]]>
  </title>
  <image_url>http://photo.goodreads.com/books/1173938506m/347733.jpg</image_url>
  <small_image_url>http://photo.goodreads.com/books/1173938506s/347733.jpg</small_image_url>
  <link>http://www.goodreads.com/book/show/347733.J2EE_Design_Patterns</link>
  <average_rating>3.00</average_rating>
  <ratings_count>2</ratings_count>
  <description>
    <![CDATA[Architects of buildings and architects of software have more in common than most people think. Both professions require attention to detail, and both practitioners will see their work collapse around them if they make too many mistakes.  It's impossible to imagine a world in which buildings get built without blueprints, but it's still common for software applications to be designed and built without blueprints, or in this case, design patterns.    A software design pattern can be identified as &quot;a recurring solution to a recurring problem.&quot; Using design patterns for software development makes sense in the same way that architectural design patterns make sense--if it works well in one place, why not use it in another?  But developers have had enough of books that simply catalog design patterns without extending into new areas, and books that are so theoretical that you can't actually do anything better after reading them than you could before you started.    Crawford and Kaplan's <em>J2EE Design Patterns</em> approaches the subject in a unique, highly practical and pragmatic way. Rather than simply present another catalog of design patterns, the authors broaden the scope by discussing ways to choose design patterns when building an enterprise application from scratch, looking closely at the real world tradeoffs that Java developers must weigh when architecting their applications. Then they go on to show how to apply the patterns when writing realworld software.  They also extend design patterns into areas not covered in other books, presenting original patterns for data modeling, transaction / process modeling, and interoperability.     <em>J2EE Design Patterns</em> offers extensive coverage of the five problem areas enterprise developers face:&lt;ul&gt;  &lt;li&gt;Maintenance (Extensibility)&lt;/li&gt;  &lt;li&gt;Performance (System Scalability)&lt;/li&gt;  &lt;li&gt;Data Modeling (Business Object Modeling)&lt;/li&gt;  &lt;li&gt;Transactions (process Modeling)&lt;/li&gt;  &lt;li&gt;Messaging (Interoperability)&lt;/li&gt;&lt;/ul&gt;  And with its careful balance between theory and practice, <em>J2EE Design Patterns</em> will give developers new to the Java enterprise development arena a solid understanding of how to approach a wide variety of architectural and procedural problems, and will give experienced J2EE pros an opportunity to extend and improve on their existing experience. ]]>
  </description>
  <published>2003</published>
</book>

    <rating>0</rating>
  <votes>0</votes>
  <spoiler_flag>false</spoiler_flag>
  <shelves>
        <shelf name="read" />
          </shelves>
  <recommended_for><![CDATA[]]></recommended_for>
  <recommended_by><![CDATA[]]></recommended_by>
  <read_at></read_at>
  <date_added>Wed Nov 18 08:23:17 -0800 2009</date_added>
  <date_updated>Wed Nov 18 08:23:17 -0800 2009</date_updated>
  <read_count></read_count>
    <body><![CDATA[]]></body>
    
  <url><![CDATA[http://www.goodreads.com/review/show/78190948]]></url>
  <link><![CDATA[http://www.goodreads.com/review/show/78190948]]></link>
</review>
      <review>
  <id>65943221</id>
    <user>
    <id>2401018</id>
    <name><![CDATA[Blair]]></name>
    <location><![CDATA[Salt Lake City, UT]]></location>
    <link><![CDATA[http://www.goodreads.com/user/show/2401018-blair-buxton]]></link>
    <image_url><![CDATA[http://www.goodreads.com/images/nophoto-U-111x148.jpg]]></image_url>
    <small_image_url><![CDATA[http://www.goodreads.com/images/nophoto-U-50x66.jpg]]></small_image_url>
  </user>
    <book>
  <id type="integer">347733</id>
  <isbn>0596004273</isbn>
  <isbn13>9780596004279</isbn13>
  <text_reviews_count type="integer">0</text_reviews_count>
  <title>
    <![CDATA[J2EE Design Patterns]]>
  </title>
  <image_url>http://photo.goodreads.com/books/1173938506m/347733.jpg</image_url>
  <small_image_url>http://photo.goodreads.com/books/1173938506s/347733.jpg</small_image_url>
  <link>http://www.goodreads.com/book/show/347733.J2EE_Design_Patterns</link>
  <average_rating>3.00</average_rating>
  <ratings_count>2</ratings_count>
  <description>
    <![CDATA[Architects of buildings and architects of software have more in common than most people think. Both professions require attention to detail, and both practitioners will see their work collapse around them if they make too many mistakes.  It's impossible to imagine a world in which buildings get built without blueprints, but it's still common for software applications to be designed and built without blueprints, or in this case, design patterns.    A software design pattern can be identified as &quot;a recurring solution to a recurring problem.&quot; Using design patterns for software development makes sense in the same way that architectural design patterns make sense--if it works well in one place, why not use it in another?  But developers have had enough of books that simply catalog design patterns without extending into new areas, and books that are so theoretical that you can't actually do anything better after reading them than you could before you started.    Crawford and Kaplan's <em>J2EE Design Patterns</em> approaches the subject in a unique, highly practical and pragmatic way. Rather than simply present another catalog of design patterns, the authors broaden the scope by discussing ways to choose design patterns when building an enterprise application from scratch, looking closely at the real world tradeoffs that Java developers must weigh when architecting their applications. Then they go on to show how to apply the patterns when writing realworld software.  They also extend design patterns into areas not covered in other books, presenting original patterns for data modeling, transaction / process modeling, and interoperability.     <em>J2EE Design Patterns</em> offers extensive coverage of the five problem areas enterprise developers face:&lt;ul&gt;  &lt;li&gt;Maintenance (Extensibility)&lt;/li&gt;  &lt;li&gt;Performance (System Scalability)&lt;/li&gt;  &lt;li&gt;Data Modeling (Business Object Modeling)&lt;/li&gt;  &lt;li&gt;Transactions (process Modeling)&lt;/li&gt;  &lt;li&gt;Messaging (Interoperability)&lt;/li&gt;&lt;/ul&gt;  And with its careful balance between theory and practice, <em>J2EE Design Patterns</em> will give developers new to the Java enterprise development arena a solid understanding of how to approach a wide variety of architectural and procedural problems, and will give experienced J2EE pros an opportunity to extend and improve on their existing experience. ]]>
  </description>
  <published>2003</published>
</book>

    <rating>0</rating>
  <votes>0</votes>
  <spoiler_flag>false</spoiler_flag>
  <shelves>
        <shelf name="read" />
          </shelves>
  <recommended_for><![CDATA[]]></recommended_for>
  <recommended_by><![CDATA[]]></recommended_by>
  <read_at>Wed Apr 01 00:00:00 -0700 2009</read_at>
  <date_added>Sun Aug 02 20:11:25 -0700 2009</date_added>
  <date_updated>Sun Aug 02 20:11:38 -0700 2009</date_updated>
  <read_count></read_count>
    <body><![CDATA[]]></body>
    
  <url><![CDATA[http://www.goodreads.com/review/show/65943221]]></url>
  <link><![CDATA[http://www.goodreads.com/review/show/65943221]]></link>
</review>
      <review>
  <id>56129388</id>
    <user>
    <id>1799056</id>
    <name><![CDATA[Chris]]></name>
    <location><![CDATA[Green Bay, WI]]></location>
    <link><![CDATA[http://www.goodreads.com/user/show/1799056-chris]]></link>
    <image_url><![CDATA[http://www.goodreads.com/images/nophoto-M-111x148.jpg]]></image_url>
    <small_image_url><![CDATA[http://www.goodreads.com/images/nophoto-M-50x66.jpg]]></small_image_url>
  </user>
    <book>
  <id type="integer">347733</id>
  <isbn>0596004273</isbn>
  <isbn13>9780596004279</isbn13>
  <text_reviews_count type="integer">0</text_reviews_count>
  <title>
    <![CDATA[J2EE Design Patterns]]>
  </title>
  <image_url>http://photo.goodreads.com/books/1173938506m/347733.jpg</image_url>
  <small_image_url>http://photo.goodreads.com/books/1173938506s/347733.jpg</small_image_url>
  <link>http://www.goodreads.com/book/show/347733.J2EE_Design_Patterns</link>
  <average_rating>3.00</average_rating>
  <ratings_count>2</ratings_count>
  <description>
    <![CDATA[Architects of buildings and architects of software have more in common than most people think. Both professions require attention to detail, and both practitioners will see their work collapse around them if they make too many mistakes.  It's impossible to imagine a world in which buildings get built without blueprints, but it's still common for software applications to be designed and built without blueprints, or in this case, design patterns.    A software design pattern can be identified as &quot;a recurring solution to a recurring problem.&quot; Using design patterns for software development makes sense in the same way that architectural design patterns make sense--if it works well in one place, why not use it in another?  But developers have had enough of books that simply catalog design patterns without extending into new areas, and books that are so theoretical that you can't actually do anything better after reading them than you could before you started.    Crawford and Kaplan's <em>J2EE Design Patterns</em> approaches the subject in a unique, highly practical and pragmatic way. Rather than simply present another catalog of design patterns, the authors broaden the scope by discussing ways to choose design patterns when building an enterprise application from scratch, looking closely at the real world tradeoffs that Java developers must weigh when architecting their applications. Then they go on to show how to apply the patterns when writing realworld software.  They also extend design patterns into areas not covered in other books, presenting original patterns for data modeling, transaction / process modeling, and interoperability.     <em>J2EE Design Patterns</em> offers extensive coverage of the five problem areas enterprise developers face:&lt;ul&gt;  &lt;li&gt;Maintenance (Extensibility)&lt;/li&gt;  &lt;li&gt;Performance (System Scalability)&lt;/li&gt;  &lt;li&gt;Data Modeling (Business Object Modeling)&lt;/li&gt;  &lt;li&gt;Transactions (process Modeling)&lt;/li&gt;  &lt;li&gt;Messaging (Interoperability)&lt;/li&gt;&lt;/ul&gt;  And with its careful balance between theory and practice, <em>J2EE Design Patterns</em> will give developers new to the Java enterprise development arena a solid understanding of how to approach a wide variety of architectural and procedural problems, and will give experienced J2EE pros an opportunity to extend and improve on their existing experience. ]]>
  </description>
  <published>2003</published>
</book>

    <rating>0</rating>
  <votes>0</votes>
  <spoiler_flag>false</spoiler_flag>
  <shelves>
            <shelf name="to-read" />
      </shelves>
  <recommended_for><![CDATA[]]></recommended_for>
  <recommended_by><![CDATA[]]></recommended_by>
  <read_at></read_at>
  <date_added>Thu May 14 19:21:28 -0700 2009</date_added>
  <date_updated>Thu May 14 19:21:28 -0700 2009</date_updated>
  <read_count></read_count>
    <body><![CDATA[]]></body>
    
  <url><![CDATA[http://www.goodreads.com/review/show/56129388]]></url>
  <link><![CDATA[http://www.goodreads.com/review/show/56129388]]></link>
</review>
      <review>
  <id>54365027</id>
    <user>
    <id>2269273</id>
    <name><![CDATA[Su]]></name>
    <location><![CDATA[The United States]]></location>
    <link><![CDATA[http://www.goodreads.com/user/show/2269273-su]]></link>
    <image_url><![CDATA[http://www.goodreads.com/images/nophoto-M-111x148.jpg]]></image_url>
    <small_image_url><![CDATA[http://www.goodreads.com/images/nophoto-M-50x66.jpg]]></small_image_url>
  </user>
    <book>
  <id type="integer">347733</id>
  <isbn>0596004273</isbn>
  <isbn13>9780596004279</isbn13>
  <text_reviews_count type="integer">0</text_reviews_count>
  <title>
    <![CDATA[J2EE Design Patterns]]>
  </title>
  <image_url>http://photo.goodreads.com/books/1173938506m/347733.jpg</image_url>
  <small_image_url>http://photo.goodreads.com/books/1173938506s/347733.jpg</small_image_url>
  <link>http://www.goodreads.com/book/show/347733.J2EE_Design_Patterns</link>
  <average_rating>3.00</average_rating>
  <ratings_count>2</ratings_count>
  <description>
    <![CDATA[Architects of buildings and architects of software have more in common than most people think. Both professions require attention to detail, and both practitioners will see their work collapse around them if they make too many mistakes.  It's impossible to imagine a world in which buildings get built without blueprints, but it's still common for software applications to be designed and built without blueprints, or in this case, design patterns.    A software design pattern can be identified as &quot;a recurring solution to a recurring problem.&quot; Using design patterns for software development makes sense in the same way that architectural design patterns make sense--if it works well in one place, why not use it in another?  But developers have had enough of books that simply catalog design patterns without extending into new areas, and books that are so theoretical that you can't actually do anything better after reading them than you could before you started.    Crawford and Kaplan's <em>J2EE Design Patterns</em> approaches the subject in a unique, highly practical and pragmatic way. Rather than simply present another catalog of design patterns, the authors broaden the scope by discussing ways to choose design patterns when building an enterprise application from scratch, looking closely at the real world tradeoffs that Java developers must weigh when architecting their applications. Then they go on to show how to apply the patterns when writing realworld software.  They also extend design patterns into areas not covered in other books, presenting original patterns for data modeling, transaction / process modeling, and interoperability.     <em>J2EE Design Patterns</em> offers extensive coverage of the five problem areas enterprise developers face:&lt;ul&gt;  &lt;li&gt;Maintenance (Extensibility)&lt;/li&gt;  &lt;li&gt;Performance (System Scalability)&lt;/li&gt;  &lt;li&gt;Data Modeling (Business Object Modeling)&lt;/li&gt;  &lt;li&gt;Transactions (process Modeling)&lt;/li&gt;  &lt;li&gt;Messaging (Interoperability)&lt;/li&gt;&lt;/ul&gt;  And with its careful balance between theory and practice, <em>J2EE Design Patterns</em> will give developers new to the Java enterprise development arena a solid understanding of how to approach a wide variety of architectural and procedural problems, and will give experienced J2EE pros an opportunity to extend and improve on their existing experience. ]]>
  </description>
  <published>2003</published>
</book>

    <rating>2</rating>
  <votes>0</votes>
  <spoiler_flag>false</spoiler_flag>
  <shelves>
        <shelf name="read" />
          </shelves>
  <recommended_for><![CDATA[]]></recommended_for>
  <recommended_by><![CDATA[]]></recommended_by>
  <read_at></read_at>
  <date_added>Wed Apr 29 09:44:47 -0700 2009</date_added>
  <date_updated>Thu Dec 24 18:13:32 -0800 2009</date_updated>
  <read_count></read_count>
    <body><![CDATA[]]></body>
    
  <url><![CDATA[http://www.goodreads.com/review/show/54365027]]></url>
  <link><![CDATA[http://www.goodreads.com/review/show/54365027]]></link>
</review>
      <review>
  <id>53587492</id>
    <user>
    <id>760917</id>
    <name><![CDATA[Eugene]]></name>
    <location><![CDATA[Ukraine]]></location>
    <link><![CDATA[http://www.goodreads.com/user/show/760917-eugene]]></link>
    <image_url><![CDATA[http://www.goodreads.com/images/nophoto-U-111x148.jpg]]></image_url>
    <small_image_url><![CDATA[http://www.goodreads.com/images/nophoto-U-50x66.jpg]]></small_image_url>
  </user>
    <book>
  <id type="integer">347733</id>
  <isbn>0596004273</isbn>
  <isbn13>9780596004279</isbn13>
  <text_reviews_count type="integer">0</text_reviews_count>
  <title>
    <![CDATA[J2EE Design Patterns]]>
  </title>
  <image_url>http://photo.goodreads.com/books/1173938506m/347733.jpg</image_url>
  <small_image_url>http://photo.goodreads.com/books/1173938506s/347733.jpg</small_image_url>
  <link>http://www.goodreads.com/book/show/347733.J2EE_Design_Patterns</link>
  <average_rating>3.00</average_rating>
  <ratings_count>2</ratings_count>
  <description>
    <![CDATA[Architects of buildings and architects of software have more in common than most people think. Both professions require attention to detail, and both practitioners will see their work collapse around them if they make too many mistakes.  It's impossible to imagine a world in which buildings get built without blueprints, but it's still common for software applications to be designed and built without blueprints, or in this case, design patterns.    A software design pattern can be identified as &quot;a recurring solution to a recurring problem.&quot; Using design patterns for software development makes sense in the same way that architectural design patterns make sense--if it works well in one place, why not use it in another?  But developers have had enough of books that simply catalog design patterns without extending into new areas, and books that are so theoretical that you can't actually do anything better after reading them than you could before you started.    Crawford and Kaplan's <em>J2EE Design Patterns</em> approaches the subject in a unique, highly practical and pragmatic way. Rather than simply present another catalog of design patterns, the authors broaden the scope by discussing ways to choose design patterns when building an enterprise application from scratch, looking closely at the real world tradeoffs that Java developers must weigh when architecting their applications. Then they go on to show how to apply the patterns when writing realworld software.  They also extend design patterns into areas not covered in other books, presenting original patterns for data modeling, transaction / process modeling, and interoperability.     <em>J2EE Design Patterns</em> offers extensive coverage of the five problem areas enterprise developers face:&lt;ul&gt;  &lt;li&gt;Maintenance (Extensibility)&lt;/li&gt;  &lt;li&gt;Performance (System Scalability)&lt;/li&gt;  &lt;li&gt;Data Modeling (Business Object Modeling)&lt;/li&gt;  &lt;li&gt;Transactions (process Modeling)&lt;/li&gt;  &lt;li&gt;Messaging (Interoperability)&lt;/li&gt;&lt;/ul&gt;  And with its careful balance between theory and practice, <em>J2EE Design Patterns</em> will give developers new to the Java enterprise development arena a solid understanding of how to approach a wide variety of architectural and procedural problems, and will give experienced J2EE pros an opportunity to extend and improve on their existing experience. ]]>
  </description>
  <published>2003</published>
</book>

    <rating>0</rating>
  <votes>0</votes>
  <spoiler_flag>false</spoiler_flag>
  <shelves>
        <shelf name="read" />
          </shelves>
  <recommended_for><![CDATA[]]></recommended_for>
  <recommended_by><![CDATA[]]></recommended_by>
  <read_at></read_at>
  <date_added>Wed Apr 22 08:40:41 -0700 2009</date_added>
  <date_updated>Wed Apr 22 08:40:41 -0700 2009</date_updated>
  <read_count></read_count>
    <body><![CDATA[]]></body>
    
  <url><![CDATA[http://www.goodreads.com/review/show/53587492]]></url>
  <link><![CDATA[http://www.goodreads.com/review/show/53587492]]></link>
</review>
      <review>
  <id>31728024</id>
    <user>
    <id>1483035</id>
    <name><![CDATA[Mamonu]]></name>
    <location><![CDATA[Greece]]></location>
    <link><![CDATA[http://www.goodreads.com/user/show/1483035-mamonu]]></link>
    <image_url><![CDATA[http://photo.goodreads.com/users/1220290327p3/1483035.jpg]]></image_url>
    <small_image_url><![CDATA[http://photo.goodreads.com/users/1220290327p2/1483035.jpg]]></small_image_url>
  </user>
    <book>
  <id type="integer">347733</id>
  <isbn>0596004273</isbn>
  <isbn13>9780596004279</isbn13>
  <text_reviews_count type="integer">0</text_reviews_count>
  <title>
    <![CDATA[J2EE Design Patterns]]>
  </title>
  <image_url>http://photo.goodreads.com/books/1173938506m/347733.jpg</image_url>
  <small_image_url>http://photo.goodreads.com/books/1173938506s/347733.jpg</small_image_url>
  <link>http://www.goodreads.com/book/show/347733.J2EE_Design_Patterns</link>
  <average_rating>3.00</average_rating>
  <ratings_count>2</ratings_count>
  <description>
    <![CDATA[Architects of buildings and architects of software have more in common than most people think. Both professions require attention to detail, and both practitioners will see their work collapse around them if they make too many mistakes.  It's impossible to imagine a world in which buildings get built without blueprints, but it's still common for software applications to be designed and built without blueprints, or in this case, design patterns.    A software design pattern can be identified as &quot;a recurring solution to a recurring problem.&quot; Using design patterns for software development makes sense in the same way that architectural design patterns make sense--if it works well in one place, why not use it in another?  But developers have had enough of books that simply catalog design patterns without extending into new areas, and books that are so theoretical that you can't actually do anything better after reading them than you could before you started.    Crawford and Kaplan's <em>J2EE Design Patterns</em> approaches the subject in a unique, highly practical and pragmatic way. Rather than simply present another catalog of design patterns, the authors broaden the scope by discussing ways to choose design patterns when building an enterprise application from scratch, looking closely at the real world tradeoffs that Java developers must weigh when architecting their applications. Then they go on to show how to apply the patterns when writing realworld software.  They also extend design patterns into areas not covered in other books, presenting original patterns for data modeling, transaction / process modeling, and interoperability.     <em>J2EE Design Patterns</em> offers extensive coverage of the five problem areas enterprise developers face:&lt;ul&gt;  &lt;li&gt;Maintenance (Extensibility)&lt;/li&gt;  &lt;li&gt;Performance (System Scalability)&lt;/li&gt;  &lt;li&gt;Data Modeling (Business Object Modeling)&lt;/li&gt;  &lt;li&gt;Transactions (process Modeling)&lt;/li&gt;  &lt;li&gt;Messaging (Interoperability)&lt;/li&gt;&lt;/ul&gt;  And with its careful balance between theory and practice, <em>J2EE Design Patterns</em> will give developers new to the Java enterprise development arena a solid understanding of how to approach a wide variety of architectural and procedural problems, and will give experienced J2EE pros an opportunity to extend and improve on their existing experience. ]]>
  </description>
  <published>2003</published>
</book>

    <rating>4</rating>
  <votes>0</votes>
  <spoiler_flag>false</spoiler_flag>
  <shelves>
        <shelf name="read" />
            <shelf name="java" />
      </shelves>
  <recommended_for><![CDATA[]]></recommended_for>
  <recommended_by><![CDATA[]]></recommended_by>
  <read_at></read_at>
  <date_added>Mon Sep 01 09:35:23 -0700 2008</date_added>
  <date_updated>Mon Sep 01 09:35:23 -0700 2008</date_updated>
  <read_count></read_count>
    <body><![CDATA[]]></body>
    
  <url><![CDATA[http://www.goodreads.com/review/show/31728024]]></url>
  <link><![CDATA[http://www.goodreads.com/review/show/31728024]]></link>
</review>
      <review>
  <id>29129439</id>
    <user>
    <id>1392044</id>
    <name><![CDATA[Nuno]]></name>
    <location><![CDATA[Porto, Portugal]]></location>
    <link><![CDATA[http://www.goodreads.com/user/show/1392044-nuno-mariz]]></link>
    <image_url><![CDATA[http://photo.goodreads.com/users/1218103860p3/1392044.jpg]]></image_url>
    <small_image_url><![CDATA[http://photo.goodreads.com/users/1218103860p2/1392044.jpg]]></small_image_url>
  </user>
    <book>
  <id type="integer">347733</id>
  <isbn>0596004273</isbn>
  <isbn13>9780596004279</isbn13>
  <text_reviews_count type="integer">0</text_reviews_count>
  <title>
    <![CDATA[J2EE Design Patterns]]>
  </title>
  <image_url>http://photo.goodreads.com/books/1173938506m/347733.jpg</image_url>
  <small_image_url>http://photo.goodreads.com/books/1173938506s/347733.jpg</small_image_url>
  <link>http://www.goodreads.com/book/show/347733.J2EE_Design_Patterns</link>
  <average_rating>3.00</average_rating>
  <ratings_count>2</ratings_count>
  <description>
    <![CDATA[Architects of buildings and architects of software have more in common than most people think. Both professions require attention to detail, and both practitioners will see their work collapse around them if they make too many mistakes.  It's impossible to imagine a world in which buildings get built without blueprints, but it's still common for software applications to be designed and built without blueprints, or in this case, design patterns.    A software design pattern can be identified as &quot;a recurring solution to a recurring problem.&quot; Using design patterns for software development makes sense in the same way that architectural design patterns make sense--if it works well in one place, why not use it in another?  But developers have had enough of books that simply catalog design patterns without extending into new areas, and books that are so theoretical that you can't actually do anything better after reading them than you could before you started.    Crawford and Kaplan's <em>J2EE Design Patterns</em> approaches the subject in a unique, highly practical and pragmatic way. Rather than simply present another catalog of design patterns, the authors broaden the scope by discussing ways to choose design patterns when building an enterprise application from scratch, looking closely at the real world tradeoffs that Java developers must weigh when architecting their applications. Then they go on to show how to apply the patterns when writing realworld software.  They also extend design patterns into areas not covered in other books, presenting original patterns for data modeling, transaction / process modeling, and interoperability.     <em>J2EE Design Patterns</em> offers extensive coverage of the five problem areas enterprise developers face:&lt;ul&gt;  &lt;li&gt;Maintenance (Extensibility)&lt;/li&gt;  &lt;li&gt;Performance (System Scalability)&lt;/li&gt;  &lt;li&gt;Data Modeling (Business Object Modeling)&lt;/li&gt;  &lt;li&gt;Transactions (process Modeling)&lt;/li&gt;  &lt;li&gt;Messaging (Interoperability)&lt;/li&gt;&lt;/ul&gt;  And with its careful balance between theory and practice, <em>J2EE Design Patterns</em> will give developers new to the Java enterprise development arena a solid understanding of how to approach a wide variety of architectural and procedural problems, and will give experienced J2EE pros an opportunity to extend and improve on their existing experience. ]]>
  </description>
  <published>2003</published>
</book>

    <rating>0</rating>
  <votes>0</votes>
  <spoiler_flag>false</spoiler_flag>
  <shelves>
        <shelf name="read" />
          </shelves>
  <recommended_for><![CDATA[]]></recommended_for>
  <recommended_by><![CDATA[]]></recommended_by>
  <read_at></read_at>
  <date_added>Sun Aug 03 10:47:46 -0700 2008</date_added>
  <date_updated>Sun Aug 03 10:47:46 -0700 2008</date_updated>
  <read_count></read_count>
    <body><![CDATA[]]></body>
    
  <url><![CDATA[http://www.goodreads.com/review/show/29129439]]></url>
  <link><![CDATA[http://www.goodreads.com/review/show/29129439]]></link>
</review>
      <review>
  <id>19778439</id>
    <user>
    <id>977766</id>
    <name><![CDATA[terababy]]></name>
    <location><![CDATA[Beijing, China]]></location>
    <link><![CDATA[http://www.goodreads.com/user/show/977766-terababy]]></link>
    <image_url><![CDATA[http://photo.goodreads.com/users/1232561900p3/977766.jpg]]></image_url>
    <small_image_url><![CDATA[http://photo.goodreads.com/users/1232561900p2/977766.jpg]]></small_image_url>
  </user>
    <book>
  <id type="integer">347733</id>
  <isbn>0596004273</isbn>
  <isbn13>9780596004279</isbn13>
  <text_reviews_count type="integer">0</text_reviews_count>
  <title>
    <![CDATA[J2EE Design Patterns]]>
  </title>
  <image_url>http://photo.goodreads.com/books/1173938506m/347733.jpg</image_url>
  <small_image_url>http://photo.goodreads.com/books/1173938506s/347733.jpg</small_image_url>
  <link>http://www.goodreads.com/book/show/347733.J2EE_Design_Patterns</link>
  <average_rating>3.00</average_rating>
  <ratings_count>2</ratings_count>
  <description>
    <![CDATA[Architects of buildings and architects of software have more in common than most people think. Both professions require attention to detail, and both practitioners will see their work collapse around them if they make too many mistakes.  It's impossible to imagine a world in which buildings get built without blueprints, but it's still common for software applications to be designed and built without blueprints, or in this case, design patterns.    A software design pattern can be identified as &quot;a recurring solution to a recurring problem.&quot; Using design patterns for software development makes sense in the same way that architectural design patterns make sense--if it works well in one place, why not use it in another?  But developers have had enough of books that simply catalog design patterns without extending into new areas, and books that are so theoretical that you can't actually do anything better after reading them than you could before you started.    Crawford and Kaplan's <em>J2EE Design Patterns</em> approaches the subject in a unique, highly practical and pragmatic way. Rather than simply present another catalog of design patterns, the authors broaden the scope by discussing ways to choose design patterns when building an enterprise application from scratch, looking closely at the real world tradeoffs that Java developers must weigh when architecting their applications. Then they go on to show how to apply the patterns when writing realworld software.  They also extend design patterns into areas not covered in other books, presenting original patterns for data modeling, transaction / process modeling, and interoperability.     <em>J2EE Design Patterns</em> offers extensive coverage of the five problem areas enterprise developers face:&lt;ul&gt;  &lt;li&gt;Maintenance (Extensibility)&lt;/li&gt;  &lt;li&gt;Performance (System Scalability)&lt;/li&gt;  &lt;li&gt;Data Modeling (Business Object Modeling)&lt;/li&gt;  &lt;li&gt;Transactions (process Modeling)&lt;/li&gt;  &lt;li&gt;Messaging (Interoperability)&lt;/li&gt;&lt;/ul&gt;  And with its careful balance between theory and practice, <em>J2EE Design Patterns</em> will give developers new to the Java enterprise development arena a solid understanding of how to approach a wide variety of architectural and procedural problems, and will give experienced J2EE pros an opportunity to extend and improve on their existing experience. ]]>
  </description>
  <published>2003</published>
</book>

    <rating>0</rating>
  <votes>0</votes>
  <spoiler_flag>false</spoiler_flag>
  <shelves>
        <shelf name="read" />
            <shelf name="j2ee" />
      </shelves>
  <recommended_for><![CDATA[]]></recommended_for>
  <recommended_by><![CDATA[]]></recommended_by>
  <read_at></read_at>
  <date_added>Wed Apr 09 00:11:14 -0700 2008</date_added>
  <date_updated>Wed Apr 09 00:11:22 -0700 2008</date_updated>
  <read_count></read_count>
    <body><![CDATA[]]></body>
    
  <url><![CDATA[http://www.goodreads.com/review/show/19778439]]></url>
  <link><![CDATA[http://www.goodreads.com/review/show/19778439]]></link>
</review>
      <review>
  <id>7819053</id>
    <user>
    <id>552368</id>
    <name><![CDATA[notv]]></name>
    <location><![CDATA[The United States]]></location>
    <link><![CDATA[http://www.goodreads.com/user/show/552368-notv]]></link>
    <image_url><![CDATA[http://www.goodreads.com/images/nophoto-U-111x148.jpg]]></image_url>
    <small_image_url><![CDATA[http://www.goodreads.com/images/nophoto-U-50x66.jpg]]></small_image_url>
  </user>
    <book>
  <id type="integer">347733</id>
  <isbn>0596004273</isbn>
  <isbn13>9780596004279</isbn13>
  <text_reviews_count type="integer">0</text_reviews_count>
  <title>
    <![CDATA[J2EE Design Patterns]]>
  </title>
  <image_url>http://photo.goodreads.com/books/1173938506m/347733.jpg</image_url>
  <small_image_url>http://photo.goodreads.com/books/1173938506s/347733.jpg</small_image_url>
  <link>http://www.goodreads.com/book/show/347733.J2EE_Design_Patterns</link>
  <average_rating>3.00</average_rating>
  <ratings_count>2</ratings_count>
  <description>
    <![CDATA[Architects of buildings and architects of software have more in common than most people think. Both professions require attention to detail, and both practitioners will see their work collapse around them if they make too many mistakes.  It's impossible to imagine a world in which buildings get built without blueprints, but it's still common for software applications to be designed and built without blueprints, or in this case, design patterns.    A software design pattern can be identified as &quot;a recurring solution to a recurring problem.&quot; Using design patterns for software development makes sense in the same way that architectural design patterns make sense--if it works well in one place, why not use it in another?  But developers have had enough of books that simply catalog design patterns without extending into new areas, and books that are so theoretical that you can't actually do anything better after reading them than you could before you started.    Crawford and Kaplan's <em>J2EE Design Patterns</em> approaches the subject in a unique, highly practical and pragmatic way. Rather than simply present another catalog of design patterns, the authors broaden the scope by discussing ways to choose design patterns when building an enterprise application from scratch, looking closely at the real world tradeoffs that Java developers must weigh when architecting their applications. Then they go on to show how to apply the patterns when writing realworld software.  They also extend design patterns into areas not covered in other books, presenting original patterns for data modeling, transaction / process modeling, and interoperability.     <em>J2EE Design Patterns</em> offers extensive coverage of the five problem areas enterprise developers face:&lt;ul&gt;  &lt;li&gt;Maintenance (Extensibility)&lt;/li&gt;  &lt;li&gt;Performance (System Scalability)&lt;/li&gt;  &lt;li&gt;Data Modeling (Business Object Modeling)&lt;/li&gt;  &lt;li&gt;Transactions (process Modeling)&lt;/li&gt;  &lt;li&gt;Messaging (Interoperability)&lt;/li&gt;&lt;/ul&gt;  And with its careful balance between theory and practice, <em>J2EE Design Patterns</em> will give developers new to the Java enterprise development arena a solid understanding of how to approach a wide variety of architectural and procedural problems, and will give experienced J2EE pros an opportunity to extend and improve on their existing experience. ]]>
  </description>
  <published>2003</published>
</book>

    <rating>0</rating>
  <votes>0</votes>
  <spoiler_flag>false</spoiler_flag>
  <shelves>
        <shelf name="read" />
            <shelf name="j2ee" />
      </shelves>
  <recommended_for><![CDATA[]]></recommended_for>
  <recommended_by><![CDATA[]]></recommended_by>
  <read_at></read_at>
  <date_added>Tue Oct 16 17:59:36 -0700 2007</date_added>
  <date_updated>Tue Oct 16 17:59:36 -0700 2007</date_updated>
  <read_count></read_count>
    <body><![CDATA[]]></body>
    
  <url><![CDATA[http://www.goodreads.com/review/show/7819053]]></url>
  <link><![CDATA[http://www.goodreads.com/review/show/7819053]]></link>
</review>
    </reviews>
  <popular_shelves>
          <shelf name="j2ee" />
          <shelf name="to-read" />
          <shelf name="java" />
      </popular_shelves>
  <book_links>
    <book_link>
  <id>8</id>
  <name><![CDATA[WorldCat]]></name>
  <link>http://www.goodreads.com/book_link/follow/8?book_id=347733</link>
</book_link>
  </book_links>
</book>
</GoodreadsResponse>