Asankha With the Signing/Enc am I right in understanding that the target service (Axis2) can't understand the messages that Synapse is creating?
Paul Seems like a simple issue (104). Can we get a timeline? On 10/4/06, Asankha C. Perera <[EMAIL PROTECTED]> wrote:
Paul I have just checked in the changes for the new Policy framework with two sample services which could be deployed on an Axis2 instance and a sample Synapse configuration to demonstrate this. Though the first example works, the second example which demonstrates signing and encryption fails on the Axis2 server side currently due to an issue I couldn't figure out yet with help from Ruchith. But it seems like its not on Synapse side, and hence I'm checking in these changes. Also when Rampart is being used, we are hit by http://issues.apache.org/jira/browse/WSCOMMONS-104 which prevents Synapse from reading a SOAP fault in an incoming fault message. This again is out of our scope, and should work once Axiom is fixed - though this may take some time. asankha Asankha C. Perera wrote: > Paul > > I'm overall +1 to your plan to release 0.90 now, and I have updated > Synapse to be in sync with the recent changes to Policy/neethi. I will > check this in ASAP with a few more tests. Then I will work on the > documents and prepare for this. > > asankha > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Paul Fremantle VP/Technology, WSO2 and OASIS WS-RX TC Co-chair http://bloglines.com/blog/paulfremantle [EMAIL PROTECTED] "Oxygenating the Web Service Platform", www.wso2.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
