[ORCHESTRA-9] NullPointerException in AbstractSpringOrchestraScope when BeanPostProcessor is configured

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.0
• Fix Version/s: 1.1
• Component/s: Conversation
• Assignee: Simon Kitching
• Reporter: Simon Kitching
• Created: 26/Nov/07 17:03
• Updated: 26/Nov/07 17:05
• Resolved: 26/Nov/07 17:05

Description

Method AbstractSpringOrchestraScope.registerDestructionCallback throws a NullPointerException if passed a bean that has aop:proxy attached to it.
The reason is that the bean-name passed is of form "scopedTarget.foo", but there is no such conversation - the conversation is named "foo".

This can presumably be triggered by having a destroy method defined for the bean.
However it also gets triggerred whenever there is a "destruction aware" BeanPostProcessor present in the spring context, eg by enabling
PersistenceAnnotationBeanPostProcessor
or
<context:annotation-config/>