Torsten Curdt wrote:
I have an interal pipeline which sometimes throws an exception due to broken links.
<map:pipeline> <map:generate type="html" src="get/{1}"/> <map:serialize type="xml"/> <map:handle-errors> <map:generate src="default.xml"/> <map:serialize type="xml"/> </map:handle-errors> </map:pipeline>
And another one using it
<map:pipeline> <map:generate src="whatever.xml"/> <map:transform type="cinclude"/> --> calls the intenal pipeline ... </map:pipeline>
Using the first pipeline works just fine. Exceptions are being caught and a default xml file is being presented instead.
Unfortunately using it through the second pipeline (through the cinclude transformer) brings up the exception.
Anyone a clue what's happing here?
IIRC, last first friday we had a chat with Carsten about adding an attribute to the <handle-errors/> or to the <pipeline/> which will indicate what behavior is needed in case of internal request: throw exception or process <handle-errors/>. Carsten?
Vadim
