This article will look at scripting languages that are not covered in the Xalan documentation, in particular, Python, VBScript, and PerlScript. In addition, we will show how Java Object instances, created in XSLT as part of the Java language extensions mechanism, are passed to these scripts and utilized by them. These samples will provide a solid foundation on which to build more complicated script-based extensions.
This requires the exact same configuration as that required for VBScript. In addition, the ActiveState Perl interpreter must be installed on the same machine as the stylesheet processor.
Simple Function without a JavaBean Parameter
The function below shows how PerlScript is used to calculate the surname output element using the name input element value.
sub calculate_surname { my ( $name ) = @_; @tokens = split(" ",$name); return @tokens[1]; }
The first line is not strictly necessary, but copying the parameters from the standard @_ parameters array into a list of named parameters makes the script more readable.
The function below shows how VBScript is used to calculate the bonus value. Again, as this is an ActiveScript, it requires the same workaround as before when passing JavaBean instances.
sub calculate_bonus { my ( $quota, $actual, $bonusplan, $bonus_table_bean_name ) = @_;
# set up lookup table variables $bonus_table = $bsf->lookupBean( $bonus_table_bean_name );
# find base bonus from lookup table $bonus_base = $bonus_table->lookUp($bonusplan,1) ;
# calculate multiple, bonus multiple is zero if they underperform $multiple = $actual > $quota ? $actual / $quota : 0.0 ;
return $bonus_base * $multiple; }
Because PerlScript is loosely typed, it is not necessary to convert the string retrieved from the lookup table into a float.