[jbossws-issues] [JBoss JIRA] Updated: (JBWS-3356) Fix PostConstruct & PreDestroy implementation for JAXWS endpoints & handlers

Alessio Soldano (JIRA) jira-events at lists.jboss.org
Wed Sep 7 07:22:27 EDT 2011


     [ https://issues.jboss.org/browse/JBWS-3356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alessio Soldano updated JBWS-3356:
----------------------------------

    Component/s: jbossws-cxf
                 jbossws-integration
                 jbossws-native


> Fix PostConstruct & PreDestroy implementation for JAXWS endpoints & handlers
> ----------------------------------------------------------------------------
>
>                 Key: JBWS-3356
>                 URL: https://issues.jboss.org/browse/JBWS-3356
>             Project: JBoss Web Services
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: jbossws-cxf, jbossws-integration, jbossws-native
>            Reporter: Richard Opalka
>             Fix For: jbossws-native-4.1, jbossws-cxf-4.1
>
>
> JSR 316: JavaEE Platform Specification
> Section 5.2.5: Annotations and Deployment Descriptors
> ---
> In some cases a class may need to perform initialization of its own after all
> resources have been injected. To support this case, one method of the class may be
> annotated with the PostConstruct annotation (or, equivalently, specified using
> the post-construct entry of a deployment descriptor). This method will be called
> after all injections have occured and before the class is put into service. This
> method will be called even if the class doesn't request any resources to be
> injected. Similarly, for classes whose lifecycle is managed by the container, the
> PreDestroy annotation (or, equivalently, the pre-destroy entry of a deployment
> descriptor) may be applied to one method that will be called when the class is
> taken out of service and will no longer be used by the container. Each class in a
> class hierarchy may have PostConstruct and PreDestroy methods. The order in
> which the methods are called matches the order of the class hierarchy with
> methods on a superclass being called before methods on a subclass.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the jbossws-issues mailing list