I’ll be at the O’Reilly Open Source Conference in San Jose this week. After so much time spent at conferences like AIIM and KMWorld, where open source is sorely under-represented, it’ll be nice to be surrounded by nothing but. I’m looking forward to sessions on Liferay Expanse, Django, Spring, Erlang (here and here), and many more. If you’re going, be sure to give me a shout.
5 comments
Comments are closed.
Hi there.
I’ve a question but is not related with this post. I’m trying to do my custom model in Alfresco 3.2. To start I try to use the code you write from someco. I copied the necessary files (the files in bin/alfresco/extension) to my alfresco extension directory. I didn’t make any change… I simply copied the files.
But, for example, if I try to create content, I don’t have the types doc and whitepaper available in type.
Is this a problem generated by the alfresco 3.2 version? Did you try your code with the last version?
Thanks
Luis
hi again… I looked at to my alfresco.log and find:
[org.alfresco.web.bean.actions.BaseActionWizard] Failed to resolve aspect ‘sc:webable’
[org.alfresco.web.bean.actions.BaseActionWizard] Failed to resolve aspect ‘sc:productRelated’
Is this normal?
The code works fine with 3.2 Community with the following exceptions:
– In Chapter 4, a new mime type definition is added for Microsoft Project. In 3.1.1 Enterprise and 3.2 Community, Alfresco provides this, so an error will be produced if you also try to define it.
– In Chapter 4, the MS Project-to-text transformer uses MPXJ. Alfresco has upgraded the version of POI it uses which means that MPXJ needs to be upgraded to 3.0.0.
I am still testing the Chapter 9 source code with 3.2 Community. When that’s done, I’ll release updated source code that is tagged by specific version (as it is now it is just “Enterprise” versus “Labs”).
So, long story short, no, you should not be seeing problems with those aspects. Make sure your model context file points to your Someco model XML file and that you’ve defined those aspects properly.
Jeff
Hi I get the same error while trying to add a custom aspect from the ui thru Web Client Extension.
15:22:12,058 WARN [org.alfresco.web.bean.actions.BaseActionWizard] Failed to resolve aspect ‘sample:temporal’
Vidya,
This message indicates that you’ve defined a new custom aspect called “sample:temporal” but the aspect isn’t registered with Alfresco. If you look in your log, you should see that it was either ignore completely or that there was a problem parsing your content model.
If it was ignored completely, my guess is that your content model context XML doesn’t point to your custom content model XML.
Jeff