Namespace prefix con is not mapped to a namespace URI

[Angelo Marques]

Boa tarde,

Eu crie dois novos types chamado markting e sop , os dois funcionam ,
quando vou adicionar um terceiro type , ele cria mostra nos types ,
mas não consigo alterar me mostra esse erro Namespace prefix con is
not mapped to a namespace URI. alguém já pegou esse erro ?

[Angelo Marques]

Segue o modelo e o share config


Share Config

<alfresco-config>

<!-- Global config section -->
<config replace="true">
<flags>
<!--
Developer debugging setting to turn on DEBUG mode for
client scripts in the browser
-->
<client-debug>false</client-debug>

<!--
LOGGING can always be toggled at runtime when in DEBUG
mode (Ctrl, Ctrl, Shift, Shift).
This flag automatically activates logging on page load.
-->
<client-debug-autologging>false</client-debug-autologging>
</flags>
</config>

<!-- Document Library config section -->
<config evaluator="string-compare" condition="DocumentLibrary"
replace="true">

<tree>
<!--
Whether the folder Tree component should enumerate child
folders or not.
This is a relatively expensive operation, so should be set
to "false" for Repositories with broad folder structures.
-->
<evaluate-child-folders>false</evaluate-child-folders>

<!--
Optionally limit the number of folders shown in treeview
throughout Share.
-->
<maximum-folder-count>-1</maximum-folder-count>
</tree>

<!--
Used by the "Manage Aspects" action

For custom aspects, remember to also add the relevant i18n
string(s)
cm_myaspect=My Aspect
-->

<!-- P A R T 1 -->
<types>
<type name="cm:content">
<!-- add our own custom type -->
<subtype name="mar:collateral" />
<subtype name="sop:sop" />
<subtype name="cm:UCOM_contratomodel" />
</type>

<type name="cm:content">
<subtype name="mar:collateral" />

</type>

<type name="cm:content">
<subtype name="cm:UCOM_contratomodel" />

</type>




<type name="sop:sop">
<!-- add our own custom type -->
<subtype name="cm:content" />
</type>


<type name="mar:collateral">
<subtype name="cm:content" />
</type>

<type name="cm:folder">
</type>
</types>

<!-- P A R T 2 -->
<aspects>
<!-- Aspects that a user can see -->
<visible>
<aspect name="cm:generalclassifiable" />
<aspect name="cm:complianceable" />
<aspect name="cm:summarizable" />
<aspect name="cm:versionable" />
<aspect name="cm:templatable" />
<aspect name="cm:emailed" />
<aspect name="emailserver:aliasable" />
<aspect name="cm:taggable" />
<aspect name="cm:dublincore" />
<aspect name="cm:effectivity" />
<aspect name="app:inlineeditable" />
<!-- show our own custom type -->
<aspect name="sop:autoReview" />
</visible>

<!-- Aspects that a user can add. Same as "visible" if
left empty -->
<addable>
</addable>

<!-- Aspects that a user can remove. Same as "visible" if
left empty -->
<removeable>
</removeable>
</aspects>


<!--
If set, will present a WebDAV link for the current item on
the Document and Folder details pages.
Also used to generate the "View in Alfresco Explorer" action
for folders.
-->
<repository-url>http://localhost:8080/alfresco</repository-url>

<!--
Google Docs™ integration
-->
<google-docs>
<!--
Enable/disable the Google Docs UI integration (Extra types
on Create Content menu, Google Docs actions).
If enabled, remember to also make sure the
gd:googleEditable aspect is made visible in the <aspects> section
above.
-->
<enabled>false</enabled>

<!--
The mimetypes of documents Google Docs allows you to
create via the Share interface.
The I18N label is created from the "type" attribute, e.g.
google-docs.doc=Google Docs&trade; Document
-->
<creatable-types>
<creatable type="doc">application/msword</creatable>
<creatable type="xls">application/vnd.ms-excel</creatable>
<creatable type="ppt">application/vnd.ms-powerpoint</
creatable>
</creatable-types>
</google-docs>
</config>

<!-- Repository Library config section -->
<config evaluator="string-compare" condition="RepositoryLibrary"
replace="true">
<!--
Whether the link to the Repository Library appears in the
header component or not.
-->
<visible>true</visible>

<!--
Root nodeRef for top-level folder.
-->
<root-node>alfresco://company/home</root-node>

<tree>
<!--
Whether the folder Tree component should enumerate child
folders or not.
This is a relatively expensive operation, so should be set
to "false" for Repositories with broad folder structures.
-->
<evaluate-child-folders>false</evaluate-child-folders>

<!--
Optionally limit the number of folders shown in treeview
throughout Share.
-->
<maximum-folder-count>500</maximum-folder-count>
</tree>
</config>

<!--
NTLM authentication config for Share
NOTE: you will also need to enable the NTLM authentication
filter in Share web.xml
change localhost:8080 below to appropriate alfresco
server location if required
-->

<!--
<config evaluator="string-compare" condition="Remote">
<remote>
<connector>
<id>alfrescoCookie</id>
<name>Alfresco Connector</name>
<description>Connects to an Alfresco instance using cookie-
based authentication</description>

<class>org.springframework.extensions.webscripts.connector.AlfrescoConnector</
class>
</connector>

<endpoint>
<id>alfresco</id>
<name>Alfresco - user access</name>
<description>Access to Alfresco Repository WebScripts that
require user authentication</description>
<connector-id>alfrescoCookie</connector-id>
<endpoint-url>http://localhost:8080/alfresco/wcs</endpoint-
url>
<identity>user</identity>
<external-auth>true</external-auth>
</endpoint>
</remote>
</config>
-->

<!-- example changing port used to access remote Alfresco server
(default is 8080)
<config evaluator="string-compare" condition="Remote">
<remote>
<endpoint>
<id>alfresco-noauth</id>
<name>Alfresco - unauthenticated access</name>
<description>Access to Alfresco Repository WebScripts that
do not require authentication</description>
<connector-id>alfresco</connector-id>
<endpoint-url>http://localhost:8080/alfresco/s</endpoint-
url>
<identity>none</identity>
</endpoint>

<endpoint>
<id>alfresco</id>
<name>Alfresco - user access</name>
<description>Access to Alfresco Repository WebScripts that
require user authentication</description>
<connector-id>alfresco</connector-id>
<endpoint-url>http://localhost:8080/alfresco/s</endpoint-
url>
<identity>user</identity>
</endpoint>

<endpoint>
<id>alfresco-feed</id>
<name>Alfresco Feed</name>
<description>Alfresco Feed - supports basic HTTP
authentication via the EndPointProxyServlet</description>
<connector-id>http</connector-id>
<endpoint-url>http://localhost:8080/alfresco/s</endpoint-
url>
<basic-auth>true</basic-auth>
<identity>user</identity>
</endpoint>
</remote>
</config>
-->
</alfresco-config>





Contrato Model


<?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="csm:UCOM_contratoModel" xmlns="http://www.alfresco.org/
model/dictionary/1.0">

<!-- Optional meta-data about the model -->
<description>COM_Contrato Model</description>
<author>Davi</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"/>
<!-- Import Alfresco Data List Model Definitions -->
<import uri="http://www.alfresco.org/model/datalist/1.0"
prefix="dl"/>
</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="marketing.green-energy-demo.com" prefix="cm"/>
</namespaces>


<constraints>

<constraint name="cm:produtos" type="LIST">

<parameter name="allowedValues">

<list>

<value>Licença</value>

<value>Treinamento</value>

<value>Servico</value>

</list>

</parameter>

</constraint>



</constraints>



<types>

<!-- Definition of new Content Type: Standard Operating
Procedure -->
<type name="cm:Contrato">
<title>Contrato</title>
<!-- This inherits from cm:content and thus has all the standard
content attributes -->
<parent>cm:content</parent>
<properties>
<!-- The properties as defined in our specification -->
<property name="cm:nomedocliente">
<description>Nome do Cliente</description>
<type>d:text</type>
</property>
<property name="cm:Numero do Contrato">
<description>Nome do Remetente</description>
<type>d:text</type>
</property>



<property name="cm:Produtos">

<title>Produtos</title>

<type>d:text</type>

<constraints>

<constraint ref="cm:produtos" />

</constraints>

</property>







</properties>


</type>

</types>



</model>