Following Java-first approach to develop soap-services for Tomcat 7, using org.glassfish.metro:webservices-rt:2.3.1 as soap-provider via Maven.
If webservices have the same function name but in different classes with different parameters and return-types, only one of them will work when deployed to the webserver, the other will report a argument type mismatch.
Parameters and return-types are classes with @XmlRootElement defined and different namespaces.
If one of the functions is renamed, both of them will work.
Following Java-first approach to develop soap-services for Tomcat 7, using org.glassfish.metro:webservices-rt:2.3.1 as soap-provider via Maven.
If webservices have the same function name but in different classes with different parameters and return-types, only one of them will work when deployed to the webserver, the other will report a argument type mismatch.
Parameters and return-types are classes with @XmlRootElement defined and different namespaces.
If one of the functions is renamed, both of them will work.
Environment
org.glassfish.metro:webservices-rt:2.3.1 Tomcat 7
Affected Versions
[not determined, 2.3]