<?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: Upgrade to 4.0.a failing using the maven alfresco lifecycle in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/upgrade-to-4-0-a-failing-using-the-maven-alfresco-lifecycle/m-p/251203#M204333</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I think I know what caused this problem now. However since I tried to start with a vanilla war instead (which applied all patches) before reverting to my maven built war I not 100% sure yet. &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;My guess is however that the reason lies in that i had both alfrescoNtlm and ldap-ad configured in my authentication-chain and the ldap.authentication flag set to false. (since I'm not using this in my development environment). The stacktrace indicates that the authenticationService was not correctly injected by spring and with some debugging I found out that it was the ldap authentication subsystem component that was throwing the error. For some reason Alfresco uses the subsystem in some way although its set to false.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;/Erik&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 14 Oct 2011 08:42:06 GMT</pubDate>
    <dc:creator>billerby</dc:creator>
    <dc:date>2011-10-14T08:42:06Z</dc:date>
    <item>
      <title>Upgrade to 4.0.a failing using the maven alfresco lifecycle</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/upgrade-to-4-0-a-failing-using-the-maven-alfresco-lifecycle/m-p/251202#M204332</link>
      <description>I'm using the maven alfresco way of building my war (http://wiki.alfresco.com/wiki/Managing_Alfresco_Lifecyle_with_Maven).I have installed all alfresco 4.0.a artifacts in my local repository. The alfresco war is built without errors but one of the upgrade patches fails when I start the container:If</description>
      <pubDate>Thu, 13 Oct 2011 08:28:28 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/upgrade-to-4-0-a-failing-using-the-maven-alfresco-lifecycle/m-p/251202#M204332</guid>
      <dc:creator>billerby</dc:creator>
      <dc:date>2011-10-13T08:28:28Z</dc:date>
    </item>
    <item>
      <title>Re: Upgrade to 4.0.a failing using the maven alfresco lifecycle</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/upgrade-to-4-0-a-failing-using-the-maven-alfresco-lifecycle/m-p/251203#M204333</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I think I know what caused this problem now. However since I tried to start with a vanilla war instead (which applied all patches) before reverting to my maven built war I not 100% sure yet. &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;My guess is however that the reason lies in that i had both alfrescoNtlm and ldap-ad configured in my authentication-chain and the ldap.authentication flag set to false. (since I'm not using this in my development environment). The stacktrace indicates that the authenticationService was not correctly injected by spring and with some debugging I found out that it was the ldap authentication subsystem component that was throwing the error. For some reason Alfresco uses the subsystem in some way although its set to false.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;/Erik&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 14 Oct 2011 08:42:06 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/upgrade-to-4-0-a-failing-using-the-maven-alfresco-lifecycle/m-p/251203#M204333</guid>
      <dc:creator>billerby</dc:creator>
      <dc:date>2011-10-14T08:42:06Z</dc:date>
    </item>
  </channel>
</rss>

