Submit Feedback
Legacy Knowledge Base
Published Jun. 30, 2025

Eclipse / Liferay IDE: "Failed to read schema document" URL when creating JNDI connections for Spring Portlets

Written By

Michael Tran

How To articles are not official guidelines or officially supporteddocumentation. They are community-contributed content and may not alwaysreflect the latest updates to Liferay DXP. We welcome your feedback toimprove How to articles!

While we make every effort to ensure this Knowledge Base is accurate, itmay not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with anyfeedback or concerns.

Legacy Article

You are viewing an article from our legacy "FastTrack"publication program, made available for informational purposes. Articlesin this program were published without a requirement for independentediting or verification and are provided "as is" withoutguarantee.

Before using any information from this article, independently verify itssuitability for your situation and project.

Issue

  • When creating JNDI connections using Spring, Eclipse / Liferay IDE users may encounter the following error: 
    • "Failed to read schema document 'http://www.liferay.com/schema/lrjee/liferay-jee.xsd', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>

 

Environment

  • Liferay 7.4

 

Resolution

  • The IDE was not able to resolve the URL as-is since the XSD file is not actually available for the URL
  • This error can be resolved by configuring the IDE in the following way:
    1. Go to Preferences > XML > XML Catalog, and click Add.
    2. Under Location, enter the path to the liferay-jee.xsd file, relative to the workspace. The XSD file will need to be on the local file system.
    3. Under Key Type, select Schema Location
    4. Under Key, enter http://www.liferay.com/schema/lrjee/liferay-jee.xsd
    5. After saving this, Eclipse will be able to resolve the XSD correctly and the error marked in Eclipse will go away.

 

Additional Information

 

 

 

Did this article resolve your issue ?
Legacy Knowledge Base
Did this article resolve your issue ?