[
https://issues.apache.org/jira/browse/DOSGI-206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Schneider resolved DOSGI-206.
---------------------------------------
Resolution: Won't Fix
I have digged a bit deeper into this. The exceptions only happen if the file
contains xml that is not well formed. In this case I think it is not a big
problem that both parsers report the problem.
So I think we do not need to fix this right now. For the next major version we
should make sure the files reside in different directories. Then we can also
activate validation.
> Parse errors for xml files in discovery local and dsw
> -----------------------------------------------------
>
> Key: DOSGI-206
> URL: https://issues.apache.org/jira/browse/DOSGI-206
> Project: CXF Distributed OSGi
> Issue Type: Bug
> Affects Versions: 1.6.0
> Reporter: Christian Schneider
> Assignee: Christian Schneider
> Fix For: 1.6.0
>
>
> There are two xml files types used to extend dosgi.
> - For endpoint descriptions which is used in discovery local
> - For adding and adding properties to services which is used in dsw-cxf
> The files are at the same location but currently use different xsds.
> So we get parse errors when the wrong bundle reads the file. We could solve
> this by either using one schema or by separating the files by name or
> directory.
> The first solution is backwards compatible so we should go this way.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
