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

Robert F. Peake commented on OPENJPA-2791:
------------------------------------------

Debugging, the actual code is effectively identical to your example until the 
final setProperty method. Instead of a String giving the url of the xsd file, a 
schema object is passed containing an input stream and a jarURLConnection, 
which points to the jar file at:
apache-tomee-webprofile-7.1.1/lib/openjpa-2.4.3.jar!/org/apache/openjpa/persistence/persistence-xsd.rsrc.
 That file contains the xsd schema for JPA 1.0. So the focus of investigation 
would seem to be how the schema object is assembled and why it is not getting 
the right url. The implementation is not available in the source code, as far 
as I can tell.
Let me know if there is anything else I can check.

> Parsing persistence.xml throws premature end of file error
> ----------------------------------------------------------
>
>                 Key: OPENJPA-2791
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-2791
>             Project: OpenJPA
>          Issue Type: Bug
>          Components: build / infrastructure, jpa
>    Affects Versions: 2.4.3
>         Environment: Linux Ubuntu 18.04
>            Reporter: Robert F. Peake
>            Priority: Major
>              Labels: build
>
> XMLMetaDataParser in org.apache.openjpa.lib.meta uses the SaxParser to read 
> persistence.xml. Just within the last few days, it has begun to throw this 
> error:
> {quote}org.xml.sax.SAXException: 
> [file:/home/robert/git/sccdata/target/classes/META-INF/persistence.xml|file:///home/robert/git/sccdata/target/classes/META-INF/persistence.xml]
>  [Location: Line: 5, C: 64]: org.xml.sax.SAXParseException; systemId: 
> [http://xmlns.jcp.org/xml/ns/persistence/persistence_2_1.xsd]; lineNumber: 1; 
> columnNumber: 1; Premature end of file.
> {quote}
> Resorting to XML Copy Editor to validate the schema shows the error actually 
> involved: Fatal Error at line 0, column 0: unsupported protocol in URL. It 
> seems that Oracle's web site has switched from HTTP to HTTPS, which is a 
> protocol that parser cannot handle, as explained in this post:
> {color:#000000}[article|[https://knowledgebase.progress.com/articles/Article/Unsupported-protocol-in-URL-reading-XML-from-a-URI].]{color}
> {color:#000000} {color}
> {color:#000000}The problem has been reported elsewhere [Stack 
> Overflow|https://stackoverflow.com/questions/56728487/org-xml-sax-saxparseexceptionpublicid-http-xmlns-jcp-org-xml-ns-persistence-p/56741356#56741356].{color}
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to