RE: o.a.s.contentparser.api.ContentHandler: Namespace handling

yes, sure! stefan >-Original Message- >From: Konrad Windszus >Sent: Thursday, April 15, 2021 2:27 PM >To: dev@sling.apache.org >Subject: Re: o.a.s.contentparser.api.ContentHandler: Namespace handling > >Hi Stefan, >would it be ok to you if

Re: o.a.s.contentparser.api.ContentHandler: Namespace handling

Hi Stefan, would it be ok to you if I would copy over https://raw.githubusercontent.com/wcm-io/wcm-io-tooling/develop/commons/content-package-builder/src/main/java/io/wcm/tooling/commons/contentpackagebuilder/ValueConverter.java

Re: o.a.s.contentparser.api.ContentHandler: Namespace handling

akes sense. > not sure for b) if you have always control over this - but does not harm to > have it in place there as well. > > stefan > >> -Original Message- >> From: Konrad Windszus >> Sent: Wednesday, April 14, 2021 9:25 PM >> To: dev@sling.apach

RE: o.a.s.contentparser.api.ContentHandler: Namespace handling

well. stefan >-Original Message- >From: Konrad Windszus >Sent: Wednesday, April 14, 2021 9:25 PM >To: dev@sling.apache.org >Subject: Re: o.a.s.contentparser.api.ContentHandler: Namespace handling > >Hi Stefan, >thanks for the response. According to >https://is

Re: o.a.s.contentparser.api.ContentHandler: Namespace handling

Hi Stefan, thanks for the response. According to https://issues.apache.org/jira/browse/SLING-4937 the Sling-Namespaces header is no longer supported since 2015. The only thing which is still there is 'Sling-Nodetypes'. Therefore I think it is re

RE: o.a.s.contentparser.api.ContentHandler: Namespace handling

hello konrad. i've faced the same problem in [1][2] which is using [3] internally. this is the standard list [4] i've come up with - but you have to make it configurable to support custom namespaces. in the plugin, i'm parsing the bundle for Sling-Namespaces headers [5] which usually should cont