You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 10, 2023. It is now read-only.
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]
The text was updated successfully, but these errors were encountered:
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]
The text was updated successfully, but these errors were encountered: