Hi Balaji, After deeply digging in to the issue, I have fixed this issue. Please see the JIRA SYNAPSE-157 [1] for more details on this.
I have tried this issues on a slightly different configuration than yours, so check this with your exact configuration and get back to me if there are any issues.. [1] - https://issues.apache.org/jira/browse/SYNAPSE-157 Thanks, Ruwan On 10/19/07, Ruwan Linton <[EMAIL PROTECTED]> wrote: > > Hi Balaji, > > See my comments inline; > > On 10/19/07, balaji hari <[EMAIL PROTECTED]> wrote: > > > > > > Hi Ruwan, > > > > Actually the configuration file i sent is the latest one and it still > > works > > with Sep 25th SNAPSHOT. > > > Well there was a bug in those days (even in 1.0 release) that is if you > specify an endpoint inside send in the out path it wont take that endpoint > to the account and just sends the message back to the caller and I have > fixed this, so your configuration should not work after that fix. Seems like > that bug presented a wrong confg to be pretended as a right config :D > > And I made the changes you suggested and it works with the latest version > > now. Thanks! > > > You are more than welcome!!!! > > Currently we are running into an issue when trying to send soap12 request. > > > > Actually adding an attribute > > version="soap12" to makefault mediator throws an error. > > > This is strange, yes there is a bug here but I was unable to fix this yet > because it is coming either from Rampart or AXIOM. I will try my best to > resolve this ASAP and will do it before the 1.1 RC1 for sure. If this is a > blocker for you, there is a workaround for this which I can do in a minute > (if there are no details for the fault detach the default Detail element) > but is not the very right solution. Please do let me know if it is so, if > not, we may need to wait for a new AXIOM (or Rampart) release as same as the > XmlSchema release for that xsd problem. > > I will try my best to figure out what is going wrong here soon. > > Thanks, > Ruwan > > I have attached output right from beginning of the validate mediator. > > http://www.nabble.com/file/p13284520/console.txt console.txt and latest > > synapse configuration. > > http://www.nabble.com/file/p13284520/websvc_raterank_validate.xml > > websvc_raterank_validate.xml > > > > Balaji > > > > > > Ruwan Linton wrote: > > > > > > Hi Balaji, > > > > > > You need to add a send and a drop mediator to the end of the onFail > > > mediators (i.e after the property mediator) as follows. > > > > > > <on-fail> > > > <makefault> > > > <code value="tns:Sender"/> > > > <reason expression="get-property('ERROR_MESSAGE')"/> > > > </makefault> > > > <property name="RESPONSE" value="true"/> > > > <send/> > > > <drop/> > > > </on-fail> > > > > > > This is because earlier in you configuration you were having a default > > > send > > > mediator out of the validate mediator which gets executed and sent the > > > > > message back, but it seems now you have changed that to direct to a > > > particular endpoint. The above suggestion should resolve your problem. > > > > > > Thanks, > > > Ruwan > > > > > > On 10/18/07, balaji hari < [EMAIL PROTECTED]> wrote: > > >> > > >> > > >> Validation feature was working good with synapse build taken from svn > > on > > >> 9/25/2007. But it seems to be broken in oct - 9 / oct 12 build. > > >> > > >> After executing on-fail mediator synapse is not sending the > > validation > > >> error > > >> back. Instead it forwards the message to server configured in send > > >> mediator! > > >> > > >> I have attached synapse configuration. > > >> > > >> Balaji http://www.nabble.com/file/p13267546/websvc_raterank_validate.xml > > > > >> websvc_raterank_validate.xml > > >> > > >> > > >> > > >> asankha wrote: > > >> > > > >> > Hi Balaji > > >> > > > >> > We are targetting end of October as it stands now > > >> > > > >> > asankha > > >> > > > >> > balaji hari wrote: > > >> >> Hi Ruwan, > > >> >> > > >> >> Great it works! Can we know the approximate release schedule for > > >> >> Synapse1.1? > > >> >> > > >> >> Balaji > > >> >> > > >> >> > > >> >> > > >> >> Ruwan Linton wrote: > > >> >> > > >> >>> Hi Asankha, > > >> >>> > > >> >>> Thanks for pointing this out, but when I tried this, > > ERROR_MESSAGE > > >> >>> property > > >> >>> was not set on to the MC in the validate mediator failure. > > >> >>> > > >> >>> This is because the Validate mediator is handling the failure > > cases > > >> >>> inside > > >> >>> itself (not propagates out) and mediate using the onfail sequence > > in > > >> >>> case > > >> >>> of > > >> >>> a validation failure. There fore our ErrorHandler will not be > > invoked > > >> in > > >> >>> the > > >> >>> validate failure case and this property wont be set in to the MC. > > > > >> >>> > > >> >>> So, I had to change the validate mediator code to set that > > property > > >> >>> inside > > >> >>> the mediator itself. I have commited this change. > > >> >>> > > >> >>> Balaji, if you get a build of the current SVN head, you will be > > able > > >> to > > >> >>> use > > >> >>> this property explained by Asankha. > > >> >>> > > >> >>> Thanks, > > >> >>> Ruwan > > >> >>> > > >> >>> On 9/22/07, Asankha C. Perera <[EMAIL PROTECTED] > wrote: > > >> >>> > > >> >>>> Balaji > > >> >>>> > > >> >>>> Did you check the "ERROR_MESSAGE" property after the validation > > >> >>>> failure? > > >> >>>> This should contain the text from the schema validator. Check > > >> >>>> http://ws.apache.org/synapse/Synapse_Configuration_Language.html > > for > > >> >>>> the > > >> >>>> reference to the above property - we will enhance the > > documentation > > >> and > > >> >>>> clearly exposes such properties in 1.1 release. > > >> >>>> > > >> >>>> Ruwan - lets check the above before a JIRA is opened, and if it > > >> needs > > >> >>>> an > > >> >>>> improvement lets open a new JIRA > > >> >>>> > > >> >>>> asankha > > >> >>>> > > >> >>>> Ruwan Linton wrote: > > >> >>>> > > >> >>>> Hi Balaji, > > >> >>>> > > >> >>>> AFAIK, this should go to the improvements list. Can you raise an > > >> >>>> improvement JIRA on this. We will be able to get this in to the > > >> >>>> 1.1release which is coming soon. If you can try nightly builds > > or > > >> build > > >> >>>> from > > >> >>>> source we will be able to provide this functionality within next > > >> week. > > >> >>>> > > >> >>>> Thanks for the information, > > >> >>>> > > >> >>>> Thanks, > > >> >>>> Ruwan > > >> >>>> > > >> >>>> On 9/22/07, balaji hari < [EMAIL PROTECTED] > wrote: > > >> >>>> > > >> >>>>> We tried to use validate mediator for validating XML against > > schema > > >> >>>>> for > > >> >>>>> web > > >> >>>>> service. > > >> >>>>> How do we access the validation error messages generated in > > >> >>>>> ValidateMediator? > > >> >>>>> > > >> >>>>> Synapse1.0 sample_7 provides a way for generating static error > > >> >>>>> message. > > >> >>>>> > > >> >>>>> <definitions xmlns=" http://ws.apache.org/ns/synapse";> > > >> >>>>> <localEntry key="validate_schema" src="file:shipment.xsd"/> > > >> >>>>> <in> > > >> >>>>> <validate> > > >> >>>>> <schema key="validate_schema"/> > > >> >>>>> <on-fail> > > >> >>>>> <!-- if the request does not validate againt > > schema > > >> >>>>> throw a > > >> >>>>> fault --> > > >> >>>>> <makefault> > > >> >>>>> <code > > value="tns:Receiver" > > >> >>>>> xmlns:tns="http://www.w3.org/2003/05/soap-envelope"/> > > >> >>>>> <reason > > expression="Test > > >> Error > > >> >>>>> message"/> > > >> >>>>> </makefault> > > >> >>>>> <property name="RESPONSE" value="true"/> > > >> >>>>> </on-fail> > > >> >>>>> </validate> > > >> >>>>> </in> > > >> >>>>> <send/> > > >> >>>>> </definitions> > > >> >>>>> > > >> >>>>> Any pointers or suggestions would be greatly appreciated. > > >> >>>>> > > >> >>>>> Thanks in advance > > >> >>>>> Balaji > > >> >>>>> -- > > >> >>>>> View this message in context: > > >> >>>>> > > >> >>>>> > > >> >>>> > > >> > > http://www.nabble.com/Access-to-validation-error-message-tf4498668.html#a12830101 > > >> >>>> > > >> >>>>> Sent from the Synapse - Dev mailing list archive at Nabble.com. > > >> >>>>> > > >> >>>>> > > >> >>>>> > > >> --------------------------------------------------------------------- > > >> >>>>> To unsubscribe, e-mail: [EMAIL PROTECTED] > > >> >>>>> For additional commands, e-mail: [EMAIL PROTECTED] > > >> >>>>> > > >> >>>>> > > >> >>>>> > > >> >>>> -- > > >> >>>> Ruwan Linton > > >> >>>> http://www.wso2.org - "Oxygenating the Web Services Platform" > > >> >>>> > > >> >>>> > > >> >>>> > > >> >>> -- > > >> >>> Ruwan Linton > > >> >>> http://www.wso2.org - "Oxygenating the Web Services Platform" > > >> >>> > > >> >>> > > >> >>> > > >> >> > > >> >> > > >> > > > >> > > > >> > > >> -- > > >> View this message in context: > > >> http://www.nabble.com/Access-to-validation-error-message-tf4498668.html#a13267546 > > > > >> Sent from the Synapse - Dev mailing list archive at Nabble.com. > > >> > > >> > > >> --------------------------------------------------------------------- > > >> To unsubscribe, e-mail: [EMAIL PROTECTED] > > >> For additional commands, e-mail: [EMAIL PROTECTED] > > >> > > >> > > > > > > > > > -- > > > Ruwan Linton > > > http://www.wso2.org - "Oxygenating the Web Services Platform" > > > > > > > > > > -- > > View this message in context: > > http://www.nabble.com/Access-to-validation-error-message-tf4498668.html#a13284520 > > > > Sent from the Synapse - Dev mailing list archive at Nabble.com. > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > -- > Ruwan Linton > http://www.wso2.org - "Oxygenating the Web Services Platform" > -- Ruwan Linton http://www.wso2.org - "Oxygenating the Web Services Platform"
