<?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: AWMUtil tightly coupled with FacesContext in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/awmutil-tightly-coupled-with-facescontext/m-p/150296#M105181</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;AVMUtil is a client side class and thus presumes that a JSF context is available. A scheduled job runs in the context of the repository (server) and so as you have found can not access or create the FacesContext.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Unfortunately, the config you are trying to access was put in the wrong place, it really belongs to the deployment action and should therefore be configured in Spring. This has been rectified in 2.2 (and now HEAD) where deployment has been overhauled, but that doesn't help you much &lt;span class="lia-unicode-emoji" title=":disappointed_face:"&gt;😞&lt;/span&gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;If you can't move to 2.2 (which is only in beta at the moment) or a current nightly build then you'll have to create a config service bean that reads in the relevant config file (web-client-config-wcm.xml) and inject it into your scheduled job.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 18 Feb 2008 17:23:26 GMT</pubDate>
    <dc:creator>gavinc</dc:creator>
    <dc:date>2008-02-18T17:23:26Z</dc:date>
    <item>
      <title>AWMUtil tightly coupled with FacesContext</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/awmutil-tightly-coupled-with-facescontext/m-p/150295#M105180</link>
      <description>I am trying to use the AWMUtil from within a quartz scheduled job but because the AVMUtil requires a FacesContext some exceptions are been thrown:java.lang.IllegalArgumentException: FacesContext must not be null&amp;nbsp;&amp;nbsp;&amp;nbsp; at org.springframework.util.Assert.notNull(Assert.java:113)&amp;nbsp;&amp;nbsp;&amp;nbsp; at org.springframework</description>
      <pubDate>Sat, 16 Feb 2008 10:43:45 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/awmutil-tightly-coupled-with-facescontext/m-p/150295#M105180</guid>
      <dc:creator>ebo</dc:creator>
      <dc:date>2008-02-16T10:43:45Z</dc:date>
    </item>
    <item>
      <title>Re: AWMUtil tightly coupled with FacesContext</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/awmutil-tightly-coupled-with-facescontext/m-p/150296#M105181</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;AVMUtil is a client side class and thus presumes that a JSF context is available. A scheduled job runs in the context of the repository (server) and so as you have found can not access or create the FacesContext.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Unfortunately, the config you are trying to access was put in the wrong place, it really belongs to the deployment action and should therefore be configured in Spring. This has been rectified in 2.2 (and now HEAD) where deployment has been overhauled, but that doesn't help you much &lt;span class="lia-unicode-emoji" title=":disappointed_face:"&gt;😞&lt;/span&gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;If you can't move to 2.2 (which is only in beta at the moment) or a current nightly build then you'll have to create a config service bean that reads in the relevant config file (web-client-config-wcm.xml) and inject it into your scheduled job.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 18 Feb 2008 17:23:26 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/awmutil-tightly-coupled-with-facescontext/m-p/150296#M105181</guid>
      <dc:creator>gavinc</dc:creator>
      <dc:date>2008-02-18T17:23:26Z</dc:date>
    </item>
  </channel>
</rss>

