I did not specify which behavior I was referring to, but I would like to understand why different complex types' WSDL definitions end up in WSDL for a web service that does not use them and is even serviced by a different EJB altogether.
The loading/unloading behavior, while strange, takes second stage to the above issue in my opinion.
I have confirmed that this problem is not present in JBoss 4.0DR3. Could it be that this is due to the packaging of Axis 1.2 inside JBoss with this release, or was something fixed in JBoss itself? If so, could this same fix be applied to 3.2.4?
I have also confirmed that this problem exists in 3.2.4RC1. Is this something that might be included in 3.2.4RC2+? Is is really quite important for us to see this issue resolved (and the 4.0 branch is not yet a viable option). If you can point me in the right direction for resolution, I would be glad to try anything.
I have seen this as well but have been unable to determine a fix. Does anyone know if this is an identified bug in either JBoss, Axis or the integration of the two?
An associate of mine did some leg work and found the following bug reported as corrected in Axis 1.2
2004-02-27 17:07 gdaniels
Don't output all mapped types when generating WSDL, just the
ones we use (and all subtypes).
Anyone know if this is the issue in question?
Yes, this is the cause of the problem. Its possible that 3.2.4 will include an upgrade to axis 1.2, but not certain at this point.