cancel
Showing results for 
Search instead for 
Did you mean: 

Content Modeling Parsing Error ( 02084835)

jjmierwa
Champ in-the-making
Champ in-the-making
Hi,

I'm very new to Alfresco so please bear with me. I have created a Content Model and am trying to install it for dynamic deployment by adding it into the Data Dictionary/Models page of Alfresco Explorer.

When I set the model to active in the Modify Content Properties page and select "OK", to do so, I get the following error message:
"Error  Please correct the errors below then click OK.
    A system error happened during the operation: 02084835 Failed to parse model"

Searching online yields no results. So the question is either how can I verify the correctness of the content model before trying to make it active, or how do I debug/interpret this error so that I can find out what is wrong with the model?
4 REPLIES 4

mrogers
Star Contributor
Star Contributor
You could start by adding your model to your posting above.   Or you could validate it against the xsd

And have you checked the log file?

jjmierwa
Champ in-the-making
Champ in-the-making
Thanks for the quick response.
With regards to logging, exactly where do I find the logs? I can find the tomcat logs but can not find the alfresco.log file anywhere. Is there something that I am missing in how to ensure that the logging is actually enabled?

With regards to validation against the schema, I tried to validate in Oxygen 13.2 but the schema itself fails validation with a UPA (Unique Particle Attribution) error in xerces as follows: "Description: cos-nonambig: "http://www.alfresco.org/model/dictionary/1.0':mandatory and "http://www.alfresco.org/model/dictionary/1.0':mandatory (or elements from their substitution group) violate "Unique Particle Attribution". During validation against this schema, ambiguity would be created for those two particles.", I didn't think that correcting the error in the schema would be prudent as I'm assuming that the app deals with that in some fashion.

The content model is below. It is a modified version of the kb.xml content model from the book Professional Alfresco (Caruana, Newton, et al). The kb.xml example model activates just fine.

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

<!–                              –>
<!– EFiling Filings Content Model –>
<!–                              –>

<model name="efile:contentmodel" xmlns="http://www.alfresco.org/model/dictionary/1.0">
   <!–
   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
   xsi:schemaLocation="http://www.alfresco.org/model/dictionary/1.0 file:/C:/Alfresco%20Code/book-website-chapters-1.0.0-SNAPSHOT/chapter05/modelSchema.xsd">
–>
   <!– Metadata about the model –>
   <description>EFiling Filing Event Content Model</description>
   <author>URL Integration</author>
   <version>1.0</version>

   <!– Imports are required to allow references to definitions in other models –>
   <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>

   <!– Define the URI and Prefix for this content model –>
   <namespaces>
      <namespace uri="http://www.urlintegration.com/efiling/documentmanagementsystem/model/dictionary/1.0" prefix="ef"/>
   </namespaces>

   <!– Define constraints –>
   <constraints>
        
      <!– Ensures that one of the allowed values is assigned –>
      <constraint name="efile:attachmenttype_constraint" type="LIST">
         <parameter name="allowedValues">
            <list>
               <value>Exhibit</value>
               <value>Other</value>
            </list>
         </parameter>
      </constraint>
     
   </constraints>

   <!– Content Types –>
   <types>
      <type name="efile:space">
         <title>Lake County Efiling Document Management System</title>
         <parent>cm:folder</parent>
      </type>

      <type name="efile:FilingDocumentAttachment">
         <title>Document Attachment</title>
         <parent>efile:FilingDocument</parent>
         <properties>
            <property name="efile:AttachmentCategory">
               <title>Attachment Type</title>
               <type>d:text</type>
               <default>Other</default>
               <constraints>
                   <constraint ref="efile:attachmenttype_constraint"/>
               </constraints>
            </property>
         </properties>
      </type>
      <type name="efile:FilingDocument">
         <title>Filing Document</title>
         <parent>cm:content</parent>
         <properties>
            <property name="efile:DocID">
               <title>Document ID</title>
               <type>d:text</type>
            </property>
            <property name="efile:CMSID">
               <title>Document CMS ID</title>
               <type>d:text</type>
            </property>
            <property name="efile:SequenceNumber">
               <title>Sequence Number</title>
               <type>d:text</type>
            </property>
            <property name="efile:DocumentType">
               <title>Document Type</title>
               <type>d:text</type>
            </property>
            <property name="efile:DocumentSubType">
               <title>Document Type</title>
               <type>d:text</type>
            </property>
            <child-association name="efile:documentAttachments">
               <target>
                  <class>efile:FilingDocumentAttachment</class>
                  <mandatory>false</mandatory>
                  <many>true</many>
               </target>
            </child-association>
         </properties>
      </type>
   </types>

   <!– Aspects –>
   <aspects>

      <!– Marks a content item as a KB Article –>
      <aspect name="efile:FilingEvent">
         <title>Filing</title>
         <properties>
        
            <!– Adds a new metadata property to the KB article –>
            <!– Constrains the value –>
            <property name="efile:CaseNumber">
               <title>Case Number</title>
               <type>d:text</type>
               <mandatory>true</mandatory>
            </property>
         </properties>

         <associations>
            <child-association name="efile:eventDocuments">
               <target>
                  <class>efile:FilingDocument</class>
                  <mandatory>false</mandatory>
                  <many>true</many>
               </target>
               <duplicate>true</duplicate>
            </child-association>
         </associations>
      </aspect>

   </aspects>

</model>

jjmierwa
Champ in-the-making
Champ in-the-making
Getting the logging going was a separate problem that also helped partially, but that's another story.

It turns out that somehow I had an older and invalid version of the model that I was originally trying to validate against. Using the version of the schema that was installed identified the error in the content model.

mitpatoliya
Star Collaborator
Star Collaborator
<namespaces>
          <namespace uri="http://www.urlintegration.com/efiling/documentmanagementsystem/model/dictionary/1.0" prefix="ef"/>
       </namespaces>

In above section replace "ef" with "efile"
Getting started

Tags


Find what you came for

We want to make your experience in Hyland Connect as valuable as possible, so we put together some helpful links.