Spring: Well, to have two contexts - web & backend?

Question

I have a spring web application with a spring database. Integration is currently being done in a stupid way of manually copying the .xml backend to web application resources and merges.

I was wondering if Spring is ready to have a bean that will be different ApplicationContext, and whether it can get beans from it; also if it handles bean name conflicts - for example. if I can assign the namespace to "imported" beans.

Or - which is best for this case?

Thanks, Ondra.

Answer 1

XML Spring : web, service, persistence. . , ; .

Answer 2

. , ([servlet-name] -context.xml) WebApplicationContext ApplicationContext, , ConfigLocation, ContextLoaderListener. beans, , beans, , , beans .

Web- WebApplicationContext - .. , , ApplicationContext, , xml , , .

<import resource="classpath:dao-context.xml" />
<import resource="classpath:service-context.xml" />
<import resource="security-context.xml" />

. spring - , , [servlet-name] -context.xml -placeholder - , , .

Answer 3

If I understood you correctly, this is definitely good. Some people share database contexts with their online contexts. Example below in your web.xml:

<context-param>
    <param-name>contextConfigLocation</param-name>
    <param-value>
        classpath:someApplicationContext.xml
        classpath:someOtherApplicationContext.xml
    </param-value>
</context-param>

<listener>
    <listener-class>
        org.springframework.web.context.ContextLoaderListener
    </listener-class>
</listener>

As for the collision of beans - you must provide the beans with a unique identifier.