<?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 WDR Deployment Target - alfresco in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/wdr-deployment-target-alfresco/m-p/231545#M184675</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hello,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;In Alfresco 3.2, the Web Delivery Runtime deployment engine was introduced. Amongst the preconfigured deployment targets is the DM deployment target: alfresco.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;I am lacking a bit of understanding as to what the functions of the DM deployment target are. Deploying from DM to WCM will be very useful but what advantages exist for deploying from WCM to DM? I'm sure there is a good reason for this, but, please, shed some light &lt;img id="smileyhappy" class="emoticon emoticon-smileyhappy" src="https://connect.hyland.com/i/smilies/16x16_smiley-happy.png" alt="Smiley Happy" title="Smiley Happy" /&gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thank you.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 20 Jan 2010 01:31:30 GMT</pubDate>
    <dc:creator>lilyh</dc:creator>
    <dc:date>2010-01-20T01:31:30Z</dc:date>
    <item>
      <title>WDR Deployment Target - alfresco</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/wdr-deployment-target-alfresco/m-p/231545#M184675</link>
      <description>Hello,In Alfresco 3.2, the Web Delivery Runtime deployment engine was introduced. Amongst the preconfigured deployment targets is the DM deployment target: alfresco.I am lacking a bit of understanding as to what the functions of the DM deployment target are. Deploying from DM to WCM will be very use</description>
      <pubDate>Wed, 20 Jan 2010 01:31:30 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/wdr-deployment-target-alfresco/m-p/231545#M184675</guid>
      <dc:creator>lilyh</dc:creator>
      <dc:date>2010-01-20T01:31:30Z</dc:date>
    </item>
    <item>
      <title>Re: WDR Deployment Target - alfresco</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/wdr-deployment-target-alfresco/m-p/231546#M184676</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Its the other way around "WCM authoring" deploying to "alfresco".&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;There's a few reasons, some of them better than others :?&amp;nbsp; &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Here's some of my reasons&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;a) because the deployment refactorings of 3.0 and Community 3.2 have made it far easier to implement.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;b) because the content is then available via CMIS rather than bespoke or alfresco specific interfaces.&amp;nbsp; &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;c) because it gives access to the other alfresco services like transformation.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 20 Jan 2010 10:20:56 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/wdr-deployment-target-alfresco/m-p/231546#M184676</guid>
      <dc:creator>mrogers</dc:creator>
      <dc:date>2010-01-20T10:20:56Z</dc:date>
    </item>
  </channel>
</rss>

