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 6018041
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 23, 20262026-05-23T03:13:00+00:00 2026-05-23T03:13:00+00:00

I have a bean which I use to load cache. I give the key

  • 0

I have a bean which I use to load cache. I give the key for cache from Spring injection. I am duplicating the same bean just for the property and Spring is creating multiple instances of same bean. Is there anyway I can use one instance of the bean?

<aop:config>
    <aop:pointcut id="terminalPointcut"
        expression="execution(* *..TerminalDao.getTerminals())" />
    <aop:pointcut id="miscPointcut"
        expression="execution(* *..MiscDao.getMiscTableList(*))" />
    <aop:pointcut id="errorPointcut"
        expression="execution(* *..ErrorDao.getErrorList())" />
    <aop:advisor id="terminalCacheLoaderAdvisor"
        advice-ref="terminalCacheLoaderAdvice" pointcut-ref="terminalPointcut" />
    <aop:advisor id="miscCacheLoaderAdvisor"
        advice-ref="miscCacheLoaderAdvice" pointcut-ref="miscPointcut" />
    <aop:advisor id="errorCdDetailCacheLoaderAdvisor"
        advice-ref="errorCacheLoaderAdvice" pointcut-ref="errorPointcut" />
</aop:config>

<bean id="miscCacheLoaderAdvice" class="com.temp.ehCache.interceptor.CacheLoader">
        <property name="cacheManager" ref="simpleCacheManager" />   
        <property name="cache_data_key" value="MISC_DATA_KEY" />
</bean>

<bean id="errorCacheLoaderAdvice" class="com.temp.ehCache.interceptor.CacheLoader">
        <property name="cacheManager" ref="simpleCacheManager" />   
        <property name="cache_data_key" value="ERROR_DATA_KEY" />
</bean> 
  • 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-05-23T03:13:01+00:00Added an answer on May 23, 2026 at 3:13 am
    <bean id="miscCacheLoaderAdvice" class="com.temp.ehCache.interceptor.CacheLoader">
            <property name="cacheManager" ref="simpleCacheManager" />   
            <property name="cache_data_key" value="MISC_DATA_KEY" />
    </bean>
    
    <bean id="errorCacheLoaderAdvice" class="com.temp.ehCache.interceptor.CacheLoader">
            <property name="cacheManager" ref="simpleCacheManager" />   
            <property name="cache_data_key" value="ERROR_DATA_KEY" />
    </bean> 
    

    You obviously need the same bean twice with two different configurations. So even if it were possible to combine it in one bean it would be a total pain (You could e.g. use ThreadLocals to set the property as needed etc.)

    I’d say change your design. If com.temp.ehCache.interceptor.CacheLoader is heavy, try to extract the heavy stuff to a delegate bean that can be used by the CacheLoader beans. Keep the CacheLoader beans as small as possible, and it won’t be a problem to have more than one of them around (as long as you don’t use autowiring by type).

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I have an application where I have to use Spring to load a bean
I am using spring to initialise my beans. I have configured a bean which
I have a resource (Spring bean) which has some of its fields injected by
I have a bean definition in Spring and it's proxy counterpart which is meant
I have a bean which I map to the database using Hibernate. I'm using
I have a problem with selectInputDate: I have a backing bean which I am
I have a method invoking bean which calls a method to perform some sort
I have one method in my managed bean which returns javascript as a string.
I have a bean of type string[] which has two or more values. I
I have a MDB (Message driven bean) that receives messages with String which represent

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.