8 Replies Latest reply on Dec 29, 2011 12:11 AM by manimatters

    How to sign a hybrid extension?

    Anatoly Paraev Level 1


      I need to package and sign a hybrid extension (an extension that includes a CSXS-based Flex extension and a native C++ event adapter for Illustrator). Following the instructions given here: http://help.adobe.com/en_US/extensionmanager/cs/using/packaging_extension.pdf, I do the following:

      1. Build a Flex-based extension and package it into a signed ZXP file using the Extension Builder export function
      2. Build a native event adapter plug-in for Illustrator
      3. Prepare an .mxi file for my extension, which lists both the flex packaged .zxp-file (with the file-type="csxs" keyword) and the native plug-in (with the file-type="ordinary" keyword).
      4. Open the created .mxi file with Extension Manager and create a wrapper .zxp file.

      Now I need to sign the resulting wrapper .zxp file. The above mentioned document says the following: “For information on digitally signing extensions, refer to the Creative Suite SDK: http://www.adobe.com/devnet/creativesuite/sdk”
      On the SDK webpage I have found the link to Creative Suite 5 Extension Packaging and Signing Toolkit, which basically is the ucf.jar tool and a pdf file with a minimal set of instructions. The instructions are very poor - they do not explain how to use the tool, do not list all the arguments of the tool and do not explain the meaning of those arguments. As far as I understand, I cannot use the ucf.jar tool to just sign an already packaged extension - I have to package it first.
      Is this correct? Is there a way to sign an extension without re-packaging it?
      Thank you in advance,