You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Gert Vanthienen (JIRA)" <ji...@apache.org> on 2008/08/07 09:07:52 UTC

[jira] Resolved: (SM-1248) ServiceMix Drools Enhancements

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

Gert Vanthienen resolved SM-1248.
---------------------------------

    Resolution: Fixed

Instead of doing the proposed change, we should revamp servicemix-drools to support full asynchronous messaging support (cfr. SM-1502)

> ServiceMix Drools Enhancements
> ------------------------------
>
>                 Key: SM-1248
>                 URL: https://issues.apache.org/activemq/browse/SM-1248
>             Project: ServiceMix
>          Issue Type: Improvement
>          Components: servicemix-drools
>    Affects Versions: 3.2.1
>            Reporter: Andrea Zoppello
>            Assignee: Guillaume Nodet
>             Fix For: 3.3
>
>         Attachments: DroolsEndpoint.java.patch, JbiHelper.java.patch
>
>
> To be complete the servicemix 3.2.1 drools components, require some enhancements:
> 1) There's the need to support a default destination, where exchange will be routed if none rules in the drools file is verified.
> To support this, we need to provide a way to specify default destinations. there will be a defaultTargetService ( QName ) attribute and a defaultTargetURI attribute in drools endpoint class. ( defaultTargetURI will have the precedence on defaultTargetServiceAttribute)
> 2) We must add the possibility to configure not only global "objects" for memory but also a list of "asserted objects" to be asserted in memory ( so it's possible to use that objects in LHS part of rules )
> 3) The actual code of jbi helper does not care about sender and correlation id.
> 4) We need a method in jbi helper object to support the concept of  fault withn the flow, ( to default destination ) without generate a jbi fault. a fault in flow from jbi point of view is a "correct" normalized message.
> The attached patches solve all the above in a very generic way.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.