[ https://issues.jboss.org/browse/JBWS-4046?page=com.atlassian.jira.plugin.... ] Bartosz Spyrko-Śmietanko updated JBWS-4046: ------------------------------------------- Description: 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...spyrko... was: 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: -- This message was sent by Atlassian JIRA (v7.2.3#72005)