[JENA-359] inModel() dependencies on ModelCom

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Jena 2.7.4
• Fix Version/s: Jena 2.10.0
• Component/s: Jena
• Assignee: Andy Seaborne
• Reporter: Claude Warren
• Created: 01/Dec/12 17:02
• Updated: 02/Dec/12 18:35
• Resolved: 02/Dec/12 18:21

Description

LiteralImpl.inModel( Model m ) and ResourceImpl.inModel( Model m ) cast the Model m to a ModelCom in some instances.

ResourecImpl.inModel() calls
asNode().isConcrete() == false ? (Resource) ((ModelCom) m).getRDFNode( asNode() )

this line handles working with variables and I am not sure how to fix that.

LiteralImpl.inModel() calls
(Literal) ((ModelCom) m).getRDFNode( asNode() )

I think this can be replaced with
m.createTypedLiteral(getLexicalForm(), getDataType())

My issue is that I have a model implementation that does not derive from ModelCom so these methods fail some test cases.