cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Willem Jiang (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (CXF-1809) Annotated @PostConstruct methods called twice on single Spring bean
Date Fri, 10 Oct 2008 06:55:44 GMT

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

Willem Jiang resolved CXF-1809.
-------------------------------

       Resolution: Fixed
    Fix Version/s: 2.1.3
                   2.0.9

trunk
http://svn.apache.org/viewvc?rev=703309&view=rev
2.1.x
http://svn.apache.org/viewvc?rev=703313&view=rev
2.0.x
http://svn.apache.org/viewvc?rev=703338&view=rev


> Annotated @PostConstruct methods called twice on single Spring bean 
> --------------------------------------------------------------------
>
>                 Key: CXF-1809
>                 URL: https://issues.apache.org/jira/browse/CXF-1809
>             Project: CXF
>          Issue Type: Bug
>    Affects Versions: 2.1.1
>         Environment: All
>            Reporter: Eric Sirianni
>            Assignee: Daniel Kulp
>             Fix For: 2.0.9, 2.1.3
>
>
> Seems like an overlap between CXF's Jsr250BeanPostProcessor and Spring's CommonAnnotationBeanPostProcessor:
> First invocation:
>         MyBean.init() line: 41
> 	NativeMethodAccessorImpl.invoke0(Method, Object, Object[]) line: not available [native
method]	
> 	NativeMethodAccessorImpl.invoke(Object, Object[]) line: 39	
> 	DelegatingMethodAccessorImpl.invoke(Object, Object[]) line: 25	
> 	Method.invoke(Object, Object...) line: 585	
> 	InitDestroyAnnotationBeanPostProcessor$LifecycleElement.invoke(Object) line: 297	
> 	InitDestroyAnnotationBeanPostProcessor$LifecycleMetadata.invokeInitMethods(Object, String)
line: 250	
> 	CommonAnnotationBeanPostProcessor(InitDestroyAnnotationBeanPostProcessor).postProcessBeforeInitialization(Object,
String) line: 144	
> 	DefaultListableBeanFactory(AbstractAutowireCapableBeanFactory).applyBeanPostProcessorsBeforeInitialization(Object,
String) line: 350	
> 	DefaultListableBeanFactory(AbstractAutowireCapableBeanFactory).initializeBean(String,
Object, RootBeanDefinition) line: 1330	
> 	DefaultListableBeanFactory(AbstractAutowireCapableBeanFactory).doCreateBean(String,
RootBeanDefinition, Object[]) line: 473	
> 	AbstractAutowireCapableBeanFactory$1.run() line: 409	
> Second invocation:
>         MyBean.init() line: 41
> 	NativeMethodAccessorImpl.invoke0(Method, Object, Object[]) line: not available [native
method]	
> 	NativeMethodAccessorImpl.invoke(Object, Object[]) line: 39	
> 	DelegatingMethodAccessorImpl.invoke(Object, Object[]) line: 25	
> 	Method.invoke(Object, Object...) line: 585	
> 	ResourceInjector.invokePostConstruct() line: 304	
> 	ResourceInjector.construct(Object) line: 86	
> 	Jsr250BeanPostProcessor.postProcessAfterInitialization(Object, String) line: 58	
> 	DefaultListableBeanFactory(AbstractAutowireCapableBeanFactory).applyBeanPostProcessorsAfterInitialization(Object,
String) line: 361	
> 	DefaultListableBeanFactory(AbstractAutowireCapableBeanFactory).initializeBean(String,
Object, RootBeanDefinition) line: 1343	
> 	DefaultListableBeanFactory(AbstractAutowireCapableBeanFactory).doCreateBean(String,
RootBeanDefinition, Object[]) line: 473	
> 	AbstractAutowireCapableBeanFactory$1.run() line: 409	
> I noticed this checkin after doing a google search http://code.google.com/p/xebia-france/source/detail?r=139
- it seems relevant to this bug

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


Mime
View raw message