[
https://issues.apache.org/jira/browse/CXF-8960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17788043#comment-17788043
]
Andriy Redko commented on CXF-8960:
-----------------------------------
[~frederik.zimmer] thanks for the issue, afaik Apache CXF does not support
EclipseLink Moxy, there is long standing issue to add that (CXF-5131) but it
not yet resolved.
> Error property "eclipselink.default-target-namespace" is not supported when
> eclipselink is on the classpath
> -----------------------------------------------------------------------------------------------------------
>
> Key: CXF-8960
> URL: https://issues.apache.org/jira/browse/CXF-8960
> Project: CXF
> Issue Type: Bug
> Affects Versions: 4.0.3
> Reporter: Frederik Zimmer
> Priority: Major
>
> When eclipselink is on the classpath before the glassfish JAXB implementation
> then the eclipse JAXB provider is the default.
> org.apache.cxf.common.jaxb.JAXBContextCache then detects the eclipse
> implementation and sets the HAS_MOXY to true which then results in the JAXB
> property eclipselink.default-target-namespace being set. In
> org.eclipse.persistence.jaxb.JAXBUtils then a JAXB context is created not by
> using the default provider but by explicitly using the
> org.glassfish.jaxb.runtime.v2.ContextFactory . This then complains about the
> unknown eclipselink property.
> Only by setting the default JAXB provider to be the glassfish implementation
> by setting the system property
> jakarta.xml.bind.JAXBContextFactory=org.glassfish.jaxb.runtime.v2.ContextFactory
> CXF will work in this setting.
> Please make CXF work even if eclipselink is the default JAXB provider by not
> using eclipselink specific properties when the glassfish JAXB provider is
> explicitly requested or support eclipselink as a JAXB provider and use the
> default JAXB provider and don't explicitly request the glassfish
> implementation.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
