You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@synapse.apache.org by "Heshan Suriyaarachchi (JIRA)" <ji...@apache.org> on 2010/11/02 07:38:23 UTC
[jira] Created: (SYNAPSE-705) Fixing an issue in the script
mediator
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
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 retrieves 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
[jira] Updated: (SYNAPSE-705) Fixing an issue in the script
mediator
Posted by "Heshan Suriyaarachchi (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Heshan Suriyaarachchi updated SYNAPSE-705:
------------------------------------------
Attachment: SYNAPSE-705.patch
> 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
[jira] Commented: (SYNAPSE-705) Fixing an issue in the script
mediator
Posted by "Heshan Suriyaarachchi (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12927328#action_12927328 ]
Heshan Suriyaarachchi commented on SYNAPSE-705:
-----------------------------------------------
Recreating the issue:
=================
You can use the Synapse configuration given in [1] to recreate the issue. After starting Synapse, with the above mentioned configuration send a stockquote request.
ant stockquote -Daddurl=http://localhost:9000/services/SimpleStockQuoteService -Dtrpurl=http://localhost:8280/ -Dsymbol=MSFT
Capture the response message with TcpMon.
Expected response message:
=======================
HTTP/1.1 500 Internal Server Error
Content-Type: text/xml; charset=UTF-8
Host: 127.0.0.1:8281
SOAPAction: "urn:getQuote"
Date: Tue, 02 Nov 2010 06:11:55 GMT
Transfer-Encoding: chunked
34d
<?xml version='1.0' encoding='UTF-8'?>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
<soapenv:Header xmlns:wsa="http://www.w3.org/2005/08/addressing">
<wsa:MessageID>urn:uuid:96617199D43AF7762811061528457722739393852</wsa:MessageID>
<wsa:Action>urn:getQuote</wsa:Action>
<wsa:RelatesTo>urn:uuid:683D23ADE4892AD61A1288678308322</wsa:RelatesTo>
</soapenv:Header>
<soapenv:Body>
<soapenv:Fault>
<faultcode xmlns:tns="http://www.w3.org/2003/05/soap-envelope">tns:Receiver</faultcode>
<faultstring>Currently , Address endpoint : [ Name : endpoint_urn_uuid_F3FC39CF93F681A11649593938524451942754528 ] [ State : SUSPENDED ]</faultstring>
<detail>
<AppErrorCode>
<TimeStamp>11/2/10 11:41 AM</TimeStamp>
<ErrorCode>8719</ErrorCode>
<ErrorText>Issue has</ErrorText>
</AppErrorCode>
</detail>
</soapenv:Fault>
</soapenv:Body>
</soapenv:Envelope>0
Actual response message:
====================
HTTP/1.1 500 Internal Server Error
Content-Type: text/xml; charset=UTF-8
Host: 127.0.0.1:8281
SOAPAction: "urn:getQuote"
Date: Tue, 02 Nov 2010 06:11:55 GMT
Transfer-Encoding: chunked
34d
<?xml version='1.0' encoding='UTF-8'?>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
<soapenv:Header xmlns:wsa="http://www.w3.org/2005/08/addressing">
<wsa:MessageID>urn:uuid:96617199D43AF7762811061528457722739393852</wsa:MessageID>
<wsa:Action>urn:getQuote</wsa:Action>
<wsa:RelatesTo>urn:uuid:683D23ADE4892AD61A1288678308322</wsa:RelatesTo>
</soapenv:Header>
<soapenv:Body>
<soapenv:Fault>
<faultcode xmlns:tns="http://www.w3.org/2003/05/soap-envelope">tns:Receiver</faultcode>
<faultstring>Currently , Address endpoint : [ Name : endpoint_urn_uuid_F3FC39CF93F681A11649593938524451942754528 ] [ State : SUSPENDED ]</faultstring>
<detail><AppErrorCode><TimeStamp>10/26/10 12:49 PM</TimeStamp><ErrorCode>8719</ErrorCode><ErrorText>Issue has </ErrorText></AppErrorCode></detail>
</soapenv:Fault>
</soapenv:Body>
</soapenv:Envelope>0
[1] - http://heshans.blogspot.com/2010/10/generate-custom-error-messages-with.html
> 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
>
>
> 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
[jira] Reopened: (SYNAPSE-705) Fixing an issue in the script
mediator
Posted by "Hiranya Jayathilaka (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hiranya Jayathilaka reopened SYNAPSE-705:
-----------------------------------------
The patch doesn't solve the problem entirely. Look at the import introduced to the ScriptMessageContext:
import org.mozilla.javascript.xml.XMLObject;
Clearly this is JavaScript specific. We cannot introduce language specific code into ScriptMessageContext or ScriptMediator. We need to fix this the proper way.
> 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
[jira] Updated: (SYNAPSE-705) Fixing an issue in the script
mediator
Posted by "Heshan Suriyaarachchi (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Heshan Suriyaarachchi updated SYNAPSE-705:
------------------------------------------
Description:
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.
was:
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 retrieves 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.
> 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
>
>
> 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
[jira] Commented: (SYNAPSE-705) Fixing an issue in the script
mediator
Posted by "Heshan Suriyaarachchi (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12967097#action_12967097 ]
Heshan Suriyaarachchi commented on SYNAPSE-705:
-----------------------------------------------
Hi Hiranya,
I will fix it and attach a patch. Thanks for pointing out the issue.
> 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
[jira] Resolved: (SYNAPSE-705) Fixing an issue in the script
mediator
Posted by "Supun Kamburugamuva (JIRA)" <ji...@apache.org>.
[ 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
[jira] Commented: (SYNAPSE-705) Fixing an issue in the script
mediator
Posted by "Heshan Suriyaarachchi (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12927340#action_12927340 ]
Heshan Suriyaarachchi commented on SYNAPSE-705:
-----------------------------------------------
Attached the patch to fix the issue.
> 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
[jira] Issue Comment Edited: (SYNAPSE-705) Fixing an issue in the
script mediator
Posted by "Heshan Suriyaarachchi (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12927328#action_12927328 ]
Heshan Suriyaarachchi edited comment on SYNAPSE-705 at 11/2/10 4:28 AM:
------------------------------------------------------------------------
Recreating the issue:
=================
You can use the Synapse configuration given in [1] to recreate the issue. After starting Synapse, with the above mentioned configuration send a stockquote request.
ant stockquote -Daddurl=http://localhost:9000/services/SimpleStockQuoteService -Dtrpurl=http://localhost:8280/ -Dsymbol=MSFT
Capture the response message with TcpMon.
Expected response message:
=======================
HTTP/1.1 500 Internal Server Error
Content-Type: text/xml; charset=UTF-8
Host: 127.0.0.1:8281
SOAPAction: "urn:getQuote"
Date: Tue, 02 Nov 2010 06:11:55 GMT
Transfer-Encoding: chunked
34d
<?xml version='1.0' encoding='UTF-8'?>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
<soapenv:Header xmlns:wsa="http://www.w3.org/2005/08/addressing">
<wsa:MessageID>urn:uuid:96617199D43AF7762811061528457722739393852</wsa:MessageID>
<wsa:Action>urn:getQuote</wsa:Action>
<wsa:RelatesTo>urn:uuid:683D23ADE4892AD61A1288678308322</wsa:RelatesTo>
</soapenv:Header>
<soapenv:Body>
<soapenv:Fault>
<faultcode xmlns:tns="http://www.w3.org/2003/05/soap-envelope">tns:Receiver</faultcode>
<faultstring>Currently , Address endpoint : [ Name : endpoint_urn_uuid_F3FC39CF93F681A11649593938524451942754528 ] [ State : SUSPENDED ]</faultstring>
<detail>
<AppErrorCode>
<TimeStamp>11/2/10 11:41 AM</TimeStamp>
<ErrorCode>8719</ErrorCode>
<ErrorText>Issue has</ErrorText>
</AppErrorCode>
</detail>
</soapenv:Fault>
</soapenv:Body>
</soapenv:Envelope>0
Actual response message:
====================
HTTP/1.1 500 Internal Server Error
Content-Type: text/xml; charset=UTF-8
Host: 127.0.0.1:8281
SOAPAction: "urn:getQuote"
Date: Tue, 02 Nov 2010 06:11:55 GMT
Transfer-Encoding: chunked
34d
<?xml version='1.0' encoding='UTF-8'?>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
<soapenv:Header xmlns:wsa="http://www.w3.org/2005/08/addressing">
<wsa:MessageID>urn:uuid:96617199D43AF7762811061528457722739393852</wsa:MessageID>
<wsa:Action>urn:getQuote</wsa:Action>
<wsa:RelatesTo>urn:uuid:683D23ADE4892AD61A1288678308322</wsa:RelatesTo>
</soapenv:Header>
<soapenv:Body>
<soapenv:Fault>
<faultcode xmlns:tns="http://www.w3.org/2003/05/soap-envelope">tns:Receiver</faultcode>
<faultstring>Currently , Address endpoint : [ Name : endpoint_urn_uuid_F3FC39CF93F681A11649593938524451942754528 ] [ State : SUSPENDED ]</faultstring>
<detail><AppErrorCode><TimeStamp>10/26/10 12:49 PM</TimeStamp><ErrorCode>8719</ErrorCode><ErrorText>Issue has </ErrorText></AppErrorCode></detail>
</soapenv:Fault>
</soapenv:Body>
</soapenv:Envelope>0
Therefore, if you look at the <detail/> element, you can understand the issue.
[1] - http://heshans.blogspot.com/2010/10/generate-custom-error-messages-with.html
was (Author: heshan):
Recreating the issue:
=================
You can use the Synapse configuration given in [1] to recreate the issue. After starting Synapse, with the above mentioned configuration send a stockquote request.
ant stockquote -Daddurl=http://localhost:9000/services/SimpleStockQuoteService -Dtrpurl=http://localhost:8280/ -Dsymbol=MSFT
Capture the response message with TcpMon.
Expected response message:
=======================
HTTP/1.1 500 Internal Server Error
Content-Type: text/xml; charset=UTF-8
Host: 127.0.0.1:8281
SOAPAction: "urn:getQuote"
Date: Tue, 02 Nov 2010 06:11:55 GMT
Transfer-Encoding: chunked
34d
<?xml version='1.0' encoding='UTF-8'?>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
<soapenv:Header xmlns:wsa="http://www.w3.org/2005/08/addressing">
<wsa:MessageID>urn:uuid:96617199D43AF7762811061528457722739393852</wsa:MessageID>
<wsa:Action>urn:getQuote</wsa:Action>
<wsa:RelatesTo>urn:uuid:683D23ADE4892AD61A1288678308322</wsa:RelatesTo>
</soapenv:Header>
<soapenv:Body>
<soapenv:Fault>
<faultcode xmlns:tns="http://www.w3.org/2003/05/soap-envelope">tns:Receiver</faultcode>
<faultstring>Currently , Address endpoint : [ Name : endpoint_urn_uuid_F3FC39CF93F681A11649593938524451942754528 ] [ State : SUSPENDED ]</faultstring>
<detail>
<AppErrorCode>
<TimeStamp>11/2/10 11:41 AM</TimeStamp>
<ErrorCode>8719</ErrorCode>
<ErrorText>Issue has</ErrorText>
</AppErrorCode>
</detail>
</soapenv:Fault>
</soapenv:Body>
</soapenv:Envelope>0
Actual response message:
====================
HTTP/1.1 500 Internal Server Error
Content-Type: text/xml; charset=UTF-8
Host: 127.0.0.1:8281
SOAPAction: "urn:getQuote"
Date: Tue, 02 Nov 2010 06:11:55 GMT
Transfer-Encoding: chunked
34d
<?xml version='1.0' encoding='UTF-8'?>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
<soapenv:Header xmlns:wsa="http://www.w3.org/2005/08/addressing">
<wsa:MessageID>urn:uuid:96617199D43AF7762811061528457722739393852</wsa:MessageID>
<wsa:Action>urn:getQuote</wsa:Action>
<wsa:RelatesTo>urn:uuid:683D23ADE4892AD61A1288678308322</wsa:RelatesTo>
</soapenv:Header>
<soapenv:Body>
<soapenv:Fault>
<faultcode xmlns:tns="http://www.w3.org/2003/05/soap-envelope">tns:Receiver</faultcode>
<faultstring>Currently , Address endpoint : [ Name : endpoint_urn_uuid_F3FC39CF93F681A11649593938524451942754528 ] [ State : SUSPENDED ]</faultstring>
<detail><AppErrorCode><TimeStamp>10/26/10 12:49 PM</TimeStamp><ErrorCode>8719</ErrorCode><ErrorText>Issue has </ErrorText></AppErrorCode></detail>
</soapenv:Fault>
</soapenv:Body>
</soapenv:Envelope>0
[1] - http://heshans.blogspot.com/2010/10/generate-custom-error-messages-with.html
> 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
>
>
> 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