Guided Editor in BRMS / Guvnor Version 5 (Snapshot of 26 June)
by Paul Browne
Folks,
For various reasons I'm trying out the Guided Editor for Business Rules in
the Guvnor Version 5 (Snapshot of 26 June from Hudson, deployed on JBoss App
Server 4.2.2GA).
I've created the Package / Category and uploaded a simple fact model (as
works in BRMS version 4). I create a new business rule using the guided
editor and the screen shows successfully with both 'When' and 'Then'
parts.Assume the next question is due to me missing something, but wanted to
double check:
When I press the green '+' to the right of the screen I am shown the message
/ dialog layer saying '
*Add a condition to the rule... *or* Add an action to the rule.
*Problem is that there doesn't appear to be a way of adding a condition or
action. The only thing I'm seeing in the logs is
* (Contexts.java:flushAndDestroyContexts:335) could not discover
transaction status
*Am I missing something or should I come back to Guvnor later in the
development Cycle?
Thanks
Paul
13 years, 7 months
Can drools continue testing even if one of the conditions fail ?
by DroolUser
Hi,
I'm using drools for testing if the few attributes of my MO are not null.
I construct the rule in the .drl file in following way :
rule "name"
when
condition1
condition2
condition3
condition4
then
consequence
end
I have observed that the drool engine verifies the conditions line by line
(in the sequence they have written). The moment condition fails, control
comes back to the calling method.
I don't want this. I want the control to execute each and every condition
whether true or false and maintain a record of passed/failed conditions.
Something like this :
rule "name"
when
condition1
log the test result --- This statement should get executed
even if condition 1 fails and control should go to condition 2
condition2
log the test result
condition3
log the test result
condition4
log the test result
then
consequence
end
Is this possible in Drools ?
--
View this message in context: http://www.nabble.com/Can-drools-continue-testing-even-if-one-of-the-cond...
Sent from the drools - dev mailing list archive at Nabble.com.
16 years, 6 months
Extended Deadline - Semantic Web Applications and Tools for Life Sciences (SWAT4LS)
by paschke＠mi.fu-berlin.de
Dear Colleagues,
Because of a large number of requests, the submission date for the
International Workshop on Semantic Web Applications and Tools for Life
Sciences (SWAT4LS) has been extended to October 13th.
We hope that you will consider submitting a paper - see submission
details below.
Note: A selection of papers will be published in a special issue of
BMC Bioinformatics supplement devoted to the workshop.
Best regards,
Adrian Paschke (on behalf of all Chairs)
-----------------------------------------------------
Prof. Dr. Adrian Paschke (paschke(a)inf.fu-berlin.de)
AG-CSW (AG Corporate Semantic Web)
Free University Berlin
Germany
International Workshop on
Semantic Web Applications and Tools for Life Sciences (SWAT4LS)
28th November 2008, Edinburgh, UK
http://www.swat4ls.org/
Call for Papers
New submission deadline: 13 October 2008!
A selection of papers will be published in a BMC Bioinformatics
supplement devoted to the workshop
Overview
--------
The workshop is organized in sessions and open discussions. Invited
speakers will present state-of-theart,
provocative lectures on the workshop's main topic, while a number of
submissions will be accepted as
oral presentations and posters on all workshop's topics.
Workshop Description
--------------------
Semantic Web technologies, tools and applications are starting to
emerge in Life Sciences. In recent
years, systems have been introduced and an increasing interest among
researchers is arising. This
workshop will provide a venue to present and discuss benefits and
limits of the adoption of these
technologies and tools in biomedical informatics and computational biology.
It will showcase experiences, information resources, tools development
and applications. It will bring
together researchers, both developers and users, from the various
fields of Biology, Bioinformatics and
Computer Science, to discuss goals, current limits and some real use
cases for Semantic Web
technologies in Life Sciences.
Keynote Speakers
------------------------
+ Semantic web technology in translational cancer research,
Michael Krauthammer, Department of Pathology, Yale University School
of Medicine, USA
+ Using Ontologies to bring Web Services on to the Semantic Web
Mark Wilkinson, Dept. of Medical Genetics, University of British
Columbia, Canada
Workshop Venue and Format
------------------------
The workshop will take place in Edinburgh, Scotland, on 28 November
2008, and is hosted by the e-
Science Institute of the UK's National e-Science Centre (NeSC).
SWAT4LS will be a one-day workshop and will consist of two invited
talks, regular paper and poster
presentations. The workshop will conclude with a panel discussion on
the strength and weaknesses of
the Semantic Web for the Life Sciences.
Deadlines
---------
* Submission deadline (both papers and posters): 13 October 2008 (New
deadline!)
* Notification of acceptance: 20 October 2008
* Camera-ready submission: 3 November 2008
Topics of Interest
------------------
Topics of interest include, but are not limited to:
* Standards, Technologies, Tools for the Semantic Web
o Semantic Web standards (RDF, OWL, ...)
o RDF/OWL, SKOS, .... and their applicability to bioinformatics
o RDF Schemas and Query systems
o Biomedical Ontologies and related tools
o Formal approaches to large biomedical controlled terminologies
and vocabularies
* Systems for a Semantic Web for Bioinformatics
o Bio-ontologies, RDF stores, Semantic Web Services
o RDF repositories and query systems for life sciences
o Semantically aware biomedical Web Services
o Semantic Biological Data Integration Systems
* Existing and perspective applications of the Semantic Web for Bioinformatics
o Semantic browsers, Semantic collaborative research
o Case studies, use cases, and scenarios
o Semantic Web applications in life sciences
Type of contributions and instructions
----------------------
The following possible original contributions are sought:
* Oral communications (regular papers)
* Posters
* Software demos
All contributions must be in English and must be submitted through the
EasyChair review system at:
http://www.easychair.org/conferences/?conf=swat4ls.
Please upload all submissions as PDF files in LNCS format (see
http://www.springer.de/comp/lncs/authors.html ).
To ensure high quality, submitted papers will be carefully
peer-reviewed by at least three members of the
Scientific Committee.
* Submissions for Oral communications should be between 10 and 15 pages.
* Posters submissions should be between 4 and 8 pages.
* Software demo proposals should also be between 4 and 8 pages.
All accepted oral communications and posters will be published with
the CEUR-WS.org Workshop
Proceedings service (see http://ceur-ws.org/).
Furthermore, a selection of papers will be published in a special
issue of the BMC Bioinformatics journal
devoted to the SWAT4LS workshop.
To this end, a special Call will be launched shortly after the
workshop, for extended and revised versions
of contributions submitted to the workshop and accepted either as oral
communication or poster.
For any information, refer to info(a)swat4ls.org.
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
16 years, 7 months
Re: [rules-users] Max packages
by Mark Proctor
Joe White wrote:
>
> Mark, thank you very much for your help, it is greatly appreciated.
>
>
>
> "There are improvements we can make to generated code into a single
> class and use a switch statement to invoke the correct part, but we
> don't have time for that right now, so would need to come from the
> community."
>
>
>
> I would be interested in doing this work if someone can point me in
> the right direction on where to start.
>
look for the *.mvel templates in drools-compiler you'll see how we
generate the code. Then look at all the various java builders, like
JavaConsequenceBuilder and you'll see how we construct it. compiled code
is done in two places. We first generate an invoker class which
implements the interface, like the Consequence interface and then we
genernate the code to be executed which is called via the invoker. It
needs to be two as the needed parameters for the java consequence to
execute differer (different number of vars) so the invokers job is to
match the needed interfaces and adapt/bridge to calling to the actual
consequence/eval/predicate. We currently generate all the
consequence/eval/predicate in a single class per rule, but we have a
class per invoker.
So we now need invoker apis, like Consequence, to take an int so it can
use a switch statement to which allows multiple invocations to be
generated into the same file. An idea solution will take a configuration
on teh granularity that people want - to what we have now right up to
putting everything into a single file for the entire package.
>
> I also would be interested in doing the work to allow drools to
> reference multiple levels of inner classes.
>
This is done and fixed in 4.0.x and trunk - we just haven't released any
binaries wit hteh fix.
>
> Our work would benefit from both pieces of functionality. I'll move
> this to the developer list, but would appreciate if somebody
> knowledgeable could show me where to get started on the code necessary
> to generate to a single class.
>
I've cc'd this into the dev mailing list, so please when you reply do so
to just that mailing list.
>
>
>
> Thanks,
>
> Joe
>
>
>
> *From:* rules-users-bounces(a)lists.jboss.org
> [mailto:rules-users-bounces@lists.jboss.org] *On Behalf Of *Mark Proctor
> *Sent:* Wednesday, August 13, 2008 2:53 AM
> *To:* Rules Users List
> *Subject:* Re: [rules-users] Max packages
>
>
>
> Joe White wrote:
>
> Can someone help me understand the relationship between the number of
> Packages in a single RuleBase and PermGen memory consumption? I have a
> test that generates 200 rules and then adds those rules as different
> packages to a single rule base. PermGen consumption grows near
> linearly with the addition of Packages to the rule base and on a
> default PermGen setting the JVM runs out of PermGen after about 120
> packages.
>
> It's not related to Packages, it's related to the number of rules and
> whether those rules have compiled java parts - like the consequence,
> eval etc - each one adds an additional class.
>
>
>
> Is every new Package and RuleBase backed by a set of generated
> Classes? Is there a way to get around the amount of class generation
> that is taking place?
>
> The test has been run against Drools 5.
>
> You can use MVEL, which has no class generation. There are
> improvements we can make to generated code into a single class and use
> a switch statement to invoke the correct part, but we don't have time
> for that right now, so would need to come from the community.
>
>
>
> Thank you for your help,
>
> Joe
>
>
> ------------------------------------------------------------------------
>
>
>
>
> _______________________________________________
> rules-users mailing list
> rules-users(a)lists.jboss.org <mailto:rules-users@lists.jboss.org>
> https://lists.jboss.org/mailman/listinfo/rules-users
>
>
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> rules-users mailing list
> rules-users(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/rules-users
>
17 years
file per asset type
by Mark Proctor
What do people think of insisting on a file per type. So functions go in
one file, rules in another and declare models in another. They all end
up in the same package object, but we enforce a separation at both the
file and api level.
kbuilder.addRulesFromURL( url );
kbuilder.addModelFromURL( url );
kbuilder.addFunctionsFromURL( url );
kbuilder.addProcessFromURL( url );
Really more thinking about orthogonality of api and design here. We have
the following situation
kbuilder.addPackageFromXML()
kbuilder.addProcessFromXML()
Processes live in a package, so to a package there is no difference from
a process to a rule - yet we are losing that orthogonality in the api to
handle the special case.
What do people think, I'm just trying to find a better way to get some
language orthogonality. I don't think we are likely to do this, but just
throwing it out for discussion.
I think ideally we would like kbuilder.addResource( url/reader ), but
not sure if we can easily determine each file type, we can't do it by
file extensions as readers have none.
Mark
17 years, 1 month
M2 Guvnor Tomcat Deployment Issues and Resolutions
by David Sinclair
Just a heads up for everyone out there. I needed to make the following
changes to guvnor's POM in order to get the webapp to work properly on
Tomcat. I would imagine some of these issues would appear on JBoss also but
have not tried.
1. Changed seam from 2.1.0.BETA1 to 2.1.0-SNAPSHOT to prevent classloader
problem
POM Changes
<dependency>
<groupId>org.jboss.seam</groupId>
<artifactId>jboss-seam-remoting</artifactId>
<version>2.1.0-SNAPSHOT</version>
</dependency>
<dependency>
<groupId>org.jboss.seam</groupId>
<artifactId>jboss-seam</artifactId>
<version>2.1.0-SNAPSHOT</version>
</dependency>
EXCEPTION without change
SEVERE: Exception sending context initialized event to listener instance of
class org.jboss.seam.servlet.SeamListener
java.lang.IllegalStateException: Cannot load
WEB-INF/classes/net/sf/webdav/exceptions/AccessDeniedException.class from
WebappClassLoader
delegate: false
repositories:
/WEB-INF/classes/
----------> Parent Classloader:
org.apache.catalina.loader.StandardClassLoader@c4fe76
(using getResourceAsStream() returned null)
at
org.jboss.seam.deployment.AbstractDeploymentHandler.getClassFile(AbstractDeploymentHandler.java:41)
at
org.jboss.seam.deployment.ComponentDeploymentHandler.handle(ComponentDeploymentHandler.java:57)
at
org.jboss.seam.deployment.DeploymentStrategy.handle(DeploymentStrategy.java:177)
at
org.jboss.seam.deployment.AbstractScanner.handleItem(AbstractScanner.java:30)
at
org.jboss.seam.deployment.URLScanner.handleDirectory(URLScanner.java:141)
at
org.jboss.seam.deployment.URLScanner.handleDirectory(URLScanner.java:137)
at
org.jboss.seam.deployment.URLScanner.handleDirectory(URLScanner.java:137)
at
org.jboss.seam.deployment.URLScanner.handleDirectory(URLScanner.java:137)
at
org.jboss.seam.deployment.URLScanner.handleDirectory(URLScanner.java:137)
at
org.jboss.seam.deployment.URLScanner.handleDirectory(URLScanner.java:137)
at
org.jboss.seam.deployment.URLScanner.handleDirectory(URLScanner.java:137)
at
org.jboss.seam.deployment.URLScanner.scanDirectories(URLScanner.java:40)
at
org.jboss.seam.deployment.StandardDeploymentStrategy.scan(StandardDeploymentStrategy.java:107)
at
org.jboss.seam.init.Initialization.create(Initialization.java:113)
at
org.jboss.seam.servlet.SeamListener.contextInitialized(SeamListener.java:34)
at
org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3843)
at
org.apache.catalina.core.StandardContext.start(StandardContext.java:4350)
at
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791)
at
org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771)
at
org.apache.catalina.core.StandardHost.addChild(StandardHost.java:525)
at
org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:829)
at
org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:718)
at
org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:490)
at
org.apache.catalina.startup.HostConfig.start(HostConfig.java:1147)
at
org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:311)
at
org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117)
at
org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053)
at
org.apache.catalina.core.StandardHost.start(StandardHost.java:719)
at
org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045)
at
org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443)
at
org.apache.catalina.core.StandardService.start(StandardService.java:516)
at
org.apache.catalina.core.StandardServer.start(StandardServer.java:710)
at org.apache.catalina.startup.Catalina.start(Catalina.java:578)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:288)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413)
2. Added javax.persistence to prevent ClassNotFoundException
POM Changes
<dependency>
<groupId>javax.persistence</groupId>
<artifactId>persistence-api</artifactId>
<version>1.0</version>
</dependency>
EXCEPTION without change
SEVERE: Exception sending context initialized event to listener instance of
class org.jboss.seam.servlet.SeamListener
java.lang.RuntimeException: Could not create Component:
org.jboss.seam.core.init
at
org.jboss.seam.init.Initialization.addComponent(Initialization.java:1068)
at org.jboss.seam.init.Initialization.init(Initialization.java:614)
at
org.jboss.seam.servlet.SeamListener.contextInitialized(SeamListener.java:34)
at
org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3843)
at
org.apache.catalina.core.StandardContext.start(StandardContext.java:4350)
at
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791)
at
org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771)
at
org.apache.catalina.core.StandardHost.addChild(StandardHost.java:525)
at
org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:829)
at
org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:718)
at
org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:490)
at
org.apache.catalina.startup.HostConfig.start(HostConfig.java:1147)
at
org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:311)
at
org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117)
at
org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053)
at
org.apache.catalina.core.StandardHost.start(StandardHost.java:719)
at
org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045)
at
org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443)
at
org.apache.catalina.core.StandardService.start(StandardService.java:516)
at
org.apache.catalina.core.StandardServer.start(StandardServer.java:710)
at org.apache.catalina.startup.Catalina.start(Catalina.java:578)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:288)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413)
Caused by: java.lang.NoClassDefFoundError: javax/persistence/Entity
at org.jboss.seam.Seam.getComponentType(Seam.java:109)
at org.jboss.seam.Component.<init>(Component.java:210)
at org.jboss.seam.Component.<init>(Component.java:199)
at
org.jboss.seam.init.Initialization.addComponent(Initialization.java:1052)
... 26 more
Caused by: java.lang.ClassNotFoundException: javax.persistence.Entity
at
org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1360)
at
org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1206)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
... 30 more
3. Added hibernate-validator to prevent ClassNotFoundException
POM Changes
<dependency>
<groupId>org.hibernate</groupId>
<artifactId>hibernate-validator</artifactId>
<version>3.0.0.GA</version>
</dependency>
EXCEPTION without change
SEVERE: Exception sending context initialized event to listener instance of
class org.jboss.seam.servlet.SeamListener
java.lang.RuntimeException: Could not create Component:
org.jboss.seam.international.statusMessages
at
org.jboss.seam.init.Initialization.addComponent(Initialization.java:1068)
at
org.jboss.seam.init.Initialization.installComponents(Initialization.java:984)
at org.jboss.seam.init.Initialization.init(Initialization.java:646)
at
org.jboss.seam.servlet.SeamListener.contextInitialized(SeamListener.java:34)
at
org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3843)
at
org.apache.catalina.core.StandardContext.start(StandardContext.java:4350)
at
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791)
at
org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771)
at
org.apache.catalina.core.StandardHost.addChild(StandardHost.java:525)
at
org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:829)
at
org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:718)
at
org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:490)
at
org.apache.catalina.startup.HostConfig.start(HostConfig.java:1147)
at
org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:311)
at
org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117)
at
org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053)
at
org.apache.catalina.core.StandardHost.start(StandardHost.java:719)
at
org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045)
at
org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443)
at
org.apache.catalina.core.StandardService.start(StandardService.java:516)
at
org.apache.catalina.core.StandardServer.start(StandardServer.java:710)
at org.apache.catalina.startup.Catalina.start(Catalina.java:578)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:288)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413)
Caused by: java.lang.NoClassDefFoundError:
[Lorg/hibernate/validator/InvalidValue;
at java.lang.Class.getDeclaredMethods0(Native Method)
at java.lang.Class.privateGetDeclaredMethods(Class.java:2427)
at java.lang.Class.privateGetPublicMethods(Class.java:2547)
at java.lang.Class.privateGetPublicMethods(Class.java:2563)
at java.lang.Class.getMethods(Class.java:1410)
at org.jboss.seam.Component.hasAnnotation(Component.java:1078)
at org.jboss.seam.Component.<init>(Component.java:212)
at org.jboss.seam.Component.<init>(Component.java:199)
at
org.jboss.seam.init.Initialization.addComponent(Initialization.java:1052)
... 27 more
Caused by: java.lang.ClassNotFoundException:
org.hibernate.validator.InvalidValue
at
org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1360)
at
org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1206)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
... 36 more
4. Seam's version of the Java Expression Language was clashing with Tomcat's
POM Changes
- exclude from seam
<dependency>
<groupId>org.jboss.seam</groupId>
<artifactId>jboss-seam</artifactId>
<version>2.1.0-SNAPSHOT</version>
<exclusions>
<exclusion>
<groupId>javax.el</groupId>
<artifactId>el-api</artifactId>
</exclusion>
</exclusions>
</dependency>
- comment out from POM
<!--<dependency>-->
<!--<groupId>javax.el</groupId>-->
<!--<artifactId>el-api</artifactId>-->
<!--<version>1.2</version>-->
<!--<scope>runtime</scope>-->
<!--</dependency>-->
Exception without change
java.lang.LinkageError: loader constraint violation: when resolving
interface method
"javax.servlet.jsp.JspApplicationContext.getExpressionFactory()Lj
avax/el/ExpressionFactory;" the class loader (instance of
org/apache/jasper/servlet/JasperLoader) of the current class,
org/apache/jsp/index_jsp, and
the class loader (instance of
org/apache/catalina/loader/StandardClassLoader) for resolved class,
javax/servlet/jsp/JspApplicationContext, have differ
ent Class objects for the type javax/el/ExpressionFactory used in the
signature
at org.apache.jsp.index_jsp._jspInit(index_jsp.java:22)
at org.apache.jasper.runtime.HttpJspBase.init(HttpJspBase.java:52)
at
org.apache.jasper.servlet.JspServletWrapper.getServlet(JspServletWrapper.java:159)
at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:329)
at
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:337)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:266)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.jboss.seam.web.ContextFilter$1.process(ContextFilter.java:42)
at
org.jboss.seam.servlet.ContextualHttpServletRequest.run(ContextualHttpServletRequest.java:53)
at org.jboss.seam.web.ContextFilter.doFilter(ContextFilter.java:37)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286)
at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
at
org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
at java.lang.Thread.run(Thread.java:619)
let me know if we should use different versions then the ones I have listed.
thanks
dave sinclair
17 years, 1 month
BRMS with DB2.....
by arpan.makwana
From: arpan.makwana [mailto:arpan.makwana@indralok.com]
Sent: Tuesday, September 30, 2008 6:04 PM
To: 'rules-dev(a)lists.jboss.org'
Subject: BRMS with DB2.....
Hi ,
I am a fresher in this field. We have a requirement to tune BRMS with
db2. I read all the articles where in they have stated the use of MYSQL with
BRMS.
I am able to create the default tables in the DB2. I made certain changes in
the repository.xml and it works out fine. I also want to make BRMS
absolutely independent of Derby database..
I want to know how to change the location of the data stored from local file
system to the database. I read the previous postings but it didn't really
help me.
Please suggest me something so that I can store the data from BRMS into
database directly.
17 years, 1 month
BRMS with DB2.....
by arpan.makwana
Hi ,
I am a fresher in this field. We have a requirement to tune BRMS with
db2. I read all the articles where in they have stated the use of MYSQL with
BRMS.
I am able to create the default tables in the DB2. I made certain changes in
the repository.xml and it works out fine. I also want to make BRMS
absolutely independent of Derby database..
I want to know how to change the location of the data stored from local file
system to the database. I read the previous postings but it didn't really
help me.
Please suggest me something so that I can store the data from BRMS into
database directly.
cid:1.1868414067@web39105.mail.mud.yahoo.com
Regards,
ARPAN MAKWANA
Associate Software Developer
Indralok Technology Pvt. Ltd.
email: arpan.makwana(a)indralok.com
Ph: +91-9727990044
17 years, 1 month
Enhancing BRDRLPersistence
by Nimesh Muley
Hi,
This is in continuation of the mail thread in user list http://lists.jboss.org/pipermail/rules-users/2008-September/006619.html
Currently we are not in a position to enhance the BRDRLPersistence to add functionality that is already supported by DRL but available in the RuleModel or in the translation.
I could think of two approaches for people to write their own implementations by extending existing ones
1. Have the LHS or RHS PatternVisitor classes pluggable instead of creating the instances inside the marshalXXX methods.
2. Accept additional implementations of LHS and RHS PatternVisitor. Hence in the mashalXXX there would an additional for loop to run for each of the PatternVisitors apart from the existing for loop of each conditions or actions.
If you let me know which would be preferred option I can implement the same and submit a patch.
Going down the line when people write new implementations it would be easier for them to submit the patch and also make it work in their existing environment till the time the patch is not released.
Even the existing classes LHS or RHS PatternVisitor need to be modified so that extending from them is easier. I will write about this in a separate mail if suggestions in this mail are acceptable.
Thanks.
Regards,
- Nimesh
MASTEK LTD.
Mastek is in NASSCOM's 'India Top 20' Software Service Exporters List.
In the US, we're called MAJESCOMASTEK
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Opinions expressed in this e-mail are those of the individual and not that of Mastek Limited, unless specifically indicated to that effect. Mastek Limited does not accept any responsibility or liability for it. This e-mail and attachments (if any) transmitted with it are confidential and/or privileged and solely for the use of the intended person or entity to which it is addressed. Any review, re-transmission, dissemination or other use of or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. This e-mail and its attachments have been scanned for the presence of computer viruses. It is the responsibility of the recipient to run the virus check on e-mails and attachments before opening them. If you have received this e-mail in error, kindly delete this e-mail from desktop and server.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
17 years, 1 month
drools-api
by Mark Proctor
We've created a branch to do drools-api, so that we don't break trunk
while we are moving around. As mentioned before while we are providing a
new api, we will keep the core/compiler apis as is so not to break
people's code, while they transition to the new api.
http://anonsvn.labs.jboss.com/labs/jbossrules/branches/drools-api-refacto...
http://fisheye.jboss.org/browse/JBossRules/branches/drools-api-refactor-2...
To help you get an idea of what the api now looks like, here is a brief
code snippet from a typical session creation:
KnowledgeBuilder kbuilder =
KnowledgeBuilderFactory.newKnowledgeBuilder();
kbuilder.addPackageFromDrl( reader );
Collection<KnowledgePackage> kpkgs =
kbuilder.getKnowledgePackages();
KnowledgeBase kbase = KnowledgeBaseFactory.newKnowledgeBase();
kbase.addKnowledgePackages( kpkgs );
StatefulKnowledgeSession ksession =
kbase.newStatefulKnowledgeSession();
I'm going for the k prefix to indicate a knowlede variable.
builder/pkgBuilder = kbuilder
pkgs -> kpkgs
ruleBase -> kbase
session -> ksession.
Another decision we made is that we always return a generic collection
for things now, instead of arrays or lists. In general a Collection is
easier for the end user to work with, and it has toArray methods on it
anyway. We didn't use list, as list implies ordered semantics. So
whether it's kbuilder.KnowledgePackages() or kpackage.getRules() or
kpackage.getProcesses() it's always returning a Collection<Class>. I'm
open to other ideas, if people think this can be improved. I did think
about returning just Iterable, to make it even more generic, but figured
that people would want the size./isEmpty methods, we'll have to make the
other mutating methods throw an exception if someone tries to use them.
Don't forget everything is factory/provider based now, so I'd love
someone to start doing a spring set of providers in parallel so we can
make sure I've got it right. Anyone game?
Please do monitor and give feedback, I need to get this wrapped up this
week, so get the feedback to me asap. I'll post an update in a few days,
once the event and process stuff is migrated to the new knowledge api.
As always the Drools team can be found on IRC for real time chat:
http://www.jboss.org/drools/irc.html
Mark
17 years, 1 month
