servicemix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrea Zoppello (JIRA)" <>
Subject [jira] Commented: (SM-1248) ServiceMix Drools Enhancements
Date Tue, 26 Feb 2008 11:15:17 GMT


Andrea Zoppello commented on SM-1248:


1) What you suggest to do when exchange Is InOut??

2) defaultTargetService in my point of view must be used, where you want specify service in
terms of
qname, otherwise you'll use the default targetURI

3) Agree on the separator observation.

4) I simply need a way that user express the concept of an "application fault", but as i explained
this from a jbi point of view is a "correct message" i just implemented a new method in jbi
helper so the user could use jbi helper to logically express this three situation

a) nomal routing with jbi route
b) fail with a jbi fault ( jbi fault )
c) fail logically "faultToDefaultTarget"

5) regards sender and correlation id, i've some doubt on this, i simply take our previous
patches ( that was rererred to smx 3.1.x ), if this is not needed anymore, we could avoid

I agree with probably the "faultToDefaultTarget" could be avoided but this allow the rules
writer to distiguish
the case of both jbi and logical fault.

5) I've used the smx 3.2.1 source and used the create patch command.

> ServiceMix Drools Enhancements
> ------------------------------
>                 Key: SM-1248
>                 URL:
>             Project: ServiceMix
>          Issue Type: Improvement
>          Components: servicemix-drools
>    Affects Versions: 3.2.1
>            Reporter: Andrea Zoppello
>         Attachments:,
> 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.

View raw message