<?xml version="1.0" encoding="UTF-8"?>
 <rdf:RDF xmlns="http://purl.org/rss/1.0/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:cc="http://web.resource.org/cc/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://pinboard.in">
    <title>Pinboard (DennisLaumen)</title>
    <link>https://pinboard.in/u:DennisLaumen/public/</link>
    <description>recent bookmarks from DennisLaumen</description>
    <items>
      <rdf:Seq>	<rdf:li rdf:resource="http://code.google.com/p/google-web-toolkit/wiki/BeanValidation"/>
	<rdf:li rdf:resource="http://code.google.com/webtoolkit/articles/mvp-architecture.html"/>
      </rdf:Seq>
    </items>
  </channel><item rdf:about="http://code.google.com/p/google-web-toolkit/wiki/BeanValidation">
    <title>JSR 303 Bean Validation for GWT</title>
    <dc:date>2011-02-16T20:21:58+00:00</dc:date>
    <link>http://code.google.com/p/google-web-toolkit/wiki/BeanValidation</link>
    <dc:creator>DennisLaumen</dc:creator><description><![CDATA[GWT supports a subset of JSR 303 Bean Validation. At compile time GWT validation uses the same Validation Provider you use on the server to create a Validator for all your objects.]]></description>
<dc:subject>gwt softwaredevelopment webdevelopment jsr303 validation</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:DennisLaumen/b:60d0d291ae4a/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:DennisLaumen/t:gwt"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DennisLaumen/t:softwaredevelopment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DennisLaumen/t:webdevelopment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DennisLaumen/t:jsr303"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DennisLaumen/t:validation"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://code.google.com/webtoolkit/articles/mvp-architecture.html">
    <title>Google Web Toolkit: Large scale application development and MVP</title>
    <dc:date>2010-06-30T10:00:22+00:00</dc:date>
    <link>http://code.google.com/webtoolkit/articles/mvp-architecture.html</link>
    <dc:creator>DennisLaumen</dc:creator><description><![CDATA[Building any large scale application has its hurdles, and GWT apps are no exception. Multiple developers working simultaneously on the same code base, while maintaining legacy features and functionality, can quickly turn into messy code. To help sort things out we introduce design patterns to create compartmentalized areas of responsibility within our project.
There are various design patterns to choose from; Presentation-abstraction-control, Model-view-controller, Model-view-presenter, etc... And while each pattern has its benefits, we have found that a Model-view-presenter (MVP) architecture works best when developing GWT apps for two main reasons. First the MVP model, much like other design patterns, decouples development in a way that allows multiple developers to work simultaneously. Secondly, this model allows us to minimize our use of GWTTestCase and, for the bulk of our code, write lightweight (and fast) JRE tests.]]></description>
<dc:subject>gwt google java softwaredevelopment architecture modelviewpresenter</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:DennisLaumen/b:d3c3bf0ac9ec/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:DennisLaumen/t:gwt"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DennisLaumen/t:google"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DennisLaumen/t:java"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DennisLaumen/t:softwaredevelopment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DennisLaumen/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DennisLaumen/t:modelviewpresenter"/>
</rdf:Bag></taxo:topics>
</item>
</rdf:RDF>