Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 9208427
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 18, 20262026-06-18T00:36:58+00:00 2026-06-18T00:36:58+00:00

I have Maven project with Spring. I have backend project as jar in the

  • 0

I have Maven project with Spring. I have backend project as jar in the classpath(added as maven dependency). The backend project is with Spring again and has it’s own applicationContext.xml. In the frontend project I have applicationContext.xml and I want to access the application context from tha backend like this:

<import resource="classpath:applicationContext.xml" />

but i got:

org.springframework.beans.factory.parsing.BeanDefinitionParsingException: Configuration problem: Failed to import bean definitions from URL location [classpath:applicationContext.xml]
Offending resource: ServletContext resource [/WEB-INF/appContext.xml]; nested exception is org.springframework.beans.factory.BeanDefinitionStoreException: IOException parsing XML document from class path resource [applicationContext.xml]; nested exception is java.io.FileNotFoundException: class path resource [applicationContext.xml] cannot be opened because it does not exist

Also tried:

<import resource="classpath*:applicationContext.xml" />

and

<import resource="classpath:/applicationContext.xml" />
  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-18T00:36:59+00:00Added an answer on June 18, 2026 at 12:36 am

    If I understand correctly, you want the front end to access the applicationContext.xml of the back end project. Then classpath* is the right statement, and you should make sure namespaces of both configuration files are the same.

    For example, this case won’t work

    Front end:

    http://www.springframework.org/schema/beans/spring-beans-3.1.xsd
    

    Back end:

    http://www.springframework.org/schema/beans/spring-beans-3.2.xsd
    
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I have a Spring project that uses Maven and has several profiles to allow
We have created a jar(Spring project) which we are including using Maven in another
I have Maven project with Hibernate and Spring framework. I want Hibernate to create
I have a maven project that was generated by Spring Roo. Now I am
I am using Spring and Maven project. I have Project mit-webservices and mit-util project
I have a Maven based Spring-WS client project that I want to package as
I have a maven project that has a set of library dependancies that are
I have a maven project with the following structure: spring-di-test +--spring-di-test-core | com.example.core.DITestMain +--spring-di-test-store
I've got an Eclipse Maven project for spring-data-jpa and QueryDsl. I seem to have
I have a multi-module Maven project that uses Spring IoC, something like parent-proj -

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.