[jira] Commented: (SM-1081) A StaticRecipientListAggregator like SplitAggregator is needed
[ https://issues.apache.org/activemq/browse/SM-1081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_40216 ] Andrea Zoppello commented on SM-1081: - Ok, We make this update to allow the message envelope to be optional. That's all. Andrea A StaticRecipientListAggregator like SplitAggregator is needed --- Key: SM-1081 URL: https://issues.apache.org/activemq/browse/SM-1081 Project: ServiceMix Issue Type: Improvement Components: servicemix-eip Affects Versions: 3.1.1 Environment: ServiceMix 3.1.1 Reporter: Andrea Zoppello Fix For: 3.2 Attachments: RecipientListAggregator.java, SplitAggregator.java.patch, StaticRecipientList.java.patch We need a specific aggregator to use in couple with a Static recipient List. To do this we need to: 1) Modify the static recipient list to propagate some information needed to be used by RecipientListAggregator 2) Implement the RecipientListAggregator class 3) With a small update to SplitAggregator class RecipientListAggregator could simply extend SplitAggregator to reuse the aggregation logic. The problem is that the Expression properties are private, so we need to change SplitAgggregator. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SM-999) InOut to InOnly pattern Endpoint for eip-su
[ https://issues.apache.org/activemq/browse/SM-999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39650 ] Andrea Zoppello commented on SM-999: Hi Guillaume, Take a look at the code of the class it.eng.spagosoa.smx.components.sync.Synchronizer in the spagic-components distribution. We need this component basically to address the use case where 1) client applications need to call a webservice binding component and to get a response 2) the process behind binding component could be quite complex ( not just only one se ) 3) the process need to be modelled in visual tool ( Spagic Studio ) By the way if you look at the code you can see that basically the syncronizer that basically it manage an InOutExchange this is keep in and an InOnly exchange is created. If you want more details the Spagic Components Guide contains an example of that. InOut to InOnly pattern Endpoint for eip-su --- Key: SM-999 URL: https://issues.apache.org/activemq/browse/SM-999 Project: ServiceMix Issue Type: Improvement Components: servicemix-eip Reporter: Netflexity Attachments: InOutToInEndpoint.java Please add the following pattern to be able to use components that support only InOnly MEPs for InOut components. Attached file illustrates the idea. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (SM-999) InOut to InOnly pattern Endpoint for eip-su
[ https://issues.apache.org/activemq/browse/SM-999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39650 ] Andrea Zoppello edited comment on SM-999 at 7/12/07 12:19 AM: -- Hi Guillaume, Take a look at the code of the class it.eng.spagosoa.smx.components.sync.Synchronizer in the spagic-components distribution. We need this component basically to address the use case where 1) client applications need to call a webservice binding component and to get a response 2) the process behind binding component could be quite complex ( not just only one se ) 3) the process need to be modelled in visual tool ( Spagic Studio ) By the way if you look at the code you can see that basically it manage an InOutExchange this is keep in and an InOnly exchange is created. If you want more details the Spagic Components Guide contains an example of that. was: Hi Guillaume, Take a look at the code of the class it.eng.spagosoa.smx.components.sync.Synchronizer in the spagic-components distribution. We need this component basically to address the use case where 1) client applications need to call a webservice binding component and to get a response 2) the process behind binding component could be quite complex ( not just only one se ) 3) the process need to be modelled in visual tool ( Spagic Studio ) By the way if you look at the code you can see that basically the syncronizer that basically it manage an InOutExchange this is keep in and an InOnly exchange is created. If you want more details the Spagic Components Guide contains an example of that. InOut to InOnly pattern Endpoint for eip-su --- Key: SM-999 URL: https://issues.apache.org/activemq/browse/SM-999 Project: ServiceMix Issue Type: Improvement Components: servicemix-eip Reporter: Netflexity Attachments: InOutToInEndpoint.java Please add the following pattern to be able to use components that support only InOnly MEPs for InOut components. Attached file illustrates the idea. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SM-999) InOut to InOnly pattern Endpoint for eip-su
[ https://issues.apache.org/activemq/browse/SM-999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39646 ] Andrea Zoppello commented on SM-999: We've done something similar to this in spagic integration platform with Synchronous Comm Point I'ts basically a component that handle an InOut communication with a binding component and propagate a InOnly exchange. Then it mantains the original exchange and when it receives an InOnly back it will give back response in the binding components. An example could be something like: WS ---(InOut) -- Sync -(InOnly)- XSLT -(InOnly)- Groovy Script -(InOnly)- Sync InOut to InOnly pattern Endpoint for eip-su --- Key: SM-999 URL: https://issues.apache.org/activemq/browse/SM-999 Project: ServiceMix Issue Type: Improvement Components: servicemix-eip Reporter: Netflexity Attachments: InOutToInEndpoint.java Please add the following pattern to be able to use components that support only InOnly MEPs for InOut components. Attached file illustrates the idea. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (SM-999) InOut to InOnly pattern Endpoint for eip-su
[ https://issues.apache.org/activemq/browse/SM-999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39646 ] Andrea Zoppello edited comment on SM-999 at 7/11/07 8:04 AM: - We've done something similar to this in spagic integration platform with Synchronous Comm Point I'ts basically a component that handle an InOut communication with a binding component and propagate a InOnly exchange. Then it mantains the original exchange and when it receives an InOnly back it will give back response in the binding components. An example could be something like: WS (InOut) Sync (InOnly) XSLT (InOnly) Groovy Script (InOnly) Sync was: We've done something similar to this in spagic integration platform with Synchronous Comm Point I'ts basically a component that handle an InOut communication with a binding component and propagate a InOnly exchange. Then it mantains the original exchange and when it receives an InOnly back it will give back response in the binding components. An example could be something like: WS ---(InOut) -- Sync -(InOnly)- XSLT -(InOnly)- Groovy Script -(InOnly)- Sync InOut to InOnly pattern Endpoint for eip-su --- Key: SM-999 URL: https://issues.apache.org/activemq/browse/SM-999 Project: ServiceMix Issue Type: Improvement Components: servicemix-eip Reporter: Netflexity Attachments: InOutToInEndpoint.java Please add the following pattern to be able to use components that support only InOnly MEPs for InOut components. Attached file illustrates the idea. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SM-924) Drools 31 namespace support
Drools 31 namespace support Key: SM-924 URL: https://issues.apache.org/activemq/browse/SM-924 Project: ServiceMix Issue Type: Bug Affects Versions: 3.1 Environment: ServiceMix 3.1 Reporter: Andrea Zoppello Attachments: drools.patch We want to support the evaluation of xpath expressions with namespace when writing the rule conditions on drl file To do this we want to introduce support similar to the eip components where namespace context can be specified. Another thing we want to indroduce is to enable to make database checks in the drl file. To do this we can use a DbHelper object and add a method to extract data from xpath in org.servicemix.drools.model.Message -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SM-888) In the Drool 3.1 component is not possible to specify a default target service
[ https://issues.apache.org/activemq/browse/SM-888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Zoppello updated SM-888: --- Attachment: DroolsEndpoint.java.diff I've missed to add the control of exchange status after firing rules before routing to default target service In the Drool 3.1 component is not possible to specify a default target service -- Key: SM-888 URL: https://issues.apache.org/activemq/browse/SM-888 Project: ServiceMix Issue Type: Improvement Components: servicemix-drools Affects Versions: 3.1 Reporter: Andrea Zoppello Attachments: DroolsEndpoint.java.diff, DroolsEndpoint.java.diff It can be util to specify a default target service where the message will be routed if no one of the rule specified in thre rulebase file has been executed -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SM-888) In the Drool 3.1 component is not possible to specify a default target service
In the Drool 3.1 component is not possible to specify a default target service -- Key: SM-888 URL: https://issues.apache.org/activemq/browse/SM-888 Project: ServiceMix Issue Type: Improvement Components: servicemix-drools Affects Versions: 3.1 Reporter: Andrea Zoppello Attachments: DroolsEndpoint.java.diff It can be util to specify a default target service where the message will be routed if no one of the rule specified in thre rulebase file has been executed -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SM-879) EIP XPath Splitter and Drools3.1 used together cause problems in xpath evaluation
EIP XPath Splitter and Drools3.1 used together cause problems in xpath evaluation - Key: SM-879 URL: https://issues.apache.org/activemq/browse/SM-879 Project: ServiceMix Issue Type: Bug Affects Versions: 3.1 Reporter: Andrea Zoppello When a service assembly use an XPath spltter and then a drools router, there are problems in xpath evaluations on the drools router, this because probably the two components are evaluating xpath expressions in the same DOM Document. The right behaviour must ensure that when the splitter component has done his job the resulting sub-elements will be processes as separated documents not related to the original DOM processed by the splitter. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SM-879) EIP XPath Splitter and Drools3.1 used together cause problems in xpath evaluation
[ https://issues.apache.org/activemq/browse/SM-879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Zoppello updated SM-879: --- Attachment: XPathSplitter.java.patch The patch attached resolve the problem reported EIP XPath Splitter and Drools3.1 used together cause problems in xpath evaluation - Key: SM-879 URL: https://issues.apache.org/activemq/browse/SM-879 Project: ServiceMix Issue Type: Bug Affects Versions: 3.1 Reporter: Andrea Zoppello Attachments: XPathSplitter.java.patch When a service assembly use an XPath spltter and then a drools router, there are problems in xpath evaluations on the drools router, this because probably the two components are evaluating xpath expressions in the same DOM Document. The right behaviour must ensure that when the splitter component has done his job the resulting sub-elements will be processes as separated documents not related to the original DOM processed by the splitter. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SM-781) Re: Bug in ScritpComponent when using script attribute
Re: Bug in ScritpComponent when using script attribute
Key: SM-781
URL: https://issues.apache.org/activemq/browse/SM-781
Project: ServiceMix
Issue Type: Bug
Components: servicemix-components
Affects Versions: 3.0
Reporter: Andrea Zoppello
When the script component is configured using the script attribute instead of
scriptText attribute the components doesn't work.
For example:
sm:activationSpec componentName=myGenericGroovymioGroovy
service=foo:myGenericGroovymioGroovy
destinationService=*foo:myScreenOutputmioGroovy*
sm:component
bean
class=org.apache.servicemix.components.groovy.GroovyComponent
property name=script
value=c:/tmp/sm/groovy/testsmx.groovy /
/bean
/sm:component
/sm:activationSpec
fails with message: If no 'compiledScript' is specified you must specify the
'scriptText'
The problems seems to be in the start() method of
org.apache.servicemix.components.script.ScriptComponent class.
in the following lines:
if (compiledScript == null) {
checkScriptTextAvailable();
}
if (compiledScript == null) {
if (engine instanceof Compilable) {
Compilable compilable = (Compilable) engine;
compileScript(compilable);
}
}
I've replaced this code with the code below and it works correctly:
.
if ((compiledScript == null) (script != null)) {
if (engine instanceof Compilable) {
Compilable compilable = (Compilable) engine;
compileScript(compilable);
}
}
if (compiledScript == null) {
checkScriptTextAvailable();
}
.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SM-781) Re: Bug in ScritpComponent when using script attribute
[ https://issues.apache.org/activemq/browse/SM-781?page=all ]
Andrea Zoppello updated SM-781:
---
Attachment: ScriptComponent.java.diff
The file attached is the patch proposed to resolve the problem described
Re: Bug in ScritpComponent when using script attribute
Key: SM-781
URL: https://issues.apache.org/activemq/browse/SM-781
Project: ServiceMix
Issue Type: Bug
Components: servicemix-components
Affects Versions: 3.0
Reporter: Andrea Zoppello
Attachments: ScriptComponent.java.diff
When the script component is configured using the script attribute instead
of scriptText attribute the components doesn't work.
For example:
sm:activationSpec componentName=myGenericGroovymioGroovy
service=foo:myGenericGroovymioGroovy
destinationService=*foo:myScreenOutputmioGroovy*
sm:component
bean
class=org.apache.servicemix.components.groovy.GroovyComponent
property name=script
value=c:/tmp/sm/groovy/testsmx.groovy /
/bean
/sm:component
/sm:activationSpec
fails with message: If no 'compiledScript' is specified you must specify the
'scriptText'
The problems seems to be in the start() method of
org.apache.servicemix.components.script.ScriptComponent class.
in the following lines:
if (compiledScript == null) {
checkScriptTextAvailable();
}
if (compiledScript == null) {
if (engine instanceof Compilable) {
Compilable compilable = (Compilable) engine;
compileScript(compilable);
}
}
I've replaced this code with the code below and it works correctly:
.
if ((compiledScript == null) (script != null)) {
if (engine instanceof Compilable) {
Compilable compilable = (Compilable) engine;
compileScript(compilable);
}
}
if (compiledScript == null) {
checkScriptTextAvailable();
}
.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
