Andrew Berezovskyi created JENA-1477:
----------------------------------------
Summary: Updating from Jena 2.12 to Jena 3.0.1 produces different
RDF/XML output IF ARQ is loaded
Key: JENA-1477
URL: https://issues.apache.org/jira/browse/JENA-1477
Project: Apache Jena
Issue Type: Bug
Components: RDF/XML, RIOT
Affects Versions: Jena 3.0.1
Environment: Jena 3.0.1
Reporter: Andrew Berezovskyi
We are in the process of a Jena 2>3 transition in Eclipse Lyo and discovered
the following: if the ARQ is used in the application, then the typed node
elements will be used by default, which did not occur in Jena 2. It causes
problems for some legacy apps that rely on Lyo.
We were able to eliminate this behaviour by calling the static method
RDFWriterFImpl.alternative(null);
Technically, this ensures that the
'org.apache.jena.rdfxml.xmloutput.impl.Basic' implementation is not getting
substituted for the 'org.apache.jena.riot.adapters.RDFWriterRIOT'.
Questions:
# Is it the best way to ensure backwards compatibility of the RDF/XML output
when moving from Jena 2>3?
# Is there any way to control the RIOT writer to produce XML w/o typed node
elements so that we can avoid resetting the alternative writer?
# (if you have some extra time) What purpose do alternative writers serve?
What is the difference between the writers in the respective packages as the
two writers above?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
