You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Simon Kitching (JIRA)" <de...@myfaces.apache.org> on 2007/11/26 18:04:43 UTC

[jira] Created: (ORCHESTRA-9) NullPointerException in AbstractSpringOrchestraScope when BeanPostProcessor is configured

NullPointerException in AbstractSpringOrchestraScope when BeanPostProcessor is configured
-----------------------------------------------------------------------------------------

                 Key: ORCHESTRA-9
                 URL: https://issues.apache.org/jira/browse/ORCHESTRA-9
             Project: MyFaces Orchestra
          Issue Type: Bug
          Components: Conversation
    Affects Versions: 1.0
            Reporter: Simon Kitching
            Assignee: Simon Kitching


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/>


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.