hagalaz, you are right,
using $.get() instead of $.ajax() fixes the problem,
but that does mean that this is a genuine bug?
Can somebody look into it?
example:
this works for path = file.owl:
$.get(path, function(xml){callback(that.parse(xml, options));});
this does not work for path = file.owl:
$.ajax({ url: path, dataType: xml, success: function(xml)
{callback(that.parse(xml, options));}});
david decraene
http://jowl.ontologyonline.org
On 27 mei, 08:45, hagalaz [EMAIL PROTECTED] wrote:
I had similar issues with the ajax function. Then I switched to .get
and .post and all worked seamlessly. (I create xml content dynamically
with PHP)
On May 26, 9:35 pm, David Decraene [EMAIL PROTECTED]
wrote:
I have noticed some rather peculiar behavior with the ajax function:
I have a file called person.owl, which contains xml syntax, and when
trying to load that file the ajax call triggers the error function
(parsererror) / fails to load.
However, if I rename the file to person.xml (e.g. change the
extension) I have no problems whatsoever anymore, the file loads
successfully.
Anything I can do to avoid this behaviour (with exception of
renaming?), it seems to be reproducible.
Spotted the bug when working on a plugin I'm writing, the owl (web
ontology language) extension is something encountered frequent in this
setting:
jOWL, a semantic javascript library athttp://jowl.ontologyonline.org/
David Decraene.http://ontologyonline.org
