[
https://issues.apache.org/jira/browse/JENA-359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13508311#comment-13508311
]
Andy Seaborne commented on JENA-359:
------------------------------------
Fixed in both trunk and in branches/jena-core-simplified.
The simplification work is done, barring one test failing but that looks like
the test failure (in concurrency) is something the old tests did not find.
There are other ModelCom dependencies and ResourceImpl is quite tied to
ModelCom. Let's take that to the A list for general discussion
> inModel() dependencies on ModelCom
> ----------------------------------
>
> Key: JENA-359
> URL: https://issues.apache.org/jira/browse/JENA-359
> Project: Apache Jena
> Issue Type: Bug
> Components: Jena
> Affects Versions: Jena 2.7.4
> Reporter: Claude Warren
> Fix For: Jena 2.10.0
>
>
> 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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
