Antonio Gallardo wrote: > David Crossley wrote: > > > >Thanks, i have been spending a huge amount of time on it. > >I have been deep in Cocoon input modules and JXPath, > >but i am not getting far. It needs someone with better > >Java/XML/Namespace/Cocoon foo. > > Yes, thanks David. But why you think we need deep cocon understanding to > fix this bug? I am just asking. :-)
Because the commons-jxpath issue report seems to say that it is in the way that we (Cocoon) are using the library. They are adamant not to change it. > I believe, the problem is inside the commons-jxpath itself, as I posted > in my latest report in jira. In short, > http://issues.apache.org/bugzilla/show_bug.cgi?id=32360 > > To me the next step is forget cocoon for a while, create a simple > testcase for the jxpath library check the error is there and fix it. > Once the jxpath is fixed, import the patched lib to forrest. I bet it is > going to work. ;-) It probably would. However the Commons JXPath people have said that they won't fix it. Perhaps you can convince them. Good luck. So that is why i was burrowing into Cocoon's JXPath usage. -David
