[ 
https://issues.apache.org/jira/browse/OWB-319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gurkan Erdogdu closed OWB-319.
------------------------------

    Resolution: Fixed

thanks, done 

> Strange logging when writing non-Serializable SessionScoped bean
> ----------------------------------------------------------------
>
>                 Key: OWB-319
>                 URL: https://issues.apache.org/jira/browse/OWB-319
>             Project: OpenWebBeans
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: M4
>         Environment: *
>            Reporter: Jan-Kees van Andel
>            Assignee: Gurkan Erdogdu
>            Priority: Minor
>             Fix For: 1.0.0
>
>         Attachments: beandeployer_toString.patch
>
>
> When I write a SessionScoped bean, without implementing Serializable, I get 
> the following error in my log.
> 2010-03-05 22:26:38.021:WARN::Failed startup of context 
> org.mortbay.jetty.plugin.jetty6pluginwebappcont...@e73236{/ebanking,D:\dev\work\idea9\jsf2-example-ebanking\target\myfaces-example-ebanking-1.0-SNAPSHOT}
> org.apache.webbeans.exception.WebBeansConfigurationException: Passivation 
> scoped defined bean must be passivation capable, but bean : 
> org.apache.webbeans.config.beansdeplo...@120a9d6 is not passivation capable
> It's caused by a call to the wrong toString in 
> BeansDeployer.checkPassivationScope().
>                     throw new WebBeansConfigurationException("Passivation 
> scoped defined bean must be passivation capable, " +
>                             "but bean : " + toString() + " is not passivation 
> capable");                    
> And should be:
>                     throw new WebBeansConfigurationException("Passivation 
> scoped defined bean must be passivation capable, " +
>                             "but bean : " + beanObj.toString() + " is not 
> passivation capable");                    

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

Reply via email to