Preventing @WebServices on the classpath from being initialised in Weblogic
Is it possible to prevent WebLogic scanning for and creating classes with @WebService annotations when the server starts?
I am working on an application where there are a number of @WebServices on the classpath, but they do not apply functionally to this particular application (they are part of a common library and are used by other applications, but not this one). Without other supporting features in place they explode on instantiation.
We also have other cases where we want to selectively expose some services for particular deployments without rebuilding the application each time. Under other application servers, these can be selectively deployed by configuring sun-jaxws.xml, but when deployed under WebLogic, all the web services end up being exposed.