[ALF-9783] Export does not work if node have residual property Created: 04-Aug-11  Updated: 29-Jul-16  Resolved: 29-Jul-16

Status: Closed
Project: Alfresco
Component/s: None
Affects Version/s: 3.4 Enterprise
Fix Version/s: None
Security Level: external (External user)

Type: Bug Priority: Major
Reporter: Martin Bergljung (Inactive) Assignee: Closed Issues
Resolution: Won't Fix Votes: 2
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Windows 64bit


Issue Links:
Duplicate
Date of First Response:

 Description   

If a node (folder or content) has one or more residual properties such as:

{urn:schemas-microsoft-com:}

Win32FileAttributes 00000000

{http://www.alfresco.org/model/cmis/1.0/cs01}

id true

Then the Export function will not work, it says urn:schemas-microsoft-com namespace is not known.



 Comments   
Comment by Mark Rogers [X] (Inactive) [ 05-Oct-11 ]

Exception is:

18:31:58,292

{http-8080-4}

ERROR [org.alfresco.web.ui.common.Utils] A system error happened during the operation: A namespace prefix is not registered for uri fruitloops.woz.ere
org.alfresco.service.namespace.NamespaceException: A namespace prefix is not registered for uri fruitloops.woz.ere
at org.alfresco.service.namespace.QName.toPrefixString(QName.java:414)
at org.alfresco.repo.exporter.ViewXMLExporter.toPrefixString(ViewXMLExporter.java:797)
at org.alfresco.repo.exporter.ViewXMLExporter.startProperty(ViewXMLExporter.java:482)
at org.alfresco.repo.exporter.URLExporter.startProperty(URLExporter.java:180)
at org.alfresco.repo.exporter.ChainedExporter.startProperty(ChainedExporter.java:224)
at org.alfresco.repo.exporter.ExporterComponent$DefaultCrawler.walkNode(ExporterComponent.java:466)
at org.alfresco.repo.exporter.ExporterComponent$DefaultCrawler.export(ExporterComponent.java:287)
at org.alfresco.repo.exporter.ExporterComponent.exportView(ExporterComponent.java:207)
at org.alfresco.repo.exporter.ExporterComponent.exportView(ExporterComponent.java:192)

So how to do anything about this? Unfortunatly ACP format makes heavy use of alfresco prefixes so residual properties don't fit.

Comment by Mark Rogers [X] (Inactive) [ 06-Oct-11 ]

So some options to consider.
a) Do not write out residual properties at all.

b) Add a "residual" namespace with some extra properties on the property e.g namespace and type.
<cm:contains>
<cm:person view:childName="cm:fredb" view:id="fred">
<view:aspects/>
<view:properties>
<cm:userName>${username}</cm:userName>
<cm:firstName>Fred</cm:firstName>
<cm:lastName>Bloggs</cm:lastName>
<cm:homeFolder>../../cm:people_x0020_folder</cm:homeFolder>
<residual:trouble residualNamespace="

{foo.bar}

" typeName="String">${username}</residual:trouble>
</view:properties>
</cm:person>
</cm:contains>

c) dynamically create a namspace prefix for namespaces not known by the namespace service
<view:properties>
<cm:userName>${username}</cm:userName>
<cm:firstName>Fred</cm:firstName>
<cm:lastName>Bloggs</cm:lastName>
<cm:homeFolder>../../cm:people_x0020_folder</cm:homeFolder>
<residual1:trouble>${username}</residual1:trouble>
</view:properties>
</cm:person>
</cm:contains>

Comment by Derek Hulley [X] (Inactive) [ 07-Feb-12 ]

Features and bugs for import/export might be considered as part of ALF-10819.

Comment by Nick Nagels (Inactive) [ 02-Feb-14 ]

Also reproduced on Enterprise 4.1 . What is the origin of the urn:schemas-microsoft-com properties?

Comment by Richard Esplin [X] (Inactive) [ 29-Jul-16 ]

This issue was reported against a version of Alfresco Enterprise Edition that is in Limited Support. Alfresco Software will not implement further enhancements or improvements for products or versions in this support state. If this issue is impacting your deployment of Alfresco One Enterprise Edition, please contact support so that we can assist you. Customers with a support contract can request a bug fix in certain cases.

Current releases of Alfresco contain many improvements that address old problems. We are closing old issues so that we can better prioritize our efforts.

If you verify that the issue still exists in the latest release of Alfresco Community Edition, please reopen the issue. If you have any trouble reopening the issue, then leave a comment or email us at community@alfresco.com so that we can assist.

Thank you for collaborating with us on improving Alfresco.

Generated at Thu Aug 05 14:26:19 BST 2021 using Jira 7.13.15#713015-sha1:7c5ddd2c3e1709974ae9c48c17df8edd3919fe2c.