Hello Christian, I could suggest another way to access the header information, it's a kind of recommended way to do it in ODE however in case of sending heeaders. Since BPEL can't access headers directly you could try to transform the header information you are interested in, in the IL into a separate message part.
Renat On 11.02.10 11:12, "Christian Schouten" <[email protected]> wrote: Dear all, I am running Intalio|BPMS, which is Apache ODE on top of Axis2. Now, in my BPEL process I need to access the SOAP envelope's header (to be specific, I need to access the <wsse:BinarySecurityToken> element). After some searching, I came to the conclusion that the best way seems to be to create a static function in a JAR file (referencable as <bpel:from>prefix:functionName($thisReceive__requestRequestMsg.body/name space:wsdlField, "param")</bpel:from>) that can retrieve the ServiceClient instance, then get the OperationContext, then get the MessageContext in which I can get the Header and find an element. I've succeeded in creating JARs and referencing functions from an ODE process problem-free. IMHO, since the entire ODE process is within a single request/response dialog, the security information should be available somewhere. Question 1: Do you agree that this is the way to go or can anybody suggest an alternative way of obtaining the WS-Security information? Question 2: Once I'm in the JAR called through ODE, how can I reference the (Axis2) ServiceClient instance? Any help is most appreciated, Best regards, Christian C. Schouten
