<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: implement DAO pattern in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/implement-dao-pattern/m-p/6610723#M1438897</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I don't have an coded example here, but isn't it sufficient for this pattern  to build an interface with some get- and set-methods? This interface can be implemented by several classes with different data retrieval logic. Then a static factory-method could do the job to decide during runtime which actual class is instantiated, returning the interface.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 15 Feb 2010 21:48:16 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2010-02-15T21:48:16Z</dc:date>
    <item>
      <title>implement DAO pattern</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/implement-dao-pattern/m-p/6610722#M1438896</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;In my application I have some database tables with a persistency class. Some other objects are implemented by calling the service bus, some others are implemented by function modules.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I want that the developer doesn't need to know where the object is coming from.&lt;/P&gt;&lt;P&gt;Therefore I want to implement the DAO pattern (Data Access Object).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm new on abap objects, so can somebody give me a working example or blog, or guidelines how to code this pattern?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 15 Feb 2010 11:22:29 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/implement-dao-pattern/m-p/6610722#M1438896</guid>
      <dc:creator>mmgc_riel</dc:creator>
      <dc:date>2010-02-15T11:22:29Z</dc:date>
    </item>
    <item>
      <title>Re: implement DAO pattern</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/implement-dao-pattern/m-p/6610723#M1438897</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I don't have an coded example here, but isn't it sufficient for this pattern  to build an interface with some get- and set-methods? This interface can be implemented by several classes with different data retrieval logic. Then a static factory-method could do the job to decide during runtime which actual class is instantiated, returning the interface.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 15 Feb 2010 21:48:16 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/implement-dao-pattern/m-p/6610723#M1438897</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2010-02-15T21:48:16Z</dc:date>
    </item>
    <item>
      <title>Re: implement DAO pattern</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/implement-dao-pattern/m-p/6610724#M1438898</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I created a few class like you described and it works.&lt;/P&gt;&lt;P&gt;Now i'm going to implement the factory class.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 16 Feb 2010 07:37:23 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/implement-dao-pattern/m-p/6610724#M1438898</guid>
      <dc:creator>mmgc_riel</dc:creator>
      <dc:date>2010-02-16T07:37:23Z</dc:date>
    </item>
  </channel>
</rss>

