[jbossws-issues] [JBoss JIRA] (JBWS-4046) PostConstruct method not invoked on web service handler
Alessio Soldano (JIRA)
issues at jboss.org
Mon Mar 20 12:17:00 EDT 2017
[ https://issues.jboss.org/browse/JBWS-4046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alessio Soldano updated JBWS-4046:
----------------------------------
Fix Version/s: (was: jbossws-cxf-5.2.0.Final)
> PostConstruct method not invoked on web service handler
> -------------------------------------------------------
>
> Key: JBWS-4046
> URL: https://issues.jboss.org/browse/JBWS-4046
> Project: JBoss Web Services
> Issue Type: Bug
> Components: jbossws-cxf
> Affects Versions: jbossws-cxf-5.1.5.Final
> Reporter: Bartosz Spyrko-Śmietanko
> Assignee: Alessio Soldano
> Fix For: jbossws-cxf-5.1.8.Final
>
>
> Application defines two identical web service classes placed in different packages and accessed via different paths (defined in web.xml). Both web services use the same handler class.
> However, the handler's PostConstruct method is only executed for invocations of one of the two web services (expected: for invocations of both web services).
> Note this is a regression between EAP 6.4.x and 7.0.x.
> it seems this is caused by how the ServerBeanCustomizer matches endpoints. In EAP 6 this was based on the bean's class, but in EAP 7 it uses the WSDL_SERVICE and WSDL_PORT of the service. The problem happens when there are two endpoints with the same service address, but different paths.
> Potential solution: https://github.com/jbossws/jbossws-cxf/compare/jbossws-cxf-5.1.x...spyrkob:JBWS-4046?expand=1
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
More information about the jbossws-issues
mailing list