[
https://issues.apache.org/jira/browse/CXF-8623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17454615#comment-17454615
]
Freeman Yue Fang commented on CXF-8623:
---------------------------------------
And please see the related discussion here
https://lists.apache.org/thread/xzo8jjjql3y9lmfm50jpklwqq6tgg2qo
> XSD Not Served over HTTP
> ------------------------
>
> Key: CXF-8623
> URL: https://issues.apache.org/jira/browse/CXF-8623
> Project: CXF
> Issue Type: Bug
> Components: JAX-RS
> Reporter: Kevin Burnett
> Priority: Major
> Attachments: image-2021-12-06-18-03-55-276.png
>
>
> First of all, thanks for the work you do and making a tool that helps a lot
> of people. I don't know if this issue is best served here, or should go to
> the cxf.apache.org website managers.
> Anyways, I'm loading a webservice module via OSGi and am receiving the
> following error when loading the module:
> {code:java}
> org.xml.sax.SAXParseException; systemId:
> http://cxf.apache.org/schemas/jaxrs.xsd; lineNumber: 1; columnNumber: 1;
> Premature end of file. {code}
>
> When I try to curl the XSD URL, I get nothing returned (however, I do get a
> file returned when curling the HTTPS URL). As a comparison, when I curl the
> Spring Beans XSD,
> [http://www.springframework.org/schema/beans/spring-beans.xsd,] I do get back
> a file.
>
> We just started seeing this today in our production environment, but I could
> reproduce it locally when trying to start the module in OSGi. We hadn't made
> any changes in our production environment other than restarting the OSGi
> service. We discovered the fix was to download the JAX-RS XSD, reference it
> from the class path directly, then update the schema imports in "jaxrs.xsd"
> to be the following:
>
> {code:java}
> <xsd:import namespace="http://cxf.apache.org/configuration/beans";
> schemaLocation="https://cxf.apache.org/schemas/configuration/cxf-beans.xsd"/>
> <xsd:include
> schemaLocation="https://cxf.apache.org/schemas/jaxrs-common.xsd"/> {code}
>
>
> However, it would be nice to not have to make this change and allow the XSD,
> though resolved to https, to still return the XML over http.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
