<?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: PersonService implementation confusion in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/personservice-implementation-confusion/m-p/36056#M18980</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hi&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;We do use people and expect them to be in the repository.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Some config hangs off it etc …. at the moment&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;The intention is to do the same with groups.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I think you should sync from your registration system to the repoitory, in the same way that we sync people and group information from LDAP.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Then leave these two services alone.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;If your service handles requests from a lof of apps you are probably better of doing this in any case. It will also reduce the amount of repository external traffic.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Hope this helps&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Andy&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 18 May 2006 15:47:26 GMT</pubDate>
    <dc:creator>andy</dc:creator>
    <dc:date>2006-05-18T15:47:26Z</dc:date>
    <item>
      <title>PersonService implementation confusion</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/personservice-implementation-confusion/m-p/36055#M18979</link>
      <description>I'm looking to write my own PersonService implementation to get Person information from a custom registration system.Based on the comments in the PersonService.java (below), I thought this could be done without storing person properties in Alfresco.—This service encapsulates the management of people</description>
      <pubDate>Wed, 17 May 2006 19:16:58 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/personservice-implementation-confusion/m-p/36055#M18979</guid>
      <dc:creator>ethanadams</dc:creator>
      <dc:date>2006-05-17T19:16:58Z</dc:date>
    </item>
    <item>
      <title>Re: PersonService implementation confusion</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/personservice-implementation-confusion/m-p/36056#M18980</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hi&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;We do use people and expect them to be in the repository.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Some config hangs off it etc …. at the moment&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;The intention is to do the same with groups.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I think you should sync from your registration system to the repoitory, in the same way that we sync people and group information from LDAP.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Then leave these two services alone.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;If your service handles requests from a lof of apps you are probably better of doing this in any case. It will also reduce the amount of repository external traffic.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Hope this helps&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Andy&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 18 May 2006 15:47:26 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/personservice-implementation-confusion/m-p/36056#M18980</guid>
      <dc:creator>andy</dc:creator>
      <dc:date>2006-05-18T15:47:26Z</dc:date>
    </item>
  </channel>
</rss>

