[jira] Updated: (SYNAPSE-718) Supporting Dynamic registry keys in Mediators
[
https://issues.apache.org/jira/browse/SYNAPSE-718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ranga Siriwardena updated SYNAPSE-718:
--
Attachment: patch4.diff
Patch File (Patch4.diff) for implementing Dynamic registry key with XQuery and
Script Mediators.
Supporting Dynamic registry keys in Mediators
-
Key: SYNAPSE-718
URL: https://issues.apache.org/jira/browse/SYNAPSE-718
Project: Synapse
Issue Type: Improvement
Components: Core
Affects Versions: 2.1
Environment: OS - Linux
Reporter: Ranga Siriwardena
Attachments: patch.diff, patch2.diff, patch3.diff, patch4.diff
Currently synapse supporting only static registry keys with mediators. For an
example, XSLT Mediators only allows static keys when creating the mediator.
With this patch synapse will able to provide support for dynamic keys like
xpath expressions. In that case user will able to use XPath kind of approach
to dynamically generate the key instead of a static key.
With the improvement synapse supports both static and dynamic keys as in
following example.
!-- using static key ---
xslt key=xslt-key-req/
!-- using Dynamic key --
xslt key={xpathExpressionToEvaluateKey } /
Also with this improvement XSLT Mediators will able to support multiple
template caching.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] Reopened: (SYNAPSE-718) Supporting Dynamic registry keys in Mediators
[
https://issues.apache.org/jira/browse/SYNAPSE-718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ranga Siriwardena reopened SYNAPSE-718:
---
Applying this improvement for the sequence mediator. Patch3 provides
improvement for the sequence mediator.
Supporting Dynamic registry keys in Mediators
-
Key: SYNAPSE-718
URL: https://issues.apache.org/jira/browse/SYNAPSE-718
Project: Synapse
Issue Type: Improvement
Components: Core
Affects Versions: 2.1
Environment: OS - Linux
Reporter: Ranga Siriwardena
Attachments: patch.diff, patch2.diff
Currently synapse supporting only static registry keys with mediators. For an
example, XSLT Mediators only allows static keys when creating the mediator.
With this patch synapse will able to provide support for dynamic keys like
xpath expressions. In that case user will able to use XPath kind of approach
to dynamically generate the key instead of a static key.
With the improvement synapse supports both static and dynamic keys as in
following example.
!-- using static key ---
xslt key=xslt-key-req/
!-- using Dynamic key --
xslt key={xpathExpressionToEvaluateKey } /
Also with this improvement XSLT Mediators will able to support multiple
template caching.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] Updated: (SYNAPSE-718) Supporting Dynamic registry keys in Mediators
[
https://issues.apache.org/jira/browse/SYNAPSE-718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ranga Siriwardena updated SYNAPSE-718:
--
Attachment: patch3.diff
Patch file for the improvement with sequence mediator.
Supporting Dynamic registry keys in Mediators
-
Key: SYNAPSE-718
URL: https://issues.apache.org/jira/browse/SYNAPSE-718
Project: Synapse
Issue Type: Improvement
Components: Core
Affects Versions: 2.1
Environment: OS - Linux
Reporter: Ranga Siriwardena
Attachments: patch.diff, patch2.diff, patch3.diff
Currently synapse supporting only static registry keys with mediators. For an
example, XSLT Mediators only allows static keys when creating the mediator.
With this patch synapse will able to provide support for dynamic keys like
xpath expressions. In that case user will able to use XPath kind of approach
to dynamically generate the key instead of a static key.
With the improvement synapse supports both static and dynamic keys as in
following example.
!-- using static key ---
xslt key=xslt-key-req/
!-- using Dynamic key --
xslt key={xpathExpressionToEvaluateKey } /
Also with this improvement XSLT Mediators will able to support multiple
template caching.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] Created: (SYNAPSE-731) Dynamic Registry Key Sample
Dynamic Registry Key Sample
---
Key: SYNAPSE-731
URL: https://issues.apache.org/jira/browse/SYNAPSE-731
Project: Synapse
Issue Type: New Feature
Components: Core
Environment: Linux
Reporter: Ranga Siriwardena
This sample demonstrates the use of dynamic keys with mediators. XSLT mediator
is used as an example for that and deference between static and dynamic usage
of keys are shown with that.
Following is the separation of static and dynamic registry keys with new
improvement.
!-- using static key ---
xslt key=xslt-key-req/
!-- using Dynamic key --
xslt key={xpathExpressionToEvaluateKey } /
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] Updated: (SYNAPSE-731) Dynamic Registry Key Sample
[
https://issues.apache.org/jira/browse/SYNAPSE-731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ranga Siriwardena updated SYNAPSE-731:
--
Attachment: synapse_sample_16.xml
Sample with Dynamic key usage.
Dynamic Registry Key Sample
---
Key: SYNAPSE-731
URL: https://issues.apache.org/jira/browse/SYNAPSE-731
Project: Synapse
Issue Type: New Feature
Components: Core
Environment: Linux
Reporter: Ranga Siriwardena
Attachments: synapse_sample_16.xml
This sample demonstrates the use of dynamic keys with mediators. XSLT
mediator is used as an example for that and deference between static and
dynamic usage of keys are shown with that.
Following is the separation of static and dynamic registry keys with new
improvement.
!-- using static key ---
xslt key=xslt-key-req/
!-- using Dynamic key --
xslt key={xpathExpressionToEvaluateKey } /
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] Updated: (SYNAPSE-731) Dynamic Registry Key Sample
[
https://issues.apache.org/jira/browse/SYNAPSE-731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ranga Siriwardena updated SYNAPSE-731:
--
Attachment: (was: synapse_sample_16.xml)
Dynamic Registry Key Sample
---
Key: SYNAPSE-731
URL: https://issues.apache.org/jira/browse/SYNAPSE-731
Project: Synapse
Issue Type: New Feature
Components: Core
Environment: Linux
Reporter: Ranga Siriwardena
This sample demonstrates the use of dynamic keys with mediators. XSLT
mediator is used as an example for that and deference between static and
dynamic usage of keys are shown with that.
Following is the separation of static and dynamic registry keys with new
improvement.
!-- using static key ---
xslt key=xslt-key-req/
!-- using Dynamic key --
xslt key={xpathExpressionToEvaluateKey } /
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] Updated: (SYNAPSE-731) Dynamic Registry Key Sample
[
https://issues.apache.org/jira/browse/SYNAPSE-731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ranga Siriwardena updated SYNAPSE-731:
--
Attachment: dynamic_key_documentation.patch
dynamic_key_sample.patch
Sample for demonstrating dynamic registry key behavior and documentation
related to it.
Dynamic Registry Key Sample
---
Key: SYNAPSE-731
URL: https://issues.apache.org/jira/browse/SYNAPSE-731
Project: Synapse
Issue Type: New Feature
Components: Core
Environment: Linux
Reporter: Ranga Siriwardena
Attachments: dynamic_key_documentation.patch, dynamic_key_sample.patch
This sample demonstrates the use of dynamic keys with mediators. XSLT
mediator is used as an example for that and deference between static and
dynamic usage of keys are shown with that.
Following is the separation of static and dynamic registry keys with new
improvement.
!-- using static key ---
xslt key=xslt-key-req/
!-- using Dynamic key --
xslt key={xpathExpressionToEvaluateKey } /
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] Updated: (SYNAPSE-731) Dynamic Registry Key Sample
[
https://issues.apache.org/jira/browse/SYNAPSE-731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ranga Siriwardena updated SYNAPSE-731:
--
Comment: was deleted
(was: Sample with Dynamic key usage.)
Dynamic Registry Key Sample
---
Key: SYNAPSE-731
URL: https://issues.apache.org/jira/browse/SYNAPSE-731
Project: Synapse
Issue Type: New Feature
Components: Core
Environment: Linux
Reporter: Ranga Siriwardena
Attachments: dynamic_key_documentation.patch, dynamic_key_sample.patch
This sample demonstrates the use of dynamic keys with mediators. XSLT
mediator is used as an example for that and deference between static and
dynamic usage of keys are shown with that.
Following is the separation of static and dynamic registry keys with new
improvement.
!-- using static key ---
xslt key=xslt-key-req/
!-- using Dynamic key --
xslt key={xpathExpressionToEvaluateKey } /
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] Updated: (SYNAPSE-731) Dynamic Registry Key Sample
[
https://issues.apache.org/jira/browse/SYNAPSE-731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ranga Siriwardena updated SYNAPSE-731:
--
Attachment: (was: synapse_sample_16.xml)
Dynamic Registry Key Sample
---
Key: SYNAPSE-731
URL: https://issues.apache.org/jira/browse/SYNAPSE-731
Project: Synapse
Issue Type: New Feature
Components: Core
Environment: Linux
Reporter: Ranga Siriwardena
Attachments: dynamic_key_documentation.patch, dynamic_key_sample.patch
This sample demonstrates the use of dynamic keys with mediators. XSLT
mediator is used as an example for that and deference between static and
dynamic usage of keys are shown with that.
Following is the separation of static and dynamic registry keys with new
improvement.
!-- using static key ---
xslt key=xslt-key-req/
!-- using Dynamic key --
xslt key={xpathExpressionToEvaluateKey } /
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] Updated: (SYNAPSE-731) Dynamic Registry Key Sample
[
https://issues.apache.org/jira/browse/SYNAPSE-731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ranga Siriwardena updated SYNAPSE-731:
--
Attachment: (was: dynamic_key_sample.patch)
Dynamic Registry Key Sample
---
Key: SYNAPSE-731
URL: https://issues.apache.org/jira/browse/SYNAPSE-731
Project: Synapse
Issue Type: New Feature
Components: Core
Environment: Linux
Reporter: Ranga Siriwardena
Attachments: dynamic_key_documentation.patch, dynamic_key_sample.patch
This sample demonstrates the use of dynamic keys with mediators. XSLT
mediator is used as an example for that and deference between static and
dynamic usage of keys are shown with that.
Following is the separation of static and dynamic registry keys with new
improvement.
!-- using static key ---
xslt key=xslt-key-req/
!-- using Dynamic key --
xslt key={xpathExpressionToEvaluateKey } /
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] Updated: (SYNAPSE-731) Dynamic Registry Key Sample
[
https://issues.apache.org/jira/browse/SYNAPSE-731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ranga Siriwardena updated SYNAPSE-731:
--
Attachment: synapse_sample_16.xml
Dynamic Registry Key Sample
---
Key: SYNAPSE-731
URL: https://issues.apache.org/jira/browse/SYNAPSE-731
Project: Synapse
Issue Type: New Feature
Components: Core
Environment: Linux
Reporter: Ranga Siriwardena
Attachments: dynamic_key_documentation.patch, dynamic_key_sample.patch
This sample demonstrates the use of dynamic keys with mediators. XSLT
mediator is used as an example for that and deference between static and
dynamic usage of keys are shown with that.
Following is the separation of static and dynamic registry keys with new
improvement.
!-- using static key ---
xslt key=xslt-key-req/
!-- using Dynamic key --
xslt key={xpathExpressionToEvaluateKey } /
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] Updated: (SYNAPSE-731) Dynamic Registry Key Sample
[
https://issues.apache.org/jira/browse/SYNAPSE-731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ranga Siriwardena updated SYNAPSE-731:
--
Attachment: dynamic_key_sample.patch
Dynamic Registry Key Sample
---
Key: SYNAPSE-731
URL: https://issues.apache.org/jira/browse/SYNAPSE-731
Project: Synapse
Issue Type: New Feature
Components: Core
Environment: Linux
Reporter: Ranga Siriwardena
Attachments: dynamic_key_documentation.patch, dynamic_key_sample.patch
This sample demonstrates the use of dynamic keys with mediators. XSLT
mediator is used as an example for that and deference between static and
dynamic usage of keys are shown with that.
Following is the separation of static and dynamic registry keys with new
improvement.
!-- using static key ---
xslt key=xslt-key-req/
!-- using Dynamic key --
xslt key={xpathExpressionToEvaluateKey } /
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] Updated: (SYNAPSE-718) Supporting Dynamic registry keys in Mediators
[
https://issues.apache.org/jira/browse/SYNAPSE-718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ranga Siriwardena updated SYNAPSE-718:
--
Attachment: (was: patch2.diff)
Supporting Dynamic registry keys in Mediators
-
Key: SYNAPSE-718
URL: https://issues.apache.org/jira/browse/SYNAPSE-718
Project: Synapse
Issue Type: Improvement
Components: Core
Affects Versions: 2.1
Environment: OS - Linux
Reporter: Ranga Siriwardena
Attachments: patch.diff
Currently synapse supporting only static registry keys with mediators. For an
example, XSLT Mediators only allows static keys when creating the mediator.
With this patch synapse will able to provide support for dynamic keys like
xpath expressions. In that case user will able to use XPath kind of approach
to dynamically generate the key instead of a static key.
With the improvement synapse supports both static and dynamic keys as in
following example.
!-- using static key ---
xslt key=xslt-key-req/
!-- using Dynamic key --
xslt key={xpathExpressionToEvaluateKey } /
Also with this improvement XSLT Mediators will able to support multiple
template caching.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] Updated: (SYNAPSE-718) Supporting Dynamic registry keys in Mediators
[
https://issues.apache.org/jira/browse/SYNAPSE-718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ranga Siriwardena updated SYNAPSE-718:
--
Attachment: patch2.diff
Patch file for supporting both static and dynamic registry keys with Validate
Mediators. This improvement is same as above XSLT mediator improvement and with
this, Validate mediator will able to support both static and dynamic keys.
(Some fixes to the XSLT mediator also added with this)
Supporting Dynamic registry keys in Mediators
-
Key: SYNAPSE-718
URL: https://issues.apache.org/jira/browse/SYNAPSE-718
Project: Synapse
Issue Type: Improvement
Components: Core
Affects Versions: 2.1
Environment: OS - Linux
Reporter: Ranga Siriwardena
Attachments: patch.diff, patch2.diff
Currently synapse supporting only static registry keys with mediators. For an
example, XSLT Mediators only allows static keys when creating the mediator.
With this patch synapse will able to provide support for dynamic keys like
xpath expressions. In that case user will able to use XPath kind of approach
to dynamically generate the key instead of a static key.
With the improvement synapse supports both static and dynamic keys as in
following example.
!-- using static key ---
xslt key=xslt-key-req/
!-- using Dynamic key --
xslt key={xpathExpressionToEvaluateKey } /
Also with this improvement XSLT Mediators will able to support multiple
template caching.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] Updated: (SYNAPSE-718) Supporting Dynamic registry keys in Mediators
[
https://issues.apache.org/jira/browse/SYNAPSE-718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ranga Siriwardena updated SYNAPSE-718:
--
Comment: was deleted
(was: Patch file for supporting both static and dynamic registry keys with
Validate Mediators. This improvement is same as above XSLT mediator improvement
and with this, Validate mediator will able to support both static and dynamic
keys.
(Some fixes to the XSLT mediator also added with this))
Supporting Dynamic registry keys in Mediators
-
Key: SYNAPSE-718
URL: https://issues.apache.org/jira/browse/SYNAPSE-718
Project: Synapse
Issue Type: Improvement
Components: Core
Affects Versions: 2.1
Environment: OS - Linux
Reporter: Ranga Siriwardena
Attachments: patch.diff, patch2.diff
Currently synapse supporting only static registry keys with mediators. For an
example, XSLT Mediators only allows static keys when creating the mediator.
With this patch synapse will able to provide support for dynamic keys like
xpath expressions. In that case user will able to use XPath kind of approach
to dynamically generate the key instead of a static key.
With the improvement synapse supports both static and dynamic keys as in
following example.
!-- using static key ---
xslt key=xslt-key-req/
!-- using Dynamic key --
xslt key={xpathExpressionToEvaluateKey } /
Also with this improvement XSLT Mediators will able to support multiple
template caching.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] Updated: (SYNAPSE-718) Supporting Dynamic registry keys in Mediators
[
https://issues.apache.org/jira/browse/SYNAPSE-718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ranga Siriwardena updated SYNAPSE-718:
--
Summary: Supporting Dynamic registry keys in Mediators (was: Supporting
Dynamic registry keys in XSLT Mediators)
Supporting Dynamic registry keys in Mediators
-
Key: SYNAPSE-718
URL: https://issues.apache.org/jira/browse/SYNAPSE-718
Project: Synapse
Issue Type: Improvement
Components: Core
Affects Versions: 2.1
Environment: OS - Linux
Reporter: Ranga Siriwardena
Attachments: patch.diff
Currently synapse supporting only static registry keys with mediators. For an
example, XSLT Mediators only allows static keys when creating the mediator.
With this patch synapse will able to provide support for dynamic keys like
xpath expressions. In that case user will able to use XPath kind of approach
to dynamically generate the key instead of a static key.
With the improvement synapse supports both static and dynamic keys as in
following example.
!-- using static key ---
xslt key=xslt-key-req/
!-- using Dynamic key --
xslt key={xpathExpressionToEvaluateKey } /
Also with this improvement XSLT Mediators will able to support multiple
template caching.
--
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-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] Updated: (SYNAPSE-718) Supporting Dynamic registry keys in Mediators
[
https://issues.apache.org/jira/browse/SYNAPSE-718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ranga Siriwardena updated SYNAPSE-718:
--
Attachment: patch2.diff
Patch file for supporting both static and dynamic registry keys with Validate
Mediators. This improvement is same as above XSLT mediator improvement and with
this, Validate mediator will able to support both static and dynamic keys.
Supporting Dynamic registry keys in Mediators
-
Key: SYNAPSE-718
URL: https://issues.apache.org/jira/browse/SYNAPSE-718
Project: Synapse
Issue Type: Improvement
Components: Core
Affects Versions: 2.1
Environment: OS - Linux
Reporter: Ranga Siriwardena
Attachments: patch.diff, patch2.diff
Currently synapse supporting only static registry keys with mediators. For an
example, XSLT Mediators only allows static keys when creating the mediator.
With this patch synapse will able to provide support for dynamic keys like
xpath expressions. In that case user will able to use XPath kind of approach
to dynamically generate the key instead of a static key.
With the improvement synapse supports both static and dynamic keys as in
following example.
!-- using static key ---
xslt key=xslt-key-req/
!-- using Dynamic key --
xslt key={xpathExpressionToEvaluateKey } /
Also with this improvement XSLT Mediators will able to support multiple
template caching.
--
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-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org
Re: Supporting Dynamic registry keys in Mediators
Hi All,
I did the same improvement for the validate mediator. Attached the patch
file with the same JIRA.
https://issues.apache.org/jira/browse/SYNAPSE-718
Thank You.
On Tue, Jan 18, 2011 at 11:04 AM, Ranga Siriwardena ra...@wso2.com wrote:
Hi All,
Thank you very much for the valuable comments and suggestions. As per
this discussion I have implemented the dynamic registry key feature
for XSLT mediators and with this we will able to cache multiple
templates with XSLT Mediators. According to this improvement user can
specify static-key as a normal string as earlier and
dynamic-keys(xpath expressions) can denoted inside { } . More
details about this improvement is included with following JIRA.
https://issues.apache.org/jira/browse/SYNAPSE-718
Thank you.
On Sat, Jan 8, 2011 at 9:03 AM, indika kumara indika.k...@gmail.com
wrote:
Here, I believe we refers to unique keys - Only difference is how to
calculate keys (static vs dynamic- based on something in requests). A
cache
is a genaric concept that can be applied for many cases, especially when
application data are retrieved from some other place and (or) that
retrieving operation is expensive ( e.g database, file system), and(or)
the
application data exhibits properties such expiration.
On Sat, Jan 8, 2011 at 8:11 AM, Ruwan Linton ruwan.lin...@gmail.com
wrote:
Indika,
You cannot put the key as the index as the same key would result in
different XSLT's for different messages.
I don't think Springs case is dynamic, it is just a matter of selecting
among a set of predefined XSLT's and also they have a static key it
seems.
Further, I don't see a need for a cache, as the SynapseConfiguration
entries already supports this, may be we need to create another type of
an
entry type called cached entry, which are not getting serialized to
configuration file.
Thanks,
Ruwan
On Fri, Jan 7, 2011 at 10:44 PM, indika kumara indika.k...@gmail.com
wrote:
Ruwan,
I have not tried multiple template caching but I feel that it should be
possible. The value resulted from evaluating a key expression (key) vs
a
template instance(value). It is just key-value. Do we need to create an
index? if so, what are the parameter for calculating the index? I
believe it
is a simple cache. A generic cache that can keep any domain
object(application data - template, schema, etc) would be ideal. I
believe a
cache should be able to keep any application data. Such a cache can be
put
in the synapse configuration level, registry level, or any other place.
BTW, It seems that Spring does multiple XSLT template caching [1] - it
looks like their scenario is identical to ours.
Thanks,
Indika
[1] http://forum.springsource.org/archive/index.php/t-13862.html
On Fri, Jan 7, 2011 at 8:37 PM, Ruwan Linton ruwan.lin...@gmail.com
wrote:
Indika,
I agree about the other mediators, but XSLT this cannot be done I
guess.
being able to cache multiple templates on its own would not solve the
problem as it requires some indexing mechanism. In dynamic key case,
the
XSLT is going be dynamic and caching the template with a key
expression will
not work, I expect caching over the evaluated XSLT is not going to be
that
effective too.
Ruwan
On Fri, Jan 7, 2011 at 9:53 AM, indika kumara indika.k...@gmail.com
wrote:
I have not checked the code. But I believe it is possible to modify
the
XSLT mediator to cache multiple templates. In the worst case, caching
multiple transformer instances. We have to evaluate tradeoff between
a
mediator with multiple transformer (or templates) instances vs
multiple
mediator instances.
BTW, the use case at [1] might be worth : use a single validate
mediator instead of a filter mediator + multiple validate mediators.
That
applies for many mediators.
Thanks,
Indika
[1] http://wso2.org/forum/thread/10462
On Fri, Jan 7, 2011 at 7:21 AM, Ruwan Linton ruwan.lin...@gmail.com
wrote:
I agree with Paul 100%.
Supun/Ranga, if you carefully look at the XSLT mediator, it caches
the
XSLT template, template creation in XSLT (basically compiling it) is
an
expensive task, with this approach we cannot cache the XSLT as the
XSLT is
dynamic in this case.
Thanks,
Ruwan
On Thu, Jan 6, 2011 at 3:44 PM, Paul Fremantle pzf...@gmail.com
wrote:
Ok. I can see a few scenarios where this might be useful, but in
general if there are a well-defined set of XSLTs (e.g. say we are
choosing between 10) it would be more efficient to have separate
mediators because they will do the initialization and this might
include a compilation step for the XSLT.
Paul
On Thu, Jan 6, 2011 at 10:03 AM, Supun Kamburugamuva
supu...@gmail.com wrote:
As an example lets take a XSLT transformation.
Depending on the message content user may have several XSLT
transformations specified.
With the current language
[jira] Issue Comment Edited: (SYNAPSE-718) Supporting Dynamic registry keys in Mediators
[
https://issues.apache.org/jira/browse/SYNAPSE-718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12985608#action_12985608
]
Ranga Siriwardena edited comment on SYNAPSE-718 at 1/24/11 5:36 AM:
Patch file for supporting both static and dynamic registry keys with Validate
Mediators. This improvement is same as above XSLT mediator improvement and with
this, Validate mediator will able to support both static and dynamic keys.
(Some fixes to the XSLT mediator also added with this)
was (Author: rangas):
Patch file for supporting both static and dynamic registry keys with
Validate Mediators. This improvement is same as above XSLT mediator improvement
and with this, Validate mediator will able to support both static and dynamic
keys.
Supporting Dynamic registry keys in Mediators
-
Key: SYNAPSE-718
URL: https://issues.apache.org/jira/browse/SYNAPSE-718
Project: Synapse
Issue Type: Improvement
Components: Core
Affects Versions: 2.1
Environment: OS - Linux
Reporter: Ranga Siriwardena
Attachments: patch.diff, patch2.diff
Currently synapse supporting only static registry keys with mediators. For an
example, XSLT Mediators only allows static keys when creating the mediator.
With this patch synapse will able to provide support for dynamic keys like
xpath expressions. In that case user will able to use XPath kind of approach
to dynamically generate the key instead of a static key.
With the improvement synapse supports both static and dynamic keys as in
following example.
!-- using static key ---
xslt key=xslt-key-req/
!-- using Dynamic key --
xslt key={xpathExpressionToEvaluateKey } /
Also with this improvement XSLT Mediators will able to support multiple
template caching.
--
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-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] Created: (SYNAPSE-718) Supporting Dynamic registry keys in XSLT Mediators
Supporting Dynamic registry keys in XSLT Mediators
--
Key: SYNAPSE-718
URL: https://issues.apache.org/jira/browse/SYNAPSE-718
Project: Synapse
Issue Type: Improvement
Components: Core
Affects Versions: 2.1
Environment: OS - Linux
Reporter: Ranga Siriwardena
Currently synapse supporting only static registry keys with mediators. For an
example, XSLT Mediators only allows static keys when creating the mediator.
With this patch synapse will able to provide support for dynamic keys like
xpath expressions. In that case user will able to use XPath kind of approach to
dynamically generate the key instead of a static key.
With the improvement synapse supports both static and dynamic keys as in
following example.
!-- using static key
xslt key=xslt-key-req/
!-- using Dynamic key --
xslt key={xpathExpressionToEvaluateKey } /
Also with this improvement XSLT Mediators will able to support multiple
template caching.
--
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-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] Updated: (SYNAPSE-718) Supporting Dynamic registry keys in XSLT Mediators
[
https://issues.apache.org/jira/browse/SYNAPSE-718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ranga Siriwardena updated SYNAPSE-718:
--
Attachment: patch.diff
Patch file for supporting both static and dynamic registry keys with XSLT
Mediators. Also it allows multiple template caching with XSLT Mediators.
Supporting Dynamic registry keys in XSLT Mediators
--
Key: SYNAPSE-718
URL: https://issues.apache.org/jira/browse/SYNAPSE-718
Project: Synapse
Issue Type: Improvement
Components: Core
Affects Versions: 2.1
Environment: OS - Linux
Reporter: Ranga Siriwardena
Attachments: patch.diff
Currently synapse supporting only static registry keys with mediators. For an
example, XSLT Mediators only allows static keys when creating the mediator.
With this patch synapse will able to provide support for dynamic keys like
xpath expressions. In that case user will able to use XPath kind of approach
to dynamically generate the key instead of a static key.
With the improvement synapse supports both static and dynamic keys as in
following example.
!-- using static key
xslt key=xslt-key-req/
!-- using Dynamic key --
xslt key={xpathExpressionToEvaluateKey } /
Also with this improvement XSLT Mediators will able to support multiple
template caching.
--
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-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] Updated: (SYNAPSE-718) Supporting Dynamic registry keys in XSLT Mediators
[
https://issues.apache.org/jira/browse/SYNAPSE-718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ranga Siriwardena updated SYNAPSE-718:
--
Description:
Currently synapse supporting only static registry keys with mediators. For an
example, XSLT Mediators only allows static keys when creating the mediator.
With this patch synapse will able to provide support for dynamic keys like
xpath expressions. In that case user will able to use XPath kind of approach to
dynamically generate the key instead of a static key.
With the improvement synapse supports both static and dynamic keys as in
following example.
!-- using static key ---
xslt key=xslt-key-req/
!-- using Dynamic key --
xslt key={xpathExpressionToEvaluateKey } /
Also with this improvement XSLT Mediators will able to support multiple
template caching.
was:
Currently synapse supporting only static registry keys with mediators. For an
example, XSLT Mediators only allows static keys when creating the mediator.
With this patch synapse will able to provide support for dynamic keys like
xpath expressions. In that case user will able to use XPath kind of approach to
dynamically generate the key instead of a static key.
With the improvement synapse supports both static and dynamic keys as in
following example.
!-- using static key
xslt key=xslt-key-req/
!-- using Dynamic key --
xslt key={xpathExpressionToEvaluateKey } /
Also with this improvement XSLT Mediators will able to support multiple
template caching.
Supporting Dynamic registry keys in XSLT Mediators
--
Key: SYNAPSE-718
URL: https://issues.apache.org/jira/browse/SYNAPSE-718
Project: Synapse
Issue Type: Improvement
Components: Core
Affects Versions: 2.1
Environment: OS - Linux
Reporter: Ranga Siriwardena
Attachments: patch.diff
Currently synapse supporting only static registry keys with mediators. For an
example, XSLT Mediators only allows static keys when creating the mediator.
With this patch synapse will able to provide support for dynamic keys like
xpath expressions. In that case user will able to use XPath kind of approach
to dynamically generate the key instead of a static key.
With the improvement synapse supports both static and dynamic keys as in
following example.
!-- using static key ---
xslt key=xslt-key-req/
!-- using Dynamic key --
xslt key={xpathExpressionToEvaluateKey } /
Also with this improvement XSLT Mediators will able to support multiple
template caching.
--
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-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org
Re: Supporting Dynamic registry keys in Mediators
Siriwardena ra...@wso2.com
wrote:
Hi All,
Currently we are supporting only static registry keys with
mediators.
For an example, XSLT Mediators only allows static keys when
creating
the mediator. How about having dynamic keys with these kind of
mediators. In that case we can support dynamic keys and with
that,
user will able to use XPath kind of approach to dynamically
generate
the key instead of a static key. WDYT?
Following is an example for that.
!-- using static key --
xslt key=xslt-key-req/
!-- using Dynamic key --
xslt key={ } /
If we are supporting this kind of dynamic key approach, what
should be
the proper way of representing the dynamic key?
Thoughts are welcome.
Thank You.
--
Ranga Siriwardena
Software Engineer
WSO2 Inc.
-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org
--
Paul Fremantle
Co-Founder and CTO, WSO2
Apache Synapse PMC Chair
OASIS WS-RX TC Co-chair
blog: http://pzf.fremantle.org
p...@wso2.com
Oxygenating the Web Service Platform, www.wso2.com
-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org
--
Technical Lead, WSO2 Inc
http://wso2.org
supunk.blogspot.com
-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org
--
Paul Fremantle
Co-Founder and CTO, WSO2
Apache Synapse PMC Chair
OASIS WS-RX TC Co-chair
blog: http://pzf.fremantle.org
p...@wso2.com
Oxygenating the Web Service Platform, www.wso2.com
-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org
--
Ruwan Linton
Software Architect Product Manager
WSO2 Inc.; http://wso2.org
Lean . Enterprise . Middleware
phone: +1 408 754 7388 ext 51789
email: ru...@wso2.com; cell: +94 77 341 3097
blog: http://blog.ruwan.org
linkedin: http://www.linkedin.com/in/ruwanlinton
google: http://www.google.com/profiles/ruwan.linton
tweet: http://twitter.com/ruwanlinton
--
Ruwan Linton
Software Architect Product Manager
WSO2 Inc.; http://wso2.org
Lean . Enterprise . Middleware
phone: +1 408 754 7388 ext 51789
email: ru...@wso2.com; cell: +94 77 341 3097
blog: http://blog.ruwan.org
linkedin: http://www.linkedin.com/in/ruwanlinton
google: http://www.google.com/profiles/ruwan.linton
tweet: http://twitter.com/ruwanlinton
--
Ruwan Linton
Software Architect Product Manager
WSO2 Inc.; http://wso2.org
Lean . Enterprise . Middleware
phone: +1 408 754 7388 ext 51789
email: ru...@wso2.com; cell: +94 77 341 3097
blog: http://blog.ruwan.org
linkedin: http://www.linkedin.com/in/ruwanlinton
google: http://www.google.com/profiles/ruwan.linton
tweet: http://twitter.com/ruwanlinton
--
Ranga Siriwardena
Software Engineer
WSO2 Inc.
Mobile: +94 779808031
-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org
Supporting Dynamic registry keys in Mediators
Hi All,
Currently we are supporting only static registry keys with mediators.
For an example, XSLT Mediators only allows static keys when creating
the mediator. How about having dynamic keys with these kind of
mediators. In that case we can support dynamic keys and with that,
user will able to use XPath kind of approach to dynamically generate
the key instead of a static key. WDYT?
Following is an example for that.
!-- using static key --
xslt key=xslt-key-req/
!-- using Dynamic key --
xslt key={ } /
If we are supporting this kind of dynamic key approach, what should be
the proper way of representing the dynamic key?
Thoughts are welcome.
Thank You.
--
Ranga Siriwardena
Software Engineer
WSO2 Inc.
-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org
Synapse Build failure
Hi, When building Appache-Synapse version- 2.1.0-SNAPSHOT, it gives following error. What should I do to avoid the issue. [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve dependencies for one or more projects in the reactor. Reason: Missing: -- 1) org.apache.httpcomponents:httpcore:jar:4.1-beta3-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.httpcomponents -DartifactId=httpcore -Dversion=4.1-beta3-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.httpcomponents -DartifactId=httpcore -Dversion=4.1-beta3-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.synapse:synapse-nhttp-transport:bundle:2.1.0-SNAPSHOT 2) org.apache.httpcomponents:httpcore:jar:4.1-beta3-SNAPSHOT 2) org.apache.httpcomponents:httpcore-nio:jar:4.1-beta3-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.httpcomponents -DartifactId=httpcore-nio -Dversion=4.1-beta3-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.httpcomponents -DartifactId=httpcore-nio -Dversion=4.1-beta3-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.synapse:synapse-nhttp-transport:bundle:2.1.0-SNAPSHOT 2) org.apache.httpcomponents:httpcore-nio:jar:4.1-beta3-SNAPSHOT Thank you. -- Ranga Siriwardena Software Engineer WSO2 Inc. Mobile: +94 779808031
Re: Synapse Build failure
Thanks Supun. On Sun, Nov 21, 2010 at 7:54 PM, Amila Maha Arachchi ami...@wso2.comwrote: Thanks Supun. Amila. On Sun, Nov 21, 2010 at 7:46 PM, Supun Kamburugamuva supu...@gmail.comwrote: I've changed HTTP Core version to 4.1. Please take a svn update. Thanks, Supun.. On Sun, Nov 21, 2010 at 7:41 PM, Supun Kamburugamuva supu...@gmail.comwrote: Since HTTP Core has released the 4.1 version we can move to that version. I'll update the version. Thanks, Supun.. On Sun, Nov 21, 2010 at 7:32 PM, Amila Maha Arachchi ami...@wso2.comwrote: Hi, I have checked these dependencies in the repository. But there is no dependency by the version 4.1-beta3-SNAPSHOT. Instead there is 4.0-beta3-SNAPSHOT. I have put a separate email mentioning this. thanks, Amila. On Sun, Nov 21, 2010 at 2:54 PM, Ranga Siriwardena ra...@wso2.comwrote: Hi, When building Appache-Synapse version- 2.1.0-SNAPSHOT, it gives following error. What should I do to avoid the issue. [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve dependencies for one or more projects in the reactor. Reason: Missing: -- 1) org.apache.httpcomponents:httpcore:jar:4.1-beta3-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.httpcomponents -DartifactId=httpcore -Dversion=4.1-beta3-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.httpcomponents -DartifactId=httpcore -Dversion=4.1-beta3-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.synapse:synapse-nhttp-transport:bundle:2.1.0-SNAPSHOT 2) org.apache.httpcomponents:httpcore:jar:4.1-beta3-SNAPSHOT 2) org.apache.httpcomponents:httpcore-nio:jar:4.1-beta3-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.httpcomponents -DartifactId=httpcore-nio -Dversion=4.1-beta3-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.httpcomponents -DartifactId=httpcore-nio -Dversion=4.1-beta3-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.synapse:synapse-nhttp-transport:bundle:2.1.0-SNAPSHOT 2) org.apache.httpcomponents:httpcore-nio:jar:4.1-beta3-SNAPSHOT Thank you. -- Ranga Siriwardena Software Engineer WSO2 Inc. Mobile: +94 779808031 -- Technical Lead, WSO2 Inc http://wso2.org supunk.blogspot.com -- Technical Lead, WSO2 Inc http://wso2.org supunk.blogspot.com -- Ranga Siriwardena Software Engineer WSO2 Inc. Mobile: +94 779808031
