<?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: adapter class in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/adapter-class/m-p/3889489#M934253</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Just go through below link&lt;/P&gt;&lt;P&gt;&lt;A class="jive_macro jive_macro_thread" href="https://community.sap.com/" __jive_macro_name="thread" modifiedtitle="true" __default_attr="755810"&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I hpe it helps u.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sun, 01 Jun 2008 14:54:13 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2008-06-01T14:54:13Z</dc:date>
    <item>
      <title>adapter class</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/adapter-class/m-p/3889488#M934252</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi what is adapter class.what is the use of it&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 01 Jun 2008 04:41:38 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/adapter-class/m-p/3889488#M934252</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-06-01T04:41:38Z</dc:date>
    </item>
    <item>
      <title>Re: adapter class</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/adapter-class/m-p/3889489#M934253</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Just go through below link&lt;/P&gt;&lt;P&gt;&lt;A class="jive_macro jive_macro_thread" href="https://community.sap.com/" __jive_macro_name="thread" modifiedtitle="true" __default_attr="755810"&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I hpe it helps u.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 01 Jun 2008 14:54:13 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/adapter-class/m-p/3889489#M934253</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-06-01T14:54:13Z</dc:date>
    </item>
    <item>
      <title>Re: adapter class</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/adapter-class/m-p/3889490#M934254</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Adapters enable the Integration Engine and the Partner Connectivity Kit (PCK) to communicate with different applications.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Adapters connect the Integration Engine to SAP legacy systems, as well as to external systems.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In this way, adapters integrate existing SAP components with SAP Exchange Infrastructure, for example. In the process, XML and HTTP-based documents are converted to IDocs (IDoc adapter) and RFCs (RFC adapter) and the other way around. This enables you to integrate your existing SAP infrastructure with the new SAP infrastructure, which is based on system integration and the exchange of XML messages.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;pls check this link.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_nw04/helpdata/en/0d/5ab43b274a960de10000000a114084/content.htm" target="test_blank"&gt;http://help.sap.com/saphelp_nw04/helpdata/en/0d/5ab43b274a960de10000000a114084/content.htm&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 02 Jun 2008 09:20:26 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/adapter-class/m-p/3889490#M934254</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-06-02T09:20:26Z</dc:date>
    </item>
    <item>
      <title>Re: adapter class</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/adapter-class/m-p/3889491#M934255</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In computer programming, the adapter design pattern (often referred to as the wrapper pattern or simply a wrapper) 'adapts' one interface for a class into one that a client expects. An adapter allows classes to work together that normally could not because of incompatible interfaces by wrapping its own interface around that of an already existing class. The adapter is also responsible for handling any logic necessary to transform data into a form that is useful for the consumer. For instance, if multiple boolean values are stored as a single integer but your consumer requires a 'true'/'false', the adapter would be responsible for extracting the appropriate values from the integer value.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Structure:&lt;/P&gt;&lt;P&gt;There are two types of adapter patterns:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Object Adapter pattern  &lt;/P&gt;&lt;P&gt;In this type of adapter pattern, the adapter contains an instance of the class it wraps. In this situation, the adapter makes calls to the instance of the wrapped object.                                                                                &lt;/P&gt;&lt;P&gt;ADAPTEE&lt;/P&gt;&lt;P&gt;                                                                                +methodB ( )&lt;/P&gt;&lt;P&gt;                                                                                ^                                                                                &lt;/P&gt;&lt;TABLE&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;                                                            CLIENT             -&lt;/P&gt;&lt;HR originaltext="------------------" /&gt;&lt;P&gt;&amp;gt;    ADAPTER&lt;/P&gt;&lt;P&gt;                                                       +adapter : adapter                       +adaptee : adaptee&lt;/P&gt;&lt;P&gt;                                                       +doWork ( )                                 +methodA ( )&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;P&gt;                                                               &lt;/P&gt;&lt;TABLE&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;P&gt;                                                              V                                                 V&lt;/P&gt;&lt;P&gt;                                                    adapter.methodA ( ) ;                   adapter.methodB ( );&lt;/P&gt;&lt;P&gt;                                                        &lt;/P&gt;&lt;P&gt;The object adapter pattern expressed in UML. The adapter hides the adaptee's interface from the client.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For more detail explaination with diagrams refer the following link:&lt;/P&gt;&lt;P&gt;&lt;A href="http://en.wikipedia.org/wiki/Wrapper_pattern#Sample_-_Class_Adapter" target="test_blank"&gt;http://en.wikipedia.org/wiki/Wrapper_pattern#Sample_-_Class_Adapter&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Reward points if my attempt made you to understand what an adapter class is.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Sekhar&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 02 Jun 2008 10:29:56 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/adapter-class/m-p/3889491#M934255</guid>
      <dc:creator>former_member188594</dc:creator>
      <dc:date>2008-06-02T10:29:56Z</dc:date>
    </item>
  </channel>
</rss>

