I seem to be no longer able to check out a Template file (XSL in our case) that it associated with a Web Form in the Data Dictionary. When I try to check out a template I see the error message:
Unable to check out Content Node due to system error:Unknown Exception in Transaction.
In the log file I see:
INFO | jvm 1 | 2007/07/05 13:49:34 | 13:49:34,885 ERROR [node.integrity.IntegrityChecker] Found 1 integrity violations: INFO | jvm 1 | 2007/07/05 13:49:34 | The association parent multiplicity has been violated: INFO | jvm 1 | 2007/07/05 13:49:34 | Target Node: workspace://SpacesStore/97727a66-28a1-11dc-9a06-7f728efa622d INFO | jvm 1 | 2007/07/05 13:49:34 | Association: Association[ class=ClassDef[name={http://www.alfresco.org/model/wcmappmodel/1.0}renderingenginetemplate], name={http://www.alfresco.org/model/wcmappmodel/1.0}renditionproperties, target class={http://www.alfresco.org/model/wcmappmodel/1.0}renditionproperties, source role={http://www.alfresco.org/model/wcmappmodel/1.0}capture, target role=null] INFO | jvm 1 | 2007/07/05 13:49:34 | Required parent Multiplicity: 0..1 INFO | jvm 1 | 2007/07/05 13:49:34 | Actual parent Multiplicity: 2 INFO | jvm 1 | 2007/07/05 13:49:35 | 13:49:34,946 ERROR [ui.common.Utils] Unable to check out Content Node due to system error:Unknown Exception in Transaction. INFO | jvm 1 | 2007/07/05 13:49:35 | org.alfresco.error.AlfrescoRuntimeException: Unknown Exception in Transaction. INFO | jvm 1 | 2007/07/05 13:49:35 | at org.alfresco.repo.transaction.RetryingTransactionHelper.doInTransaction(RetryingTransactionHelper.java:292) INFO | jvm 1 | 2007/07/05 13:49:35 | at org.alfresco.repo.transaction.RetryingTransactionHelper.doInTransaction(RetryingTransactionHelper.java:155) INFO | jvm 1 | 2007/07/05 13:49:35 | at org.alfresco.web.bean.CheckinCheckoutBean.checkoutFile(CheckinCheckoutBean.java:529)
I am running Alfresco 2.1R1 Community on Linux using MySQL.
PS: this happens for all Templates and all Web Forms. I even tested this with the "motd" example Web Form and Template.
PPS: I have no problem updating the content definition file (XSD) itself. Only the associated template.
As a workaround, until that bug is addressed, you can simply use the Update action to upload a new version of your XSL (although it won't have been properly checked out first).
