changing displayId of loaded SequenceFeature has strange outcome when later writing to rdf

[nroehner]

After loading a SequenceFeature from a rdf file using IOTools.fromRdfXml(), I changed its displayId by calling SequenceFeature.setDisplayId(). When I wrote to another rdf using IOTools.toRdfXml(), the feature in the file correctly had its new displayId, but incorrectly had its old encrypted id based on its old displayId and was missing its SO types.

The only way I could work around this was by creating a new SequenceFeature and copying into it the new displayId and all the values of the old SequenceFeature before writing out the new SequenceFeature.