cancel
Showing results for 
Search instead for 
Did you mean: 

[SOLVED] Unable to locate evaluator implementation for ...

mwildam
Champ in-the-making
Champ in-the-making
I get the following error when trying to access the web client after adding a custom aspect to alfresco configuration:
javax.faces.FacesException: javax.faces.FacesException: Could not retrieve value of component with path : {Component-Path : [Class: javax.faces.component.UIViewRoot,ViewId: /jsp/login.jsp][Class: javax.faces.component.html.HtmlForm,Id: loginForm][Class: javax.faces.component.html.HtmlInputText,Id: user-name]}
caused by:
org.apache.jasper.JasperException: javax.faces.FacesException: Could not retrieve value of component with path : {Component-Path : [Class: javax.faces.component.UIViewRoot,ViewId: /jsp/login.jsp][Class: javax.faces.component.html.HtmlForm,Id: loginForm][Class: javax.faces.component.html.HtmlInputText,Id: user-name]}
caused by:
javax.faces.FacesException: Could not retrieve value of component with path : {Component-Path : [Class: javax.faces.component.UIViewRoot,ViewId: /jsp/login.jsp][Class: javax.faces.component.html.HtmlForm,Id: loginForm][Class: javax.faces.component.html.HtmlInputText,Id: user-name]}
caused by:
javax.faces.el.EvaluationException: Cannot get value for expression '#{LoginBean.username}'
caused by:
javax.faces.el.EvaluationException: Cannot get value for expression '#{BrowseBean}'
caused by:
org.alfresco.config.ConfigException: Unable to locate evaluator implementation for 'apect-name' for org.alfresco.config.ConfigSectionImpl@109daf0 (evaluator=apect-name condition=custom:PartnerDetails replace=false)

Here are my files:
company-context.xml:
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE beans PUBLIC '-//SPRING//DTD BEAN//EN' 'http://www.springframework.org/dtd/spring-beans.dtd'>
<beans>
    <!– Registration of new models –>   
    <bean id="extension.dictionaryBootstrap" parent="dictionaryModelBootstrap" depends-on="dictionaryBootstrap">
        <property name="models">
            <list>
                <value>alfresco/extension/companyModel.xml</value>
            </list>
        </property>
    </bean>
</beans>

companyModel.xml:
<?xml version="1.0" encoding="UTF-8"?>

<!– Custom Model –>

<!– Note: This model is pre-configured to load at startup of the Repository.  So, all custom –>
<!–       types and aspects added here will automatically be registered –>

<model name="custom:companyModel" xmlns="http://www.alfresco.org/model/dictionary/1.0">

  <!– Optional meta-data about the model –>  
  <description>Company Model</description>
  <author></author>
  <version>1.0</version>

   <imports>
      <!– Import Alfresco Dictionary Definitions –>
    <import uri="http://www.alfresco.org/model/dictionary/1.0" prefix="d"/>
      <!– Import Alfresco Content Domain Model Definitions –>
      <import uri="http://www.alfresco.org/model/content/1.0" prefix="cm"/>
  </imports>

   <!– Introduction of new namespaces defined by this model –>
  <!– NOTE: The following namespace custom.model should be changed to reflect your own namespace –>
  <namespaces>
      <namespace uri="custom.model" prefix="custom"/>
  </namespaces>

   <aspects>
      <aspect name="custom:PartnerDetails">
         <title>Partner Details</title>
         <properties>
            <property name="custom:PartnerID">
               <title>Partner ID</title>
               <type>d:text</type>
               <protected>false</protected>
               <mandatory>false</mandatory>
               <multiple>false</multiple>
            </property>
            <property name="custom:PartnerName">
               <title>Partner Name</title>
               <type>d:text</type>
               <protected>false</protected>
               <mandatory>false</mandatory>
               <multiple>false</multiple>
            </property>
         </properties>
      </aspect>
      
      <aspect name="custom:ProjectDetails">
         <title>Project Details</title>
         <properties>
            <property name="custom:ProjectID">
               <title>Project ID</title>
               <type>d:text</type>
               <protected>false</protected>
               <mandatory>false</mandatory>
               <multiple>false</multiple>
            </property>
            <property name="custom:ProjectTitle">
               <title>Project Title</title>
               <type>d:text</type>
               <protected>false</protected>
               <mandatory>false</mandatory>
               <multiple>false</multiple>
            </property>
         </properties>
      </aspect>
   </aspects>
</model>

web-client-config-custom.xml:
<alfresco-config>
   <config evaluator="string-compare" condition="Action Wizards">
      <aspects>
         <aspect name="custom:PartnerDetails"/>
         <aspect name="custom:ProjectDetails"/>
      </aspects>
   </config>
   
   <config evaluator="apect-name" condition="custom:PartnerDetails">
      <property-sheet>
         <separator name="sepPartner1" display-label="Partner Details" component-generator="HeaderSeparatorGenerator"/>
         <show-property name="custom:PartnerID"/>
         <show-property name="custom:PartnerName"/>
      </property-sheet>
   </config>

   <config evaluator="apect-name" condition="custom:ProjectDetails">
      <property-sheet>
         <separator name="sepProject1" display-label="Project Details" component-generator="HeaderSeparatorGenerator"/>
         <show-property name="custom:ProjectID"/>
         <show-property name="custom:ProjectTitle"/>
      </property-sheet>
   </config>
   </alfresco-config>
I already searched the forum for such a problem but didn't find something that is equivalent to my problem. I also checked the wiki and a book we have bought. I found a bug in the bug tracker that seems somehow similar but not exactly (https://issues.alfresco.com/jira/browse/ETHREEOH-2260).

Anyone an idea what can be the reason?
1 REPLY 1

mwildam
Champ in-the-making
Champ in-the-making
Smiley Surprisedops: - the problem is visible already in the subject - it is a typo: it should be "aspect" and not "apect". I have consequently overlooked the typo.