We pull down the webservices from other systems and then map them to Java objects using JAX-WS and JAXB. We use ant's wsimport to process the WSDLs and convert them to Java. We ran into the situation recently where we were getting this error;

Caused by: com.sun.xml.internal.bind.v2.runtime.IllegalAnnotationsException: 63 counts of IllegalAnnotationExceptions
There's no ObjectFactory with an XmlElementDecl for the element {http://tempuri.org/}Service.
this problem is related to the following location:
at protected javax.xml.bind.JAXBElement org.tempuri.Service.getServiceResult

One of our vendors had placed their webmethods under the same namespace http://tempuri.org which can be long-handed to temp URI. From the tempura website; "Each XML Web Service needs a unique namespace in order for client applications to distinguish it from other services on the Web. By default, ASP.Net Web Services use http://tempuri.org/ for this purpose. While this suitable for XML Web Services under development, published services should use a unique, permanent namespace." Definitely non-ideal.

The main problem was that they had multiple WSDLs using the same tempuri namespace and the ObjectFactory that was generated from each WSDL was over-writing the previous one. Consequently the JAX-WS Java interfaces for the first WSDL processed was looking for its webmethod in the ObjectFactory and not finding it. The solution was to give those webservices or WSDLs a forced namespace in ant;

< wsimport destdir="${out.dir}" sourcedestdir="${web.dir}" package="package.other.than.tempuri.org" wsdl="${service.url}/${service.name}?WSDL"/ > 

This compiled the WSDLs down into a namespace or our choosing and stopped the clash of the ObjectFactories.

More Reading on Wsdl

• WSDL
• Brief Rundown of Webservices in Java
• IllegalAnnotationExceptions and JAX-WS, JAXB