Re: [xsl] Parametrized includes -work-around?

[Ralph Holz <ralph.holz@xxxxxxxxxxxxxxxxxxxx>]

Hi,

> I don't understand. You can change the way the transformation is invoked to
> supply an extra parameter, but you can't change it to modify the entry point
> of the transformation?

Ok, here's our scenario. The framework is based on strutscx, the output
data is XSL-FO. I need to add that we are merely extending the
framework, it's not ours.

An incoming request to the server contains information about the source
data and the transformations needed.

So far, two static stylesheets were sufficient: A and B.

A provides a basic FO layout.

B is selected according to the "transformation needed" information and
provides some basic templates to be executed on the XML tree. It includes A.

So far, so good.

Now we need to include the option to add more templates (say C and D) to
the transformation process, keeping A and B in place. That would be the
"dynamic includes". The information which ones to use additionally is
also given in the request.

Your solution would suggest to remove B from its place in the
transformation pipeline and put (C+D) there. These would then include B
(and subsequently A).

This is a modification of the framework that we might need to discuss
with our client first (because other services might depend on it).

Doing a two-step transformation seems easier at this points. We consider
doing the first part (constructing the stylesheet that performs the
actual transformation) as part of the strutscx action.

Happy weekend,
Ralph