Antonio Gallardo wrote: > Hi forresters! > > Seems like my "crazy" idea got accepted. ;-) > > http://issues.apache.org/bugzilla/show_bug.cgi?id=32360#c10 > > Do you think this is going to help us to fix this error? :-)
I don't profess to understand the issues involved. The final solution sounds like it will enable us to make a useful workaround ... an API to define non-standard things, e.g. context.setDefaultNamespaceIgnored(true) Interesting. That is similar to the workaround that i am currently trying to do, except from the Forrest end of things before Cocoon input modules and JXPath read our site.xml file. Thanks for your contributions. -David > >Antonio Gallardo commented on FOR-675: > >-------------------------------------- > > > >Interesting reading. Shows why the problems happens and posible solutions: > >http://www.xml.com/pub/a/2004/02/25/qanda.html > > > >>upgrading to commons-jxpath-1.2.jar causes failures with linkrewriter > >>protocols site: etc. > >>------------------------------------------------------------------------------------------ > >> > >> Key: FOR-675 > >> URL: http://issues.apache.org/jira/browse/FOR-675 > >> Project: Forrest > >> Type: Bug > >> Components: Core operations > >> Versions: 0.7, 0.8-dev > >> Reporter: David Crossley > >> Priority: Blocker > >> Fix For: 0.8-dev > > > >>upgrading from commons-jxpath-20030909.jar to commons-jxpath-1.2.jar > >>causes failures with linkrewriter protocols site: etc. This happens in > >>both modes: 'forret run' and 'forrest'.
