forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Antonio Gallardo <agalla...@agssa.net>
Subject Re: [jira] Commented: (FOR-675) upgrading to commons-jxpath-1.2.jar causes failures with linkrewriter protocols site: etc.
Date Sat, 22 Oct 2005 08:28:29 GMT
David Crossley wrote:

>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 was working on that since my last mail, please review if this make sense:

http://issues.apache.org/bugzilla/show_bug.cgi?id=32360#c7

>  
>
>>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.
>  
>
lol. Please cross your fingers too, if my last bugzilla comment make 
sense to them, then I hope we will have soon a patch. ;-)

>So that is why i was burrowing into Cocoon's
>JXPath usage.
>  
>
No matter how hard you will try. I think there is no way in cocoon to 
fix that. This is my 4th iteration trying to fix this error in a year. 
The first one was right after Ghent 2004. Do you remember?

I think jxpath community missundertood the xpath specification. Well, 
maybe I am fully wrong. But my common sense tell me that is really hard 
to believe that all the xalan team (before in IBM and now in Apache) + 
Michael Kay, the saxon expert, all this people were unable to understand 
correctly the xpath specification. At least in the Michael Kay case, he 
was one of the people who wrote it! Hence it is imposible he then did a 
mistake interpretaing the same specification when he wrote in Saxon. ;-)

Best Regards,

Antonio Gallardo.


Mime
View raw message