Localized Scenario Management

[nmshah]

Hello,

I work with a good number of XSLs and XSLs represent screens of applications. So I expect number of scenarios to grow quite a bit.

The current product I use, Stylus Studio, has a very good feature where scenarios are not at project level but at XSL level so that when I open my XSL I only see scenarios applicable to that XSL - which is very useful if I have lots of XSL and each having few scenarios

oxygen is a great product and it would be really good for people working with a good number of XSLs in the project to have this freature

thanks
Nilesh

[george]

Hi Nilesh,

oXygen provides a few macros that you can use when configuring a transformation scenario, thus allowing to make them more generic. That might help you reduce the number of scenarios and also the need to configure a lot of scenarios. For instance you can have a generic scenario that applies a transformation taking as imput an XML file with the same name as the stylesheet but with the XML extension. For that you can use something like:

${cfdu}/${cfn}.xml

as the input for the scenario.

Hope that helps,
George