Bug 45869 - DefaultAnnotationProcessor does not scan class hierarchy for @PostConstruct and @PreDestroy annotations
Summary: DefaultAnnotationProcessor does not scan class hierarchy for @PostConstruct a...
Status: RESOLVED DUPLICATE of bug 45285
Alias: None
Product: Tomcat 6
Classification: Unclassified
Component: Jasper (show other bugs)
Version: 6.0.14
Hardware: PC Windows XP
: P2 normal (vote)
Target Milestone: default
Assignee: Tomcat Developers Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-09-23 17:50 UTC by Firstname Lastname
Modified: 2008-09-24 05:18 UTC (History)
0 users



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Firstname Lastname 2008-09-23 17:50:07 UTC
DefaultAnnotationProcessor does not scan class hierarchy for @PostConstruct and @PreDestroy annotations.

The @PostConstruct function is not called for a managed bean when the function
is defined in the base class.

Detail:

In the base class BaseClass I have a function

@PostConstruct
public void BaseClass.init();

My bean class OuterBean is derived from BaseClass, so it inherits this init
function and hopefully the @PostConstruct annotation.

In the old version of JSF, namely 1.2-b20-FCS from April/21/2006, the init()
function was called. But in the new version of JSF, which is JSF 1.2.9 from
July/17/2008, init() is not called.

I wrote a bug against JSF, and they said that I should write a bug against Tomcat 6, and mention the DefaultAnnotationProcessor.  So this is the bug.

The URL of my JSF bug is

https://javaserverfaces.dev.java.net/issues/show_bug.cgi?id=800
Comment 1 Mark Thomas 2008-09-24 05:18:40 UTC

*** This bug has been marked as a duplicate of bug 45285 ***