[ 
https://issues.apache.org/jira/browse/CXF-8623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kevin Burnett updated CXF-8623:
-------------------------------
    Description: 
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. The fix was to 
download the 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.

  was:
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. The fix was to 
download the 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.


> 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. The fix was 
> to download the 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