Hi Guillaume,
The reason of the use of jndi in the code is that the user that write
the rule want to choose dinamically the
datasource from the datasource list defined in smx he want to use and
not to bound to a particular datasource with dependency injection.
For example we want to check against to different datasource, if i put
the datasource ref in a spring configuration file
i'm bound to this.
Andrea Zoppello
Guillaume Nodet (JIRA) ha scritto:
[
https://issues.apache.org/activemq/browse/SM-924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet resolved SM-924.
--------------------------------
Resolution: Fixed
URL: http://svn.apache.org/viewvc?view=rev&rev=526251
I haven't included your DbHelper in this patch because i have some concerns
with it.
As far as I understand, it forces the use of JNDI to retrieve the database, and
I'd rather
use a plain DataSource and configure it using spring (and JNDI eventually) ...
Namespace support in servicemix-drools
--------------------------------------
Key: SM-924
URL: https://issues.apache.org/activemq/browse/SM-924
Project: ServiceMix
Issue Type: Improvement
Components: servicemix-drools
Affects Versions: 3.1
Environment: ServiceMix 3.1
Reporter: Andrea Zoppello
Assigned To: Guillaume Nodet
Fix For: 3.2
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
