I believe currently you can only apply rules on POJO, you could use JAXB to convert from XML to POJO but this doesn’t work very well on deeply nested or complex data structures if you wish to perform updates on the data.

 

XML support is something I’ve been pondering over as to how easy it would be to do. If I get some free time I might put together a prototype to see how well it would work as currently the application I’m working on does the JAXB route and it isn’t great, particular with respects to updating different fields and re-execution of rules.

 

Thomas

 

From: rules-users-bounces@lists.jboss.org [mailto:rules-users-bounces@lists.jboss.org] On Behalf Of Nilima R
Sent: 06 January 2010 09:42
To: Rules Users List
Subject: Re: [rules-users] Drools Guvnor installation on weblogic

 


Hi All,


Can you please let me know if I can apply rules on xml data using Drools or we can just apply rules on POJO.


Regards,

Nilima Rajendra Raichandani
Sub Focus Area Lead - BPM/BAM/BRE
TEG - Open Source Platform
Tata Consultancy Services
Ph:- +91 22 6778 2027
Cell:- 9322108518
Mailto: nilima.r@tcs.com
Website: http://www.tcs.com
____________________________________________
Experience certainty.        IT Services
                       Business Solutions
                       Outsourcing
____________________________________________

From:

Vijay K Pandey <VPandey@mdes.ms.gov>

To:

Rules Users List <rules-users@lists.jboss.org>

Cc:

Nilima R <nilima.r@tcs.com>

Date:

01/05/2010 08:59 PM

Subject:

RE: [rules-users] Drools Guvnor  installation on weblogic

 




The datasource defined in the persistence unit (jta-data-source or non-jta-data-source) of the persistence.xml maps to the JNDI name that must be configured beforehand. In your case you need to have the datasource configured against the jdbc/testDS1 jndi name.
 
Regards
Vijay

 


From: rules-users-bounces@lists.jboss.org [mailto:rules-users-bounces@lists.jboss.org] On Behalf Of Nilima R
Sent: Tuesday, January 05, 2010 2:41 AM
To: rules-users@lists.jboss.org
Subject: [rules-users] Drools Guvnor installation on weblogic
 

Hi All,

I am trying to install Drools Guvnor on weblogic 10 .I have added the Guvnor WAR file and dependent jars from Drools binaries download.
However  I am getting error for datasource configuration. Do we need to configure any datasource?  
Please find error logs below



<Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1262262938099' for task '1'. Error is: 'weblogic.application.ModuleException: '
weblogic.application.ModuleException:
       at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:317)
       at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176)
       at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
       at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:360)
       at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
       Truncated. see log file for complete stacktrace
weblogic.deployment.EnvironmentException: Error processing persitence unit org.drools.persistence.jpa of module drools_guvnor.war: Error looking up a DataSource for PersistenceUnit org.drools.persistence.jpa: javax.naming.NameNotFoundException: While trying to lookup 'jdbc.testDS1' didn't find subcontext 'jdbc'. Resolved ''; remaining name 'jdbc/testDS1'
       at weblogic.deployment.PersistenceUnitInfoImpl.lookUpDataSources(PersistenceUnitInfoImpl.java:126)
       at weblogic.deployment.PersistenceUnitInfoImpl.<init>(PersistenceUnitInfoImpl.java:105)
       at weblogic.deployment.AbstractPersistenceUnitRegistry.storeDescriptors(AbstractPersistenceUnitRegistry.java:316)
       at weblogic.deployment.AbstractPersistenceUnitRegistry.loadPersistenceDescriptors(AbstractPersistenceUnitRegistry.java:96)
       at weblogic.deployment.ModulePersistenceUnitRegistry.<init>(ModulePersistenceUnitRegistry.java:53)
       Truncated. see log file for complete stacktrace
>
<Dec 31, 2009 6:05:52 PM IST> <Warning> <Deployer> <BEA-149004> <Failures were detected while initiating distribute task for application 'drools_guvnor'.>
<Dec 31, 2009 6:05:52 PM IST> <Warning> <Deployer> <BEA-149078> <Stack trace for message 149004
weblogic.application.ModuleException:
       at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:317)
       at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176)
       at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
       at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:360)
       at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
       Truncated. see log file for complete stacktrace
weblogic.deployment.EnvironmentException: Error processing persitence unit org.drools.persistence.jpa of module drools_guvnor.war: Error looking up a DataSource for PersistenceUnit org.drools.persistence.jpa: javax.naming.NameNotFoundException: While trying to lookup 'jdbc.testDS1' didn't find subco
ntext 'jdbc'. Resolved ''; remaining name 'jdbc/testDS1'
       at weblogic.deployment.PersistenceUnitInfoImpl.lookUpDataSources(PersistenceUnitInfoImpl.java:126)
       at weblogic.deployment.PersistenceUnitInfoImpl.<init>(PersistenceUnitInfoImpl.java:105)
       at weblogic.deployment.AbstractPersistenceUnitRegistry.storeDescriptors(AbstractPersistenceUnitRegistry.java:316)
       at weblogic.deployment.AbstractPersistenceUnitRegistry.loadPersistenceDescriptors(AbstractPersistenceUnitRegistry.java:96)
       at weblogic.deployment.ModulePersistenceUnitRegistry.<init>(ModulePersistenceUnitRegistry.java:53)
       Truncated. see log file for complete stacktrace
>
<Dec 31, 2009 6:05:52 PM IST> <Error> <Console> <BEA-240003> <Console encountered the following error weblogic.application.ModuleException:
       at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:317)
       at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176)
       at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
       at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:360)
       at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
       at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:56)
       at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:46)
       at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615)
       at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
       at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
       at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:147)
       at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:61)
       at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:189)
       at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:87)
       at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
       at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:719)
       at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1186)
       at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:248)
       at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:157)
       at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157)
       at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12)
       at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45)
       at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:464)
       at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
       at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
Caused by: weblogic.deployment.EnvironmentException: Error processing persitence unit org.drools.persistence.jpa of module drools_guvnor.war: Error looking up a DataSource for PersistenceUnit org.drools.persistence.jpa: javax.naming.NameNotFoundException: While trying to lookup 'jdbc.testDS1' didn't
find subcontext 'jdbc'. Resolved ''; remaining name 'jdbc/testDS1'
       at weblogic.deployment.PersistenceUnitInfoImpl.lookUpDataSources(PersistenceUnitInfoImpl.java:126)
       at weblogic.deployment.PersistenceUnitInfoImpl.<init>(PersistenceUnitInfoImpl.java:105)
       at weblogic.deployment.AbstractPersistenceUnitRegistry.storeDescriptors(AbstractPersistenceUnitRegistry.java:316)
       at weblogic.deployment.AbstractPersistenceUnitRegistry.loadPersistenceDescriptors(AbstractPersistenceUnitRegistry.java:96)
       at weblogic.deployment.ModulePersistenceUnitRegistry.<init>(ModulePersistenceUnitRegistry.java:53)
       at weblogic.servlet.internal.WebAppModule.initPURegistry(WebAppModule.java:1176)
       at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:307)
>
 


Regards,
Nilima Rajendra Raichandani
Sub Focus Area Lead - BPM/BAM/BRE
TEG - Open Source Platform
Tata Consultancy Services
Ph:- +91 22 6778 2027
Cell:- 9322108518
Mailto: nilima.r@tcs.com
Website: http://www.tcs.com
____________________________________________
Experience certainty.        IT Services
                      Business Solutions
                      Outsourcing
____________________________________________
=====-----=====-----=====
Notice: The information contained in this e-mail
message and/or attachments to it may contain
confidential or privileged information. If you are
not the intended recipient, any dissemination, use,
review, distribution, printing or copying of the
information contained in this e-mail message
and/or attachments to it are strictly prohibited. If
you have received this communication in error,
please notify us by reply e-mail or telephone and
immediately and permanently delete the message
and any attachments. Thank you
 
  

=====-----=====-----=====
Notice: The information contained in this e-mail
message and/or attachments to it may contain 
confidential or privileged information. If you are 
not the intended recipient, any dissemination, use, 
review, distribution, printing or copying of the 
information contained in this e-mail message 
and/or attachments to it are strictly prohibited. If 
you have received this communication in error, 
please notify us by reply e-mail or telephone and 
immediately and permanently delete the message 
and any attachments. Thank you
 
 


**************************************************************************************
This message is confidential and intended only for the addressee. If you have received this message in error, please immediately notify the postmaster@nds.com and delete it from your system as well as any copies. The content of e-mails as well as traffic data may be monitored by NDS for employment and security purposes. To protect the environment please do not print this e-mail unless necessary.

NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, United Kingdom. A company registered in England and Wales. Registered no. 3080780. VAT no. GB 603 8808 40-00
**************************************************************************************

This message is confidential and intended only for the addressee. If you have received this message in error, please immediately notify the postmaster@nds.com and delete it from your system as well as any copies. The content of e-mails as well as traffic data may be monitored by NDS for employment and security purposes.
To protect the environment please do not print this e-mail unless necessary.

An NDS Group Limited company. www.nds.com