<?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: Architecture in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/architecture/m-p/88278#M59892</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;BLOCKQUOTE class="jive-quote"&gt;There are several other presentations and whitepapers in other areas of the community which are also helpful.&lt;/BLOCKQUOTE&gt;&lt;BR /&gt;&lt;SPAN&gt;Ahem.&amp;nbsp; This rather gives an example of what is, for me, an enormous problem with Alfresco's use of JSF: by the time I've followed that link and logged in, JSF/Alfresco has no idea where I wanted to be in the first place.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;As for ordinary users being able to exchange bookmarks … I'm really not convinced that I can deploy a system where training is required to do something so basic!&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 27 Jun 2007 17:29:04 GMT</pubDate>
    <dc:creator>sacco</dc:creator>
    <dc:date>2007-06-27T17:29:04Z</dc:date>
    <item>
      <title>Architecture</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/architecture/m-p/88275#M59889</link>
      <description>Hi,&amp;nbsp; We need to learn how works the Alfresco's architecture. The main topic we need to study is the layer of presentation and how to work with the beans and jsp pages.&amp;nbsp; &amp;nbsp; Who knows something?</description>
      <pubDate>Wed, 18 Apr 2007 15:32:18 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/architecture/m-p/88275#M59889</guid>
      <dc:creator>kaerdsar</dc:creator>
      <dc:date>2007-04-18T15:32:18Z</dc:date>
    </item>
    <item>
      <title>Re: Architecture</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/architecture/m-p/88276#M59890</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;BR /&gt;&lt;SPAN&gt;I think the best starting point to understand Alfresco's webapp is to have a deep knowledge of JSF. Alrfresco engineers applied JSF concepts in a very clean way and added their own set of components and renderers. They also extended key JSF mechanisms like the navigation handler (to introduce their dialog and wizard framework like explained in the Wiki) or the variable resolver (to link JSF backing beans and Spring configuration).&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;The configuration layer Alfresco added on top of this is less documented from an architecture point of view (more examples, less schemas).&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 26 Apr 2007 08:55:43 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/architecture/m-p/88276#M59890</guid>
      <dc:creator>rivarola</dc:creator>
      <dc:date>2007-04-26T08:55:43Z</dc:date>
    </item>
    <item>
      <title>Re: Architecture</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/architecture/m-p/88277#M59891</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;BLOCKQUOTE class="jive-quote"&gt;Hello,&lt;BR /&gt;&lt;BR /&gt;I think the best starting point to understand Alfresco's webapp is to have a deep knowledge of JSF. Alrfresco engineers applied JSF concepts in a very clean way and added their own set of components and renderers. They also extended key JSF mechanisms like the navigation handler (to introduce their dialog and wizard framework like explained in the Wiki) or the variable resolver (to link JSF backing beans and Spring configuration).&lt;BR /&gt;The configuration layer Alfresco added on top of this is less documented from an architecture point of view (more examples, less schemas).&lt;/BLOCKQUOTE&gt;&lt;BR /&gt;&lt;SPAN&gt;Rivarola gives some hints in understanding the framework from a application perspective.&amp;nbsp; Another good place to look is in the content community – Sumer Jabri and Jeff Potts have contributed presentations which help to parse the architecture. These presentations can be found under user groups.&amp;nbsp; There are several other presentations and whitepapers in other areas of the community which are also helpful.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://www.alfresco.com/products/whitepapers/" rel="nofollow noopener noreferrer"&gt;http://www.alfresco.com/products/whitepapers/&lt;/A&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 26 Apr 2007 20:14:10 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/architecture/m-p/88277#M59891</guid>
      <dc:creator>rdanner</dc:creator>
      <dc:date>2007-04-26T20:14:10Z</dc:date>
    </item>
    <item>
      <title>Re: Architecture</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/architecture/m-p/88278#M59892</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;BLOCKQUOTE class="jive-quote"&gt;There are several other presentations and whitepapers in other areas of the community which are also helpful.&lt;/BLOCKQUOTE&gt;&lt;BR /&gt;&lt;SPAN&gt;Ahem.&amp;nbsp; This rather gives an example of what is, for me, an enormous problem with Alfresco's use of JSF: by the time I've followed that link and logged in, JSF/Alfresco has no idea where I wanted to be in the first place.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;As for ordinary users being able to exchange bookmarks … I'm really not convinced that I can deploy a system where training is required to do something so basic!&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 27 Jun 2007 17:29:04 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/architecture/m-p/88278#M59892</guid>
      <dc:creator>sacco</dc:creator>
      <dc:date>2007-06-27T17:29:04Z</dc:date>
    </item>
  </channel>
</rss>

