In fact, websphere 8.5 corresponds to Java EE 6, which means that the container must scan the classpath of the web application to find the annotated @webservice classes and deploy them as running web services.
However, depending on the servlet specification used (given in the web.xml file), scanning will not be performed: it should be automatically performed starting from version 2.5 of the specification.
For older web applications, the Websphere solution must place a special attribute in the MANIFEST.MF of the corresponding war: the UseWSFEP61ScanPolicy key and true. See here for more details.
The servlet 3.0 specification also has a parameter that controls scanning (this is usually used to speed up the initialization of a cold start of an application). Inserting metadata-complete = "true" in the root tag of your web.xml 3.0 deployment descriptor will prevent crawling (and false allows)
source share