SOAP HandlerChain class not invoked

Question

I've seen lots of posts about getting a HandlerChain class invoked, but I can't seem to find the magic cure.
I have an EJB web service with the HandlerChain annotation and a SOAP handler and a handler-chain.xml file. But the handler does not get invoked.  I was wondering if anyone HAS been able to get one to work using the HanderChain annotation for a weblogic deployment within an EJB annotated as a web service.
EJB code:
package foo.bar;
import ...
@WebService(portName = "RunWebServiceSOAP", serviceName = "RunWebService", targetNamespace = "http://foo.bar/RunWebService/", wsdlLocation = "RunWebService.wsdl", endpointInterface = "foo.bar.RunWebService")
@SchemaValidation
@BindingType(SOAPBinding.SOAP12HTTP_BINDING)
@Stateless
@Local(RunWebService.class)
@TransactionAttribute(TransactionAttributeType.REQUIRED)
@HandlerChain(file="handler-chain.xml") <<<--------------------HANDLER CHAIN ANNOTATION
//@HandlerChain(file="../..handler-chain.xml") <<<-- ALTERNATE ATTEMPT
public class RunWebServiceImpl implements RunWebService {
Handler code:
package boo.flork;
public  class LowLevelSoapMsgPrinterHandler implements SOAPHandler<SOAPMessageContext> {
  @Override
  public boolean handleMessage(SOAPMessageContext smc) {
Handler.xml file:
<?xml version="1.0" encoding="UTF-8"?>
<handler-chains xmlns="http://java.sun.com/xml/ns/javaee">
  <handler-chain>
    <handler>
      <handler-class>boo.flork.LowLevelSoapMsgPrinterHandler</handler-class>
    </handler>
  </handler-chain>
</handler-chains>
Deployment locations of the handler xml file:
1) my_app.ear/my_ejb.ejb/handler-chain.xml
2) my_app.ear/my_ejb.ejb/handler-chain.xml
3) my_app.ear/my_ejb.ejb/foo/bar/handler-chain.xml
Kind of stumped here, anyone have any success with weblogic and a HandlerChain?

Answer 1

Hello Chintan,
I can't find any way to prevent the JSR168/286 portlet container from handling the exceptions during render. There is an option (specified in WEB-INF/weblogic-portlet.xml) which allows you to specify a particular JSP that gets called when an exception is caught during render, but any exceptions thrown by the JSP will also be handled and converted into "normal markup" rather than a WSRP SOAP fault. This would mean any JAX RPC handler (or consumer-side interceptor) wouldn't see an explicit fault message.
So the answer to both questions 1 and 3 is that because the container is sending the error message embedded in markup, rather than a fault message, there is no way for the RPC handler or the interceptor to capture the exception as a fault. If you want, you can contact Oracle support and refer to issue 9645339. As a workaround, you could make the RPC / interceptor look at the markup for an embedded error message or special tag, rather than a fault message. If you took advantage of the error-handling JSP configurable in weblogic-portlet.xml you could even have the JSP include specific markers that the RPC handler / interceptor can look for. To configure the error JSP in the weblogic-portlet.xml file, you will need to add a section for each portlet along the lines of this:
<portlet>
   <portlet-name>nameFromPortlet.xml</portlet-name>
   <supports>
        <mime-type>text/html</mime-type>
        <error-uri>path/to/error.jsp</error-uri>
   </supports>
</portlet>If you have any questions about this suggestion, let me know!
For question #2, I honestly don't know the best way to get the HttpServletRequest from there.
Kevin