Hello Senthilkumar,
I think we have the 2-factor based problem here.
1 is that you use Xalan instead of Saxon in your Pipeline (error log shows
xalan package info not saxon)
2. is that it might adhere to Saxon version that you use. Old Saxon had
many features that new Saxon does NOT have unless
HI,
I am currently migrating the cocoon 2.1 based project to 2.2, while I tried to
set it up with cocoon 2.2 I am running in to following issue while executing a
transform pipeline.
Could some on help me to fix this issue and provide your expert advice. Thanks
in advance.
I have tried with the
