Carsten Ziegeler wrote:

Vadim Gritsenko wrote:


It could be convinient if it would work. But it does not.

 <map:generator name="filteredFile">
   <map:aggregate>
     <map:part src="a"/>
     <map:part src="b"/>
     <map:part src="c"/>
   </map:aggregate>
   <map:transform type="xslt" src="a.xsl"/>
   <map:transform type="xslt" src="b.xsl"/>
 </map:generator>



It works :)

You can then:

<map:generate type="filteredFile">
<map:parameter name="source-a" value="A"/>
<map:parameter name="source-b" value="B"/> <map:parameter name="source-c" value="C"/>
</map:generate>


with



<map:generator name="filteredFile">
<map:aggregate>
<map:part src="{source-a}"/>
<map:part src="{source-c}"/>
<map:part src="{source-b}"/>
</map:aggregate>
<map:transform type="xslt" src="a.xsl"/>
<map:transform type="xslt" src="b.xsl"/>
</map:generator>


You could also add two parameters for the stylesheets etc.

But, if you write
<map:generate type="filteredFile" src="something">

then you can access it automatically as {src} rather than
writing
<map:generate type="filteredFile">
 <map:parameter name="src" value="something"/>


With clarifications given -- no objections. I agree with this idea.


Vadim




Reply via email to