i've got a strange problem with the latest xalan-2.2dev and namespaces.
i've got these three pipelines set up:
<map:match pattern="foo">
<map:generate src="content/form.xml"/>
<map:transform type="inspection">
<map:parameter name="schema"
value="context://WEB-INF/etc/tables.xml"/>
<map:parameter name="table" value="event_table"/>
</map:transform>
<map:serialize type="xml"/>
</map:match>
<map:match pattern="bar">
<map:generate src="content/form.xml"/>
<map:transform type="inspection">
<map:parameter name="schema"
value="context://WEB-INF/etc/tables.xml"/>
<map:parameter name="table" value="event_table"/>
</map:transform>
<map:transform src="style/v2/index.xsl"/>
<map:serialize type="html"/>
</map:match>
<map:match pattern="bat">
<map:generate src="foo"/>
<map:transform src="style/v2/index.xsl"/>
<map:serialize type="html"/>
</map:match>
the 'bar' pipeline is what i'd ideally like to end up working. it
generates a skeletal page from a file, expands some dynamic tags using my
InspectionTransformer, and transforms those results using xalan, and
renders the results as html. unfortunately, it doesn't work properly - the
stylesheet doesn't give me the expected output, it seems to ignore a large
chunk of its input, or think that the namespace that chunk belongs to is
different than it actually is.
the weird thing is, if i save the output from the pipeline up to the xalan
transformation ('foo'), and then use that to initiate a new pipeline that
just calls xalan and serializes the results as html ('bat') everything
works fine. also, if i remove the namespace declarations from everywhere,
it works fine.
i can't make heads or tails of this. can anyone suggest a possible
debugging strategy?
- donald
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
