Announcement Announcement Module
Collapse
No announcement yet.
Invalid referenced bean Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • Invalid referenced bean

    I am getting an "Invalid referenced bean 'tareasDao'" error in this code. That did not happen before migrating to 1.3.2 from 1.3.0.

    <bean id="tareasDaoFactory" class="com.xxx.TareasDaoFactory">
    <property name="tareasDaoClassname" value="${jdbc.daoclass}"/>
    </bean>

    <bean id="tareasDao" factory-bean="tareasDaoFactory" factory-method="createTareasDao">
    <property name="dataSource" ref="dataSource"/>
    </bean>

    <bean class="org.springframework.transaction.interceptor .TransactionProxyFactoryBean">
    <property name="transactionManager" ref="transactionManager"/>
    <property name="target" ref="tareasDao"/>
    <property name="transactionAttributes">
    <props>
    <prop key="get*">PROPAGATION_REQUIRED,readOnly</prop>
    </props>
    </property>
    </bean>


    Any hint?

    Thank you in advance.

    Jose M Beleta

  • #2
    Fixed. For details please refer to ticket #335.

    Torsten

    Comment


    • #3
      Could we please have a 1.3.3 release for this fix? The IDE is pretty unusable for me with this bug, since around half the context is filled with errors.

      Comment


      • #4
        I am getting an "Invalid referenced bean 'evSession'" error in this code. I'm using 1.3.2 version of SpringIDE.

        <bean id="evSession" factory-bean="sessionBuilder" factory-method="create"><constructor-arg>
        <idref bean="evSessionId"/>
        </constructor-arg>
        </bean>

        <bean id="evSessionManager" class="my.package.SessionManager">
        <constructor-arg>
        <idref bean="evSession"/>
        </constructor-arg>
        </bean>

        It looks similar to the above described problem.

        Comment


        • #5
          Well it seems that until 1.3.3 version is released - this bug won't be fixed. I've got the same situation

          Comment


          • #6
            Originally posted by rience
            Well it seems that until 1.3.3 version is released - this bug won't be fixed. I've got the same situation
            Check out the update site

            Comment

            Working...
            X