Hi,
We have a web application which exposes some custom web services (not DFS based) and uses DFS SDK (remote) client to access EMC Documentum. The WebServices in the webapp are generated with JAX-WS, and we are using annotations to define handlers for that webservice to do input request validation and logging.
The webservice and the handlers are working fine in standalone (with an EnpointPublisher) mode or when deployed in Tomcat.
But when we deploy the webapp in WebLogic (12.1.1 as we use 6.7 SP2) the handlers are totally getting ignored, no logging, no request validation, which is quite painful.
In the service implementation class we have the annotations:
@SchemaValidation
@HandlerChain(file = "handlers.xml")
@WebService(endpointInterface = "mypkg.service.MyWebService")
public class MyWebServiceImpl {
//...
}
In the .war/WEB-INF/classes/handlers.xml we have the handler definitions:
<?xml version="1.0" encoding="UTF-8"?>
<handler-chains xmlns="http://java.sun.com/xml/ns/javaee">
<handler-chain>
<handler>
<handler-class>mypkg.handlers.LoggingHandler</handler-class>
</handler>
<handler>
<handler-class>mypkg.handlers.ValidationHandler</handler-class>
</handler>
</handler-chain>
</handler-chains>
In the .ear/META-INF/weblogic-application.xml we have these which are needed for DFS SDK client to work:
<?xml version="1.0" encoding="UTF-8"?>
<weblogic-application xmlns="http://www.bea.com/ns/weblogic/90">
<prefer-application-resources>
<resource-name>META-INF/services/*</resource-name>
</prefer-application-resources>
</weblogic-application>
Somewhere I found that the statements above in the weblogic-application.xml can cause that the handlers are ignored.
Does somebody have experience how to make it work?
Is it working only with DFS based web services? Or maybe by modifying APP-INF\classes\authorized-service-handler-chain.xml in the ear? How is it picked up and ours not?
Thank you for any clues,
Mike
