I believe onPartnerInvoked is never called on the 1.3.X codebase

>>> Joni Lee <[email protected]> 1/13/2011 12:52 PM >>>
I've found out that the method onPartnerInvoked has never been called when the 
BPEL process receives a fault message from the external web service (for 
example, in my case is "Authentication of Username Password Token Failed"), 
while other methods (onNewInstanceInvoked, onProcessInvoked) have been called 
sucessfully.
How can this be? Solution?
Thank you!Best Regards
--- On Thu, 1/13/11, Joni Lee <[email protected]> wrote:

From: Joni Lee <[email protected]>
Subject: Fun with MessageExchange Intercept
To: [email protected]
Date: Thursday, January 13, 2011, 4:29 PM

Hi all,
Here I tried some fun to intercept the message exchange routing from the 
external service back to the process with a small class as follows
-------------------
public class FaultInterceptor implements MessageExchangeInterceptor{        
private static
final Log LOG = LogFactory.getLog(FaultInterceptor.class);
    @Override    public void onPartnerInvoked(PartnerRoleMessageExchange mex, 
InterceptorContext itc) throws FailMessageExchangeException, 
FaultMessageExchangeException {
                LOG.debug("blablabla");
              /* ONLY INTERCEPT THE RESPONSE MESSAGE COMING FROM WS */        
if (mex.getStatus() == Status.RESPONSE){            Message m = 
mex.getResponse();            m.setHeaderPart("customeheader", "content");      
      throw new FaultMessageExchangeException("MycustomeFault", 
mex.getCaller(), m);        }    }...}
-----------------
First, ODE log says it registered the implementation class successfully. I want 
to write something to prove that I can really intercept the message.
Question: after invoke an external web service..
- Neiter the echo text "blablabla" nor "MycustomeFault" are printed out in log 
file of ODE. And WHY?- I want to modify the header of the "mex", but it doesn't 
seem right. Please give me some advices to throw out a message of my own.
Thank you very much








      



Reply via email to