It probably doesn't help that your transformed variable goes out of scope before you try to use it.

Mike

I've got to agree with Mike

your transformation variable goes out of scope...

in place of:

	var m = node.mimetype;

	if (m.substr(0, 5) == "image") {

		// transform an image

		var transformed = node.transformImage(args.mimetype, outputFolder);

	} else {

		// transform a document

		var transformed = node.transformDocument(args.mimetype, outputFolder);

	}

 

try

	var m = node.mimetype;

       var transformed = null;

	if (m.substr(0, 5) == "image") {

		// transform an image

		transformed = node.transformImage(args.mimetype, outputFolder);

	} else {

		// transform a document

		transformed = node.transformDocument(args.mimetype, outputFolder);

	}

 

on the openoffice "issue" I can think of a lot of reasons why call back on soffice would be a mistake
for example: connection may be simply unavailable for a moment (busy... who knows?) calling on soffice again would only make soffice throw an erro, fill up more memory, make OS unstable (don't really know witch one)

one thing I've got to agree

when a tranformation failed, in some cases alfresco still keept the target node as if it worked so if you don't know about the transformation problem the user will believe that it was a success... don't know if this was corrected althoug

for the exception... use a java backed webscript... a try...catch block can handle that problem

this little bug is no big deal... talking about a storm in a glass of water

I have this problem too.

But I think this feature must be included in transformDocument function