I'm using NamespaceHandler and BeanDefinitionParser based on reference and I'd like to use Spel with bean references. The problem is, that I cannot reach app context in NamespaceHandler or BeanDefinitionParser due to the lifecycle phase we're in, so that when my BeanDefinitionParser interprets Spel expressions it doesn't have BeanFactory available for evaluating spel with bean references. Any idea how to deal with this ? If the SpEL was placed on bean properties I could leave it be and have spring interpret it, but unfortunately the SpELs are in the XML that is to be unmarshalled to an object model that is to be used to construct the bean property.
EDITED: based on Gary Russell's advice
<bean id="securityDecriptor" class="com.fg.edee.integration.descriptor.security.SecurityDescriptorImpl">
<property name="securityModuleName" value="security"/>
<property name="securityModuleDescription" value="security"/>
</bean>
<bean id="moduleDescription" class="com.fg.edee.integration.descriptor.schema.ModuleDescription">
<property name="treeDescriptor">
<mtd:treeDescriptor>
<mtd:security rights="W" moduleId="#{ securityDecriptor.securityModuleId }" moduleName="#{ securityDecriptor.securityModuleName }">
<mtd:securityIdentifier identifierId="users" identifierName="users"/>
</mtd:security>
</mtd:treeDescriptor>
</property>
</bean>