{"action":"opened","issue":{"url":"https://api.github.com/repos/owlcs/owlapi/issues/566","repository_url":"https://api.github.com/repos/owlcs/owlapi","labels_url":"https://api.github.com/repos/owlcs/owlapi/issues/566/labels{/name}","comments_url":"https://api.github.com/repos/owlcs/owlapi/issues/566/comments","events_url":"https://api.github.com/repos/owlcs/owlapi/issues/566/events","html_url":"https://github.com/owlcs/owlapi/issues/566","id":182830223,"number":566,"title":"Serialization Issues with 3.5.4 and 4.2.6","user":{"login":"cbobed","id":12048843,"avatar_url":"https://avatars.githubusercontent.com/u/12048843?v=3","gravatar_id":"","url":"https://api.github.com/users/cbobed","html_url":"https://github.com/cbobed","followers_url":"https://api.github.com/users/cbobed/followers","following_url":"https://api.github.com/users/cbobed/following{/other_user}","gists_url":"https://api.github.com/users/cbobed/gists{/gist_id}","starred_url":"https://api.github.com/users/cbobed/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/cbobed/subscriptions","organizations_url":"https://api.github.com/users/cbobed/orgs","repos_url":"https://api.github.com/users/cbobed/repos","events_url":"https://api.github.com/users/cbobed/events{/privacy}","received_events_url":"https://api.github.com/users/cbobed/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2016-10-13T15:57:37Z","updated_at":"2016-10-13T15:57:37Z","closed_at":null,"body":"Hi, \r\n\r\nI've found some problems when serialising OWLOntology instances. \r\n\r\n- In 3.5.4 version, the owlOntologyManager is serialized before the ontologyID and raises a nullPointer exception when trying to invoke hashCode exception. At first sight, it seems that moving the order of the declarations solves the problem, but it does not serialize the logical axioms correctly (the cloned ontology has 0 axioms). \r\n- In 4.2.6 version, the reordering at OWLImmutableOntology does not work (I cannot figure right now why). In my local repository, I've developed a workaround by adding a protected int hashCode which is initialized the first time is accessed, and a modified hashCode method which does not call directly the ontologyID hashCode(). It seems that this allows to serialize and clone already loaded/parsed ontologies, which cannot be done with the current version. \r\n\r\nCheers, \r\nCarlos "}}
{"actor":{"display_login":"cbobed"}}