search

macressler / alfresco-bulk-filesystem-import

Automatically exported from code.google.com/p/alfresco-bulk-filesystem-import
GNU Lesser General Public License v3.0
1 stars 0 forks source link

an error accrued while importing file with custom aspect shadow file. #115

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1.New model and some aspects created using form-model management tool
http://addons.alfresco.com/addons/alfresco-form-model-management

2.files and it's shadows created as attached

3.Then i performed the bulk import. 

What is the expected output? 
success of bulk process as it was succeeded without shadow files.

What do you see instead?
failed with the attached error

What version of the product are you using? On what operating system?
Bulk importer :Alfresco Bulk Filesystem Import v1.1 (for Alfresco 4.0
Alfresco: 4.2.b
OS Windows 7

Please provide any additional information below.
Thank you in advance

Original issue reported on code.google.com by ahmedsam...@gmail.com on 9 Dec 2012 at 2:49

Attachments:

GoogleCodeExporter commented 9 years ago 
The error message is pretty clear about what the problem is:

    Class {ras.model}myModel has not been defined in the data dictionary

This could mean a couple of things:
1. there's a typo in the shadow metadata file - the way to verify this is to 
ensure the type "myModel" in the namespace "{ras.model}" appears in the model 
file
2. the model itself hasn't been deployed to Alfresco correctly - there's no 
straightforward way to check this, but basically you'll want to try to use the 
type "{ras.model}myModel" from somewhere other than the import tool (e.g. a 
form, a repo script, a Java program, etc.)

It's also possible there's a bug in the import tool that means the type name is 
being corrupted somehow, but given how long this logic has been available and 
has functioned correctly, that's unlikely.

Original comment by pmo...@gmail.com on 10 Dec 2012 at 4:11

GoogleCodeExporter commented 9 years ago 
Thank you, I'll check the mentioned factors + form-model designer the
and feedback.

Original comment by ahmedsam...@gmail.com on 12 Dec 2012 at 9:09

GoogleCodeExporter commented 9 years ago 
Ahmed, any update on your progress?

Original comment by pmo...@gmail.com on 3 Jan 2013 at 3:28

GoogleCodeExporter commented 9 years ago 
See issue 116 for details on new debug logging that should help troubleshoot 
this kind of issue.

Original comment by pmo...@gmail.com on 11 Jan 2013 at 11:01

GoogleCodeExporter commented 9 years ago 
Hello,
Thank you for your response
The problem has been resolved by using the main (inherited) content model 
instead of myModel and myModel is registered as a property not as class.

Regards,
Ahmed Samak

Original comment by ahmedsam...@gmail.com on 13 Jan 2013 at 6:43

GoogleCodeExporter commented 9 years ago

Original comment by pmo...@gmail.com on 13 Jan 2013 at 5:26