Found a case in Blueprint we don't currently handle for global beans referencing other beans.

    <bean class="org.apache.aries.simple.AccountFactory"
        id="accountFactory" scope="singleton">
        <argument value="account factory"/>
    </bean>
    <bean factory-method="createAccount" factory-ref="accountFactory"
        id="accountThree" scope="singleton">
        <argument value="3"/>
    </bean>

This example comes from http://aries.apache.org/modules/blueprint.html

In this example, there are two validation issues currently.

The first is caused by the fact that factory-method "createAccount" cannot be validated as an available method because there's no class in the Global Bean declaration "accountThree". Instead of referencing a class directly, it's referencing the class in another bean - "accountFactory".

The second is caused because "class" is considered to be a required attribute and it doesn't exist in the "accountThree" global bean definition.

These need to be remedied.