Hi Kumaran, Please try this [1] build.
[1] - http://people.apache.org/~ruwan/synapse/synapse-1.2-SNAPSHOT-bin.zip Thanks, Ruwan On Wed, Apr 2, 2008 at 10:24 PM, Ruwan Linton <[EMAIL PROTECTED]> wrote: > Hi Kumaran, > > I am sorry, I have mistakenly uploaded a corrupted build. I will give you > a new build by tomorrow. I am in home now and the connection is not that > healthy to upload the build. I am really sorry for this and promise to > upload a working build by tomorrow. > > Thanks, > Ruwan > > > On Wed, Apr 2, 2008 at 1:52 PM, Venkatesan, Kumaran < > [EMAIL PROTECTED]> wrote: > > > Ruwan, > > > > > > > > Two jar files were missing and have added the below and server not > > started after the patch. > > > > > > > > 1. XmlSchema-1.3.2-591227.jar > > > > 2. wsdl4j-1.6.2.jar > > > > > > > > Have copied the whole lib folder from the link given by you. > > > > > > > > 2008-04-02 16:14:23,782 [-] [main] DEBUG ManagerBase Loading 0 persisted > > sessions > > > > 2008-04-02 16:14:23,782 [-] [main] DEBUG ManagerBase Finish: Loading > > persisted sessions > > > > 2008-04-02 16:14:23,814 [-] [main] WARN ServerManager Unable to > > register a URLStreamHandlerFactory - Custom URL protocols may > > > > not work properly (e.g. classpath://) > > > > 2008-04-02 16:14:23,814 [-] [main] INFO ServerManager Using the Axis2 > > Repository C:\tomcat5.0\webapps\synapse\WEB-INF\reposit > > > > ory > > > > javax.xml.stream.FactoryConfigurationError: Provider > > com.bea.xml.stream.MXParserFactory not found > > > > at > > javax.xml.stream.FactoryFinder.newInstance(FactoryFinder.java:72) > > > > at javax.xml.stream.FactoryFinder.find(FactoryFinder.java:178) > > > > at javax.xml.stream.FactoryFinder.find(FactoryFinder.java:92) > > > > at > > javax.xml.stream.XMLInputFactory.newInstance(XMLInputFactory.java:136) > > > > at org.apache.axiom.om.util.StAXUtils$7.run(StAXUtils.java:311) > > > > at java.security.AccessController.doPrivileged(Native Method) > > > > at > > org.apache.axiom.om.util.StAXUtils.getXMLInputFactory_perClassLoader(StAXUtils.java:306) > > > > at > > org.apache.axiom.om.util.StAXUtils.getXMLInputFactory(StAXUtils.java:76) > > > > at > > org.apache.axiom.om.util.StAXUtils.createXMLStreamReader(StAXUtils.java:131) > > > > at org.apache.axis2.util.XMLUtils.toOM(XMLUtils.java:596) > > > > at org.apache.axis2.util.XMLUtils.toOM(XMLUtils.java:581) > > > > at > > org.apache.axis2.deployment.DescriptionBuilder.buildOM(DescriptionBuilder.java:97) > > > > at > > org.apache.axis2.deployment.AxisConfigBuilder.populateConfig(AxisConfigBuilder.java:86) > > > > at > > org.apache.axis2.deployment.DeploymentEngine.populateAxisConfiguration(DeploymentEngine.java:641) > > > > at > > org.apache.axis2.deployment.FileSystemConfigurator.getAxisConfiguration(FileSystemConfigurator.java:116) > > > > at > > org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:68 > > > > ) > > > > at > > org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContextFromFileSystem(ConfigurationContextF > > > > actory.java:184) > > > > at org.apache.synapse.ServerManager.start(ServerManager.java:87) > > > > > > > > *With **Regards* > > > > Kumaran > > > > Phone net : 85976 > > > > Direct line: 6331 85976 > > > > > > ------------------------------ > > > > *From:* Ruwan Linton [mailto:[EMAIL PROTECTED] > > *Sent:* Wednesday, April 02, 2008 1:46 PM > > > > *To:* Venkatesan, Kumaran > > *Subject:* Re: [jira] Resolved: (SYNAPSE-264) Add the ability to > > configure thefault detial dynamically in the MakeFault mediator > > > > > > > > Hi Kumaran, > > > > I was trying to put a nightly build on apache, but was unable to > > complete it yet due to some permission issues. I did a build for you [1], > > which includes the fix that I did for the fault mediator. So that, you can > > try this build with the above configuration to generate faults with dynamic > > fault details as expected. > > > > [1] - > > http://builder.wso2.org/download/SYNAPSE-NIGHTLY/artifacts/build-35/synapse-bin > > > > Thanks, > > Ruwan > > > > On Wed, Apr 2, 2008 at 8:57 AM, Venkatesan, Kumaran < > > [EMAIL PROTECTED]> wrote: > > > > Ruwan, > > > > > > > > This solution is simple. > > > > > > > > When this fix will be available for download or how can I proceed to get > > the fixed code. > > > > > > > > *With **Regards* > > > > Kumaran > > > > Phone net : 85976 > > > > Direct line: 6331 85976 > > > > > > ------------------------------ > > > > *From:* Ruwan Linton [mailto:[EMAIL PROTECTED] > > *Sent:* Wednesday, April 02, 2008 6:55 AM > > > > > > *To:* Venkatesan, Kumaran > > *Subject:* Re: [jira] Resolved: (SYNAPSE-264) Add the ability to > > configure thefault detial dynamically in the MakeFault mediator > > > > > > > > Hi Kumaran, > > > > Nice to hear that you got it resolved, but I must say that you could do > > that without this fault generation code by using a FaultMediator as follows; > > > > <makeFault> > > <code ...../> > > <reason ...../> > > <detail expression="get-property("errCode")"/> > > </makeFault> > > > > Thanks, > > Ruwan > > > > On Tue, Apr 1, 2008 at 2:57 PM, Venkatesan, Kumaran < > > [EMAIL PROTECTED]> wrote: > > > > Ruwan, > > > > > > > > When an application throws an exception, I need to send the error code > > to the client as SOAP fault, so that it could be captured > > > > at the client application(RIA application using TIBCO GI) and could be > > redirected to the appropriate screen. > > > > > > > > Now have created a separate fault mediator in which I will extract the > > property "errCode" and set it to the SOAP fault detail. > > > > > > > > ValidationMediator – throw exception > > > > *if* (!soapUserid.equalsIgnoreCase(userId)){ > > > > ctx.setProperty("errCode", "proxy.service.err"); > > > > *throw* *new* SynapseException("Userid from Session object and SOAPXML > > not valid"); > > > > > > > > ------------------------------ > > > > In ProxyFaultMediator.java – Capture the property set on synapse msg > > context > > > > > > > > String errDetail = (String) synCtx.getProperty("errCode"); > > > > *if* (errDetail != *null*) { > > > > SOAPFaultDetail soapFaultDetail = factory.createSOAPFaultDetail(); > > > > soapFaultDetail.setText(errDetail); > > > > fault.setDetail(soapFaultDetail); > > > > > > > > > > > > Now handled the requirement in a different way. > > > > > > > > Thanks a lot. > > > > > > ------------------------------ > > > > *From:* Ruwan Linton [mailto:[EMAIL PROTECTED] > > *Sent:* Tuesday, April 01, 2008 6:56 AM > > *To:* Venkatesan, Kumaran > > *Subject:* Re: [jira] Resolved: (SYNAPSE-264) Add the ability to > > configure thefault detial dynamically in the MakeFault mediator > > > > > > > > Hi Kumaran, > > > > If I am correct your requirement is to change the details value of the > > SOAPFault for each and every message right? > > > > This value has to be a property of the message ideally. So you could > > specify an XPATH as the detail element so that synapse will extract that > > information from the message and put it into the Fault detail. So the > > makefault configuration would be; > > > > <makeFault> > > <code value=""/> > > <reason expression="getproperty('ERROR_MESSAGE')"/> > > <detail expression="XPATH has to come here"/> > > </makeFault> > > > > Basically you can do the same thing in detail element as in the reason > > element (reason element dynamically extracts the ERROR_MESSAGE property from > > each and every message) > > > > If this is not clear to you please state your exact requirement so that > > I can give you a sample config of the fault mediator > > > > Thanks, > > Ruwan > > > > On Mon, Mar 31, 2008 at 7:06 PM, Venkatesan, Kumaran < > > [EMAIL PROTECTED]> wrote: > > > > > > Ruwan, > > > > Not able to understand the solution. > > > > How to achieve this, do you have any sample code for this. > > > > > > > > -----Original Message----- > > From: Ruwan Linton (JIRA) [mailto:[EMAIL PROTECTED] > > Sent: Monday, March 31, 2008 7:14 PM > > To: [email protected] > > Subject: [jira] Resolved: (SYNAPSE-264) Add the ability to configure > > thefault detial dynamically in the MakeFault mediator > > > > > > [ > > https://issues.apache.org/jira/browse/SYNAPSE-264?page=com.atlassian.jir > > a.plugin.system.issuetabpanels:all-tabpanel ] > > > > Ruwan Linton resolved SYNAPSE-264. > > ---------------------------------- > > > > Resolution: Fixed > > Fix Version/s: 1.2 > > > > Fixed on the trunk. Now the fault detail can be added dynamically from > > the message using the expression attribute of the detail element. > > > > <detail expression="XPATH"/> or <detail>TEXT</detail> > > > > > Add the ability to configure the fault detial dynamically in the > > MakeFault mediator > > > > > ------------------------------------------------------------------------ > > ----------- > > > > > > Key: SYNAPSE-264 > > > URL: https://issues.apache.org/jira/browse/SYNAPSE-264 > > > Project: Synapse > > > Issue Type: Improvement > > > Components: Core > > > Reporter: Ruwan Linton > > > Assignee: Ruwan Linton > > > Fix For: 1.2 > > > > > > > > > Add the ability to configure the fault detial dynamically in the > > MakeFault mediator > > > > -- > > This message is automatically generated by JIRA. > > - > > You can reply to this email to add a comment to the issue online. > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > This email is confidential. If you are not the addressee tell the sender > > immediately and destroy this email > > without using, sending or storing it. Emails are not secure and may > > suffer errors, viruses, delay, > > interception and amendment. Standard Chartered PLC and subsidiaries > > ("SCGroup") do not accept liability for > > damage caused by this email and may monitor email traffic. > > > > > > > > > > -- > > Ruwan Linton > > http://www.wso2.org - "Oxygenating the Web Services Platform" > > > > This email is confidential. If you are not the addressee tell the sender > > immediately and destroy this email > > > > without using, sending or storing it. Emails are not secure and may suffer > > errors, viruses, delay, > > > > interception and amendment. Standard Chartered PLC and subsidiaries > > ("SCGroup") do not accept liability for > > > > damage caused by this email and may monitor email traffic. > > > > > > > > > > -- > > Ruwan Linton > > http://www.wso2.org - "Oxygenating the Web Services Platform" > > > > This email is confidential. If you are not the addressee tell the sender > > immediately and destroy this email > > > > without using, sending or storing it. Emails are not secure and may suffer > > errors, viruses, delay, > > > > interception and amendment. Standard Chartered PLC and subsidiaries > > ("SCGroup") do not accept liability for > > > > damage caused by this email and may monitor email traffic. > > > > > > > > > > -- > > Ruwan Linton > > http://www.wso2.org - "Oxygenating the Web Services Platform" > > > > This email is confidential. If you are not the addressee tell the sender > > immediately and destroy this email > > without using, sending or storing it. Emails are not secure and may suffer > > errors, viruses, delay, > > interception and amendment. Standard Chartered PLC and subsidiaries > > ("SCGroup") do not accept liability for > > damage caused by this email and may monitor email traffic. > > > > > > > -- > Ruwan Linton > http://www.wso2.org - "Oxygenating the Web Services Platform" > -- Ruwan Linton http://www.wso2.org - "Oxygenating the Web Services Platform"
