[JBoss ESB Development] - Re: XPath Routing
by Kevin.Conner＠jboss.com
"tfennelly" wrote : Right... I know I said it already (indirectly perhaps :) ), but I actually think there would be less confusion for the user if we made a clean break from the ContenBasedRouter action config. We could still use the same underlying code. I think there's nothing more confusing for things to look "nearly the same", but for them to not really be the same and to have subtle little differences that need to be explained in parallel.
And it could also be argued that it is confusing to have multiple different actions doing the same job (content based routing). We could spend a long time arguing back and forwards about the merits of each when
- we don't have the time
- they are functionally equivalent.
We are not creating another mechanism when the original author has already added one. Okay, it is not as clean as I would have liked and may not have been how we would do it but it does exist and we will use it.
We also do *not* have to use the same attributes as the drools version if they do not make sense. As I already pointed out the extension mechanism passes the configuration through to the implementation.
Kev
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4256701#4256701
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4256701
17 years
[JBoss ESB Development] - Re: XPath Routing
by tfennelly
"burrsutter" wrote : For the inline use case, can we do away with the destination-name concept, it seems harder to use and doesn't add significant value.
|
| | <action class="org.jboss.soa.esb.actions.ContentBasedRouter" name="ContentBasedRouter">
| | <property name="cbrClass" value="XPath"/>
| | <property name="ruleSet">
| | <rule target-service="OrderCategory:BlueService" expression="/order/header[@cat='blue']" />
| | <rule target-category="OrderCategory" target-service="RedService"" expression="/order/header[@cat='red']" />
| | </property>
| | </action>
| |
|
Ah yes... very good suggestion Burr... we should be able to do that. I guess we'll also need to also support what I already proposed if we want all this ContentBasedRouting stuff to be consistent?
"burrsutter" wrote : A couple of other points: I don't think "cbrClass" makes sense for the value of XPath but I don't have a better suggestion.
Right... well cbrClass already exists and my thinking was that if we introduced another property then we'd have to start raising errors if the user configured both, which seems ugly to me.
"burrsutter" wrote : One thing to keep in mind, XPath and/or Regex routers are the "default" router/wiretaper/filter, Rules-based routers will be considered the advanced options for only when the complexity rises to need that solution.
|
| Our Getting Started experience should start with XPath/Regex & XSLT with Rules-based CBR/Filter and Smooks-based Transformations being for more advanced use cases.
Right... I know I said it already (indirectly perhaps :) ), but I actually think there would be less confusion for the user if we made a clean break from the ContenBasedRouter action config. We could still use the same underlying code. I think there's nothing more confusing for things to look "nearly the same", but for them to not really be the same and to have subtle little differences that need to be explained in parallel.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4256698#4256698
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4256698
17 years
[JBoss ESB Development] - Re: XPath Routing
by burrsutter
For the inline use case, can we do away with the destination-name concept, it seems harder to use and doesn't add significant value.
| <action class="org.jboss.soa.esb.actions.ContentBasedRouter" name="ContentBasedRouter">
| <property name="cbrClass" value="XPath"/>
| <property name="ruleSet">
| <rule target-service="OrderCategory:BlueService" expression="/order/header[@cat='blue']" />
| <rule target-category="OrderCategory" target-service="RedService"" expression="/order/header[@cat='red']" />
| </property>
| </action>
|
A couple of other points: I don't think "cbrClass" makes sense for the value of XPath but I don't have a better suggestion.
I think property named "ruleSet" sounds a little strange for XPath users, since they have no knowledge of rules, just XPath expressions.
One thing to keep in mind, XPath and/or Regex routers are the "default" router/wiretaper/filter, Rules-based routers will be considered the advanced options for only when the complexity rises to need that solution.
Our Getting Started experience should start with XPath/Regex & XSLT with Rules-based CBR/Filter and Smooks-based Transformations being for more advanced use cases.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4256691#4256691
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4256691
17 years