Is it possible to completely ignore namespaces during deserialization? #170

Activity

1. pdvrieze commented on Jul 19, 2023

   

   pdvrieze

   on Jul 19, 2023

   Owner

   More actions

   At the moment there is no built-in standard way to handle missing namespaces. You could do it in the policy, but it is probably easier to have a wrapper around XmlReader that replaces the default (empty) namespace with the POM namespace for tags (but not attributes as the attributes are not qualified).
2. lamba92 commented on Jul 20, 2023

   

   lamba92

   on Jul 20, 2023

   Last edited by lamba92

   Author

   More actions

   Could you please show an example of both cases? Or at least a snippet to try to understand in which direction to go
3. artemmukhin

   added 2 commits that reference this issue on Jul 24, 2023

   Fix parsing of POM files without namespaces

   ...

   73c2047

   Fix parsing of POM files without namespaces

   ...

   41fff50
4. lamba92 commented on Aug 8, 2024

   

   lamba92

   on Aug 8, 2024

   Author

   More actions

   Hi, any updates on this? Since v83.3 this workaround:

   public inline fun <reified T : Any> XML.decodeFromString(
       namespace: String,
       string: String,
   ): T {
       return decodeFromReader<T>(
           object : XmlReader by XmlStreaming.newReader(string) {
               override val namespaceURI: String get() = namespace
           },
       )
   }

   is not working anymore. Is there now a way to properly ignore namespaces during deserialization?
5. pdvrieze commented on Aug 8, 2024

   

   pdvrieze

   on Aug 8, 2024

   Owner

   More actions

   I'm not sure why the workaround doesn't work, what happens if you use a DelegatingXmlReader explicitly? The other way that you can work around it is to use the policy to do recovery (rather than throw an exception) – the filter you have should be more resilient.
6. lamba92 commented on Aug 20, 2024

   

   lamba92

   on Aug 20, 2024

   Last edited by lamba92

   Author

   More actions

   The problem seems to be here. When reader.name is invoked, somehow the QName generated does not use the overridden namespaceURI.

   Overriding the name as well works again:

   public inline fun <reified T : Any> XML.decodeFromString(
       namespace: String,
       string: String,
   ): T {
       return decodeFromReader<T>(ManualNamespaceXmlReader(namespace, string))
   }
   
   public class ManualNamespaceXmlReader(
       override val namespaceURI: String,
       xmlString: String,
   ) : XmlReader by xmlStreaming.newReader(xmlString) {
       override fun toString(): String = "ManualNamespaceXmlReader(namespaceURI=\"$namespaceURI\")"
   
       override val name: QName
           get() = QName(namespaceURI, localName, prefix)
   }
   
7. pdvrieze commented on Aug 21, 2024

   

   pdvrieze

   on Aug 21, 2024

   Owner

   More actions

   @lamba92 The problem is that when using delegation the reader.name will call the namespaceURI in the delegate, rather than the overridden writer. Where if you manually delegate (not using by delegate) the implementation of name would have to either be explicitly overridden, or it will use the default implementation (that gets the components directly).
8. pdvrieze

   marked Error when try parse maven pom #270 as a duplicate of this issue on Mar 21, 2025