Hi Jurgen,
The explorer bug could be due to the old version of sarissa being used
in 2.2.0 which was analyzed by Stephen Davies last year - could you
check and see whether you are using 0.9.9.4 please? (The trunk has the
latest one in it now thanks to Heikki I think -
web/geonetwork/scripts/sarissa.js).
I've seen the Firefox problem you mention a few times in my travels but
never had a real chance to try and solve it - in the few attempts at
analyzing it that I made I think I saw the Ajax requests for the XML
coming back with an unusual response code and no xml (in fact I don't
think the server ever saw the request!). Haven't noticed it recently
with the latest updates to Firefox (using 3.0.7 now) - but that's not
terribly comforting! :-)
What sub-version of Firefox 3 are you finding the problem with (eg. 3.0.3)?
Is the server actually receiving the request and producing the xml response?
Perhaps you can get Firebug onto this and give us a trace so we can
attempt to track it down?
I couldn't get a repeatable test case and I fiddled with delays etc to
try and see if I could change its behaviour but to no avail.
Cheers,
Simon
GeoNetwork opensource Developer website wrote:
> #94: NS_ERROR_INVALID_POINTER in Oracle Internet Application Server
> ----------------------------------+-----------------------------------------
> Reporter: ticheler | Owner: geonetwork-devel@...
> Type: defect | Status: new
> Priority: major | Milestone:
> Component: User interface (web) | Version:
> Keywords: Oracle |
> ----------------------------------+-----------------------------------------
> Dear Jeroen,
>
> We deployed GeoNetwork 2.2.0 on Oracle Internet Application Server. In
> principal it works fine. However, we found a bug in the harvesting
> management. The exception NS_ERROR_INVALID_POINTER occurs in the script
> xsl-transformer.js if the link "harvesting managment" is selected in the
> administration page. The problem is, that the value of t.responseXML is
> null. I fixed the problem for the Firefox 3.0 browser by introducing the
> following lines of code:
>
> if (t.responseXML == null)
> {
> parser = new window.DOMParser();
> t.responseXML = parser.parseFromString(t.responseText,'text/xml');
> }
>
> Nevertheless, the problem still exists for MS Internet Explorer. I was not
> able to find out the real reason of the problem. May be you will really
> detect the error and find a better bug fix. The revised version of the
> script xsl-transformer.js is attached to this email.
>
> Kind regards,
> Jürgen
> -----------------------------------
> Dr. Jürgen Seib
> Deutscher Wetterdienst
> TI1/K - IT-Koordination
> Frankfurter Strasse 135
> 63067 Offenbach
> Tel.: +49(69)8062-2609
> EMail: juergen.seib@...
>
>
|