Hide Forgot
Created attachment 824271 [details] partial server.log Description of problem: CopyTrans fails when invoked by pushing document from client Version-Release number of selected component (if applicable): Zanata version 3.2-SNAPSHOT (20131114-1743) How reproducible: Pretty consistent, I think. Steps to Reproduce: 1. Use zanata-cli to push a document, with copytrans enabled Actual results: Client log: [INFO] pushing source doc [name=authconfig size=251] to server Done in 0 secs [INFO] Running Copy Trans for authconfig Done in 0 secs [WARN] Copy Trans for the above document stopped unexpectedly. Server log: see attachment Expected results: CopyTrans successful, no error logged Additional info:
I think this is caused by new changes in the uses of 'Activity ' when pushing source documents. Copy trans from the UI doesn't seem to be affected, but it's worth testing it too. All hibernate entities that are used inside Work implementations should be loaded from inside the work invocation. Similarly, and we are more conscious of this, any Seam component instance used inside an AsyncTask implementation should be loaded from within the async call and not passed in. See: https://github.com/zanata/zanata-server/pull/274
See instead: https://github.com/zanata/zanata-server/pull/275
VERIFIED with Zanata version 3.2-SNAPSHOT (20131118-1242) zanata-maven-plugin:3.1.2