Migrating Custom XPath Functions, XSLT Stylesheets, Java Classes or JRuby Scripts for Mashups
You can define custom XPath functions and add them to the Presto Server to perform specific formatting or calculations in mashups. These XPath functions are implemented as Java classes that are deployed as class or JAR files in the external configuration folder or in the Presto Server.
You can also use mashups to wrap POJO services or use Java classes or JRuby scripts within mashups to handle custom logic. The code for these extensions is also deployed in the external configuration folder or in the Presto Server.
You can also call XSLT stylesheets to perform transformations on mashup data using the <xslt> statement. These stylesheets are also deployed in theexternal configuration folder or in the Presto Server.
All of these mashup extensions must be deployed in your migration target:
If you have deployed these extensions in an external configuration folder, you can simply add this folder to the classpath for the application server hosting your migration target or create an external configuration folder for the target and copy these extensions. See
Setting Up an External
Presto
Configuration Folder for more information.
If you deployed these extensions in either:
source-web-apps-home/presto/WEB-INF/classes source-web-apps-home/presto/WEB-INF/lib Simply copy them to the target external configuration folder or to these folders in the target Presto Server, respectively:
target-web-apps-home/presto/WEB-INF/classes target-web-apps-home/presto/WEB-INF/lib If you use JRuby scripts, you must also install and configure JRuby for the migration target.
See Installing and Configuring JRuby for Mashups for instructions.