Uploaded image for project: 'Weld'
  1. Weld
  2. WELD-537

More details to WELD-000072 Managed bean declaring a passivating scope must be passivation capable.

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Duplicate
    • Icon: Major Major
    • None
    • 1.0.1.Final
    • Class Beans (Managed and Session)
    • None

      The error message should be more detailed, currently ManagedBean.initializeAfterBeanDiscovery can have multiple conditions that set the passivationCapableBean to false (non-serializable interceptors etc) but it's hard to tell exactly what is wrong.

            [WELD-537] More details to WELD-000072 Managed bean declaring a passivating scope must be passivation capable.

            Marko Luksa (Inactive) added a comment -

            Apparently this was already taken care of.

            I've tested all the possibilities and get the correct error message in all of them.

            See validators_en.messages:

            PASSIVATING_BEAN_WITH_NONSERIALIZABLE_INTERCEPTOR=The bean {0} declared a passivating scope but has a non-serializable interceptor {1}
PASSIVATING_BEAN_WITH_NONSERIALIZABLE_DECORATOR=The bean {0} declared a passivating scope but has non-serializable decorator {1}

            Marko Luksa (Inactive) added a comment - Apparently this was already taken care of. I've tested all the possibilities and get the correct error message in all of them. See validators_en.messages: PASSIVATING_BEAN_WITH_NONSERIALIZABLE_INTERCEPTOR=The bean {0} declared a passivating scope but has a non-serializable interceptor {1} PASSIVATING_BEAN_WITH_NONSERIALIZABLE_DECORATOR=The bean {0} declared a passivating scope but has non-serializable decorator {1}

              marko.luksa@gmail.com Marko Luksa (Inactive)
              nickarls Nicklas Karlsson (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: