[ 
https://issues.apache.org/jira/browse/CXF-8623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17454085#comment-17454085
 ] 

Freeman Yue Fang commented on CXF-8623:
---------------------------------------

Hi,

Seems we have several related issues now
https://issues.apache.org/jira/browse/CXF-8622
https://issues.apache.org/jira/browse/SM-4967

Which are all caused by "http" protocol now is replaced by "https" protocol by 
default.

One thing still remains unclear to me is that why the remote one is necessary 
here. We have all xsd files in the local cxf jars, so that via spring.schemas 
mechanism, the local xsd files should be used instead of the remote one(no 
matter it's http or https)

Best Regards
Freeman


> 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
>
> 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:
> org.xml.sax.SAXParseException; systemId: 
> [http://cxf.apache.org/schemas/jaxrs.xsd]; lineNumber: 1; columnNumber: 1; 
> Premature end of file.
>  
> 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:
>   <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"/>
>  
> 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)

Reply via email to