[ https://issues.apache.org/jira/browse/SIS-406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Desruisseaux updated SIS-406: ------------------------------------ Description: The {{sis-utility}} module contains many classes needed by Apache SIS for supporting XML (marshaller pool, JAXB adapters, _etc._) but - except in {{org.apache.sis.util.iso}} - does not provide objects to be read or written in XML documents. Those objects are rather defined in the next module, {{sis-metadata}}. The initial intent was to keep {{sis-utility}} generic enough so it could be used for XML documents unrelated to ISO 19115. However with SIS-345 work, a lot of metadata-specific logic has been introduced (e.g. more ISO 19115 namespaces, {{RenameOnImport.lst}} and {{RenameOnExport.lst}} files which contain a list of ISO 19115 properties, _etc._) in addition of specialized JAXB adapters we already had. It does not make sense anymore to keep those classes separated from {{sis-metadata}}. The proposal is to move the following packages from {{sis-utility}} to {{sis-metadata}}: * {{org.apache.sis.xml}} * {{org.apache.sis.internal.jaxb}} and all sub-packages. * {{org.apache.sis.internal.simple}} (for most parts) * {{org.apache.sis.util.iso}} (maybe) as a side-effect of the displacement of JAXB adapters. The API will stay the same. This change should be transparent for users except if they add only the {{sis-utility}} dependency in their Maven project (in which case they may need to add {{sis-metadata}} dependency). was: The {{sis-utility}} module contains many classes needed by Apache SIS for supporting XML (marshaller pool, JAXB adapters, _etc._) but - except in {{org.apache.sis.util.iso}} - does not provide objects to be read or written in XML documents. Those objects are rather defined in the next module, {{sis-metadata}}. The initial intent was to keep {{sis-utility}} generic enough so it could be used for XML documents unrelated to ISO 19115. However we SIS-345 work, a lot of metadata-specific logic has been introduced (e.g. more ISO 19115 namespaces, {{RenameOnImport.lst}} and {{RenameOnExport.lst}} files which contain a list of ISO 19115 properties, _etc._) in addition of specialized JAXB adapters we already had. It does not make sense anymore to keep those classes separated from {{sis-metadata}}. The proposal is to move the following packages from {{sis-utility}} to {{sis-metadata}}: * {{org.apache.sis.xml}} * {{org.apache.sis.internal.jaxb}} and all sub-packages. * {{org.apache.sis.internal.simple}} (for most parts) * {{org.apache.sis.util.iso}} (maybe) as a side-effect of the displacement of JAXB adapters. The API will stay the same. This change should be transparent for users except if they add only the {{sis-utility}} dependency in their Maven project (in which case they may need to add {{sis-metadata}} dependency). > Move XML support from sis-utility module to sis-metadata > -------------------------------------------------------- > > Key: SIS-406 > URL: https://issues.apache.org/jira/browse/SIS-406 > Project: Spatial Information Systems > Issue Type: Task > Components: Metadata, Utilities > Reporter: Martin Desruisseaux > Assignee: Martin Desruisseaux > Priority: Major > Fix For: 1.0 > > > The {{sis-utility}} module contains many classes needed by Apache SIS for > supporting XML (marshaller pool, JAXB adapters, _etc._) but - except in > {{org.apache.sis.util.iso}} - does not provide objects to be read or written > in XML documents. Those objects are rather defined in the next module, > {{sis-metadata}}. The initial intent was to keep {{sis-utility}} generic > enough so it could be used for XML documents unrelated to ISO 19115. However > with SIS-345 work, a lot of metadata-specific logic has been introduced (e.g. > more ISO 19115 namespaces, {{RenameOnImport.lst}} and {{RenameOnExport.lst}} > files which contain a list of ISO 19115 properties, _etc._) in addition of > specialized JAXB adapters we already had. It does not make sense anymore to > keep those classes separated from {{sis-metadata}}. The proposal is to move > the following packages from {{sis-utility}} to {{sis-metadata}}: > * {{org.apache.sis.xml}} > * {{org.apache.sis.internal.jaxb}} and all sub-packages. > * {{org.apache.sis.internal.simple}} (for most parts) > * {{org.apache.sis.util.iso}} (maybe) as a side-effect of the displacement of > JAXB adapters. > The API will stay the same. This change should be transparent for users > except if they add only the {{sis-utility}} dependency in their Maven project > (in which case they may need to add {{sis-metadata}} dependency). -- This message was sent by Atlassian JIRA (v7.6.3#76005)