[
https://issues.apache.org/jira/browse/OLINGO-463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Bolz resolved OLINGO-463.
---------------------------------
Resolution: Fixed
Fix Version/s: V2 2.0.1
Fixed with [\[OLINGO-463\] Fix empty documentation
serialization|https://git-wip-us.apache.org/repos/asf?p=olingo-odata2.git;a=commit;h=7029836a9ac40cc9baa4b0fed19c7f0f4d0dc82a].
> Olingo Java V2 and EntityType.Documentation rendering problem
> -------------------------------------------------------------
>
> Key: OLINGO-463
> URL: https://issues.apache.org/jira/browse/OLINGO-463
> Project: Olingo
> Issue Type: Bug
> Components: odata2-core
> Affects Versions: V2 2.0.0
> Reporter: David A. Ventimiglia
> Assignee: Michael Bolz
> Fix For: V2 2.0.1
>
>
> In Olingo Java V2, the class
> org.apache.olingo.odata2.core.ep.producer.XmlMetadataProducer has the method
> writeDocumentation, and in that method on line 582 (at least in the source
> that I downloaded), it calls writeCharacters in the class
> javax.xml.stream.XMLStreamWriter and passes in
> documentation.getLongDescription without anticipating the possibility that
> the longDescription will be null. I think this is a bug, because the OData
> v2.0 spec says that a Documentation element CAN specify a LongDescription,
> not that it MUST specify a LongDescription. Likewise with the Summary. I
> could be wrong about this, but as far as I can tell, this is a bug.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
