You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@synapse.apache.org by "Supun Kamburugamuva (JIRA)" <ji...@apache.org> on 2010/11/25 07:38:14 UTC

[jira] Resolved: (SYNAPSE-705) Fixing an issue in the script mediator

     [ https://issues.apache.org/jira/browse/SYNAPSE-705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Supun Kamburugamuva resolved SYNAPSE-705.
-----------------------------------------

    Resolution: Fixed

Applied the patch. Thanks Heshan for the contribution.

> Fixing an issue in the script mediator
> --------------------------------------
>
>                 Key: SYNAPSE-705
>                 URL: https://issues.apache.org/jira/browse/SYNAPSE-705
>             Project: Synapse
>          Issue Type: Bug
>          Components: Script mediator
>    Affects Versions: NIGHTLY
>         Environment: Ubuntu 10.10,
> JDK 1.6
>            Reporter: Heshan Suriyaarachchi
>             Fix For: FUTURE
>
>         Attachments: SYNAPSE-705.patch
>
>
> When using makefault mediator to generate custom error messages, we can populate the <details/> element with an xpath expression. When we set a property String in the script and retrieve later in the  configuration, this works perfectly. But if you set an XML object to the property and later retrieve it and populate the <details/> element, the XML within the <details/> element would not display properly. 
> I would add a sample configuration to prove my point. I am currently working on a fix for this. Once I am done with the fix will attach it to the jira.
> Regards,
> Heshan. 

-- 
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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org