2010/10/21

WSO2 Carbon Studio: How to point to a resource from your Sequence

  • Saminda Wijeratne
  • Senior Software Engineer - WSO2 Inc
  • 21 Oct, 2010

Applies To

Projects: ESB, Carbon Studio

Solution

  1. Double click on the XSLT mediator node
  2. In the Properties view select the value of the "XSLT Key" property.
  3. A small button will appear at the end of the value field. Click on that button.
  4. "Registry Key Property Editor" dialog will appear.
    • case 1: The xslt is already in the registry which you want to deploy the sequence
      • case 1.1: The registry which the xslt contains is not reachable via the current host
        • Specify the registry path in the "Key" textbox
      • case 1.2: The registry is reachable via the current host
        • Use the "Browse Remote Registry" section to browse and select for the path os the XSLT.
    • case 2: The xslt is already in a registry which is not where you will deploy the sequence
      • Specify in the "Key" textbox the registry path which later you would want the XSLT to be saved in the registry of the carbon server which you are going to deploy the sequence
    • case 3: The xslt is present as a C-App registry resource artifact in the same C-App project
      • Specify the registry path which would resolve in the "Key" textbox to the XSLT file through the C-App registry resource artifact
    • case 4: The xslt is in the local file system
      • Specify the registry path which you want the XSLT to reside in the "Key" textbox once it is deployed to the registry
  5. Click OK
  6. If case 2 or 4
    • In this scenario you need to retrieve the XSLT file and create a C-App registry resource artifact
    • Open the artifact.xml of the sequence C-App artifact
    • Click "Create New Artifact" and select "Registry Resource"
    • case 2:
      • Select "Check-out from registry" option
      • Browse and specify the path to the xslt file
      • Note:
        • If it's not possible to reach the registry from the host, try downloading the file manually and saving it to the local file system. Then follow case 4
    • case 4:
      • Select "File" option and click "Browse"
      • Select the XSLT file
      • Specify the parent path of the XSLT file which you mentioned in the "Registry Key Property Editor" dialog
      • Click "Next" in the wizard and specify a name for the C-App registry resource artifact.
      • Click "Finish".
  7. if case 2,3,4
    • Under the local dependencies of the artifact.xml of the sequence C-App artifact tick/check the C-App registry resource artifact if it is already not so
    • Save the artifact.xml

    

Author : Saminda Wijeratne, Product Manager WSO2 Tools, WSO2 Inc, [email protected]

 

 

 

About Author

  • Saminda Wijeratne
  • Senior Software Engineer
  • WSO2 Inc