3 Replies Latest reply on Nov 3, 2009 12:14 AM by clerum

    pages.xml validation errors

    clerum

      I'm trying to get my pages.xml to validate and I'm running into two validation issues that I can't get past.


      <page view-id="/admin/search/search.xhtml">
         <description>Search Results</description>
         <action execute="#{search.doSearch}">
            <begin-conversation/>
         </action>
      </page>
      


      Says cvc-complex-type.2.1: Element 'action' must have no character or element information item [children], because the type's content type is empty.


      and


      <page view-id="/admin/org_add.xhtml">
         <description>Add Organization</description>
         <navigation from-action="#{organizationUtil.addOrg()}">
            <rule if-outcome="true">
            <redirect view-id="/admin/org_list.xhtml" />
               <end-conversation before-redirect="true"/>     
            </rule>                         
         </navigation>
      </page>
      



      Errors with cvc-complex-type.2.4.d: Invalid content was found starting with element 'end-conversation'. No child element is expected at this point.


      Looking at XSD File it I think I'm OK with my syntax but maybe I'm missing something obvious.


      Any ideas?

        • 1. Re: pages.xml validation errors
          valatharv
          Is it <navigation from-action="#{organizationUtil.addOrg()}">
          OR
          <navigation from-action="#{organizationUtil.addOrg}">

          This sample works fine in my case...
          <navigation from-action="#{itemHome.addItem}">
               <rule if-outcome="addItemError">
                    <redirect view-id="/error.xhtml">
                         <message severity="error">
                              Message : Error occurred while adding item.                    
                         </message>
                    </redirect>
               </rule>
          </navigation>
          • 2. Re: pages.xml validation errors
            clerum

            They actual code works fine. It's the XML validation that is the issue.

            • 3. Re: pages.xml validation errors
              clerum