November 2010 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-1908) updated Drools docs content from SOA 4.2.CP03 Rules Guide

by Darrin Mison (JIRA)

updated Drools docs content from SOA 4.2.CP03 Rules Guide --------------------------------------------------------- Key: JBRULES-1908 URL: https://jira.jboss.org/jira/browse/JBRULES-1908 Project: JBoss Drools Issue Type: Task Security Level: Public (Everyone can see) Components: drools-docs-expert Reporter: Darrin Mison Assignee: Mark Proctor I revised the language of the "Insertion" section while fixing a couple of reported grammatical errors for the 4.2.CP03 SOA Rules Guide. The original language is the same in: http://anonsvn.jboss.org/repos/labs/labs/jbossrules/soa_tags/4.3.0.FP01_B... , so these changes would also apply to the most recent docs. Updated content below, the section ids are different but you get the idea ;-) <section id="sect-JBoss_Rules_Reference_Manual-WorkingMemory_and_StatefulStateless_Sessions-Insertion"> <title>Insertion</title> <para> <firstterm>Insertion</firstterm> is the act of telling the WorkingMemory about the facts. </para> <important> <para> In many Expert Systems the term used for this concept is <firstterm>assert</firstterm> or <firstterm>assertion</firstterm>. However as the keyword <methodname>assert</methodname> is already used in many languages, Drools uses the keyword & term <methodname>insert</methodname>. You will often encounter these terms used interchangably in discussion of Rules Engines. </para> </important> <para> When inserted, the rule is examined for matches against the rules. The work of determining what rules to fire is done during insertion, but no rules are executed at this time. The rules are executed when <methodname>fireAllRules()</methodname> is called, and it should only be called after you have inserted all your facts. </para> <para> It is a common misconception that rule matching occurs when <methodname>fireAllRules()</methodname> is called. </para> <para> When an Object is inserted it returns a FactHandle. This FactHandle is the token used to represent your inserted Object inside the WorkingMemory, it is also how you will interact with the Working Memory when you wish to retract or modify an object. </para> <programlisting language="java">Cheese stilton = new Cheese("stilton"); FactHandle stiltonHandle = session.insert( stilton );</programlisting> <para> As mentioned in <xref linkend="sect-JBoss_Rules_Reference_Manual-The_Drools_Rule_Engine-RuleBase" /> a Working Memory can operate in two assertions modes: <firstterm>equality</firstterm> and <firstterm>identity</firstterm>. Identity is the default mode. The assertion mode determines how the Working Memory stores the facts and how it compares the newly inserted fact to previously inserted ones. If the Working Memory determines the fact to "be the same" as an already inserted one it will ignore the new fact and return the FactHandle for the previously inserted one. </para> <variablelist> <varlistentry> <term>Identity</term> <listitem> <para> Identity Mode uses an <classname>IdentityHashMap</classname>to store all asserted Objects. New facts being inserted are compared to existing facts "by reference". A new FactHandle will be returned if the object being inserted is not a reference to an object that has been inserted previously. </para> </listitem> </varlistentry> <varlistentry> <term>Equality</term> <listitem> <para> Equality Mode uses a <classname>HashMap</classname> to store all asserted Objects. New facts being inserted are compared to existing facts "by value". A new FactHandle will be returned if the content of the object is not identical to that of a previously inserted object. </para> </listitem> </varlistentry> </variablelist> </section> -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

5
7
0 / 0

[JBoss JIRA] Created: (JBRULES-2112) Cannot build Drools IDE w/ OpenJDK 6 (vm crashes)

by Nick Boldt (JIRA)

Cannot build Drools IDE w/ OpenJDK 6 (vm crashes) ------------------------------------------------- Key: JBRULES-2112 URL: https://jira.jboss.org/jira/browse/JBRULES-2112 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Nick Boldt Assignee: Mark Proctor Drools 5.0.x can compile with OpenJDK6; Drools 5.1 cannot. See attached logs. This prevents the JBoss Tools build from being able to run locally on Fedora w/ the out-of-box JVM (Open JDK 6). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 12 months

6
9
0 / 0

[JBoss JIRA] Created: (JBAS-7427) AS won't boot with sun jmx enabled

by Jonathan Halliday (JIRA)

AS won't boot with sun jmx enabled ---------------------------------- Key: JBAS-7427 URL: https://jira.jboss.org/jira/browse/JBAS-7427 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Logging Environment: sun jdk6, fedora, AS trunk r96005 Reporter: Jonathan Halliday Assignee: David Lloyd Fix For: JBossAS-6.0.0.Alpha1 [jhalli jboss-6.0.0-SNAPSHOT]$ export JAVA_OPTS="-Dcom.sun.management.jmxremote.port=12345 -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false" [jhalli jboss-6.0.0-SNAPSHOT]$ bin/run.sh ========================================================================= JBoss Bootstrap Environment JBOSS_HOME: /home/jhalli/IdeaProjects/jboss/jbossas_trunk/build/output/jboss-6.0.0-SNAPSHOT JAVA: /usr/local/jdk1.6.0_16/bin/java JAVA_OPTS: -Dprogram.name=run.sh -server -Dcom.sun.management.jmxremote.port=12345 -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false -Djava.net.preferIPv4Stack=true CLASSPATH: /home/jhalli/IdeaProjects/jboss/jbossas_trunk/build/output/jboss-6.0.0-SNAPSHOT/bin/run.jar:/usr/local/jdk1.6.0_16/lib/tools.jar ========================================================================= Failed to initalize plugin: org.jboss.logging.logmanager.LoggerPluginImpl@214a55f2, cause: java.lang.IllegalStateException: The LogManager was not properly installed (you must set the "java.util.logging.manager" system property to "org.jboss.logmanager.LogManager") ... Failed to initalize plugin: org.jboss.aop.util.logging.SystemOutLoggerPlugin@5c1ae90c, cause: java.lang.AbstractMethodError -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 12 months

3
11
0 / 0

[JBoss JIRA] Created: (JBCL-84) Extend the ClassLoadingMetaData filtered package semantics

by Adrian Brock (JIRA)

Extend the ClassLoadingMetaData filtered package semantics ---------------------------------------------------------- Key: JBCL-84 URL: https://jira.jboss.org/jira/browse/JBCL-84 Project: JBoss ClassLoader Issue Type: Feature Request Components: MetaData Reporter: Adrian Brock Currently the ClassLoadingMetaData has some includedPackages and excludedPackages metadata. This is just a comma seperated list of explicit package names. This metadata should be extended to make it more flexible. e.g. using globing <classloader> <excluded type="glob">com.foo.*</included> or explicitly naming the filter <classloader> <excluded class="com.foo.MyClassFilter>...</excluded> -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 12 months

2
3
0 / 0

[JBoss JIRA] Created: (JBBUILD-663) Some artifacts, like org.hibernate:hibernate-entitymanager:3.5.6-Final are missing in Nexus search

by BTO Sabre (JIRA)

Some artifacts, like org.hibernate:hibernate-entitymanager:3.5.6-Final are missing in Nexus search -------------------------------------------------------------------------------------------------- Key: JBBUILD-663 URL: https://jira.jboss.org/browse/JBBUILD-663 Project: JBoss Build System Issue Type: Bug Components: Sonatype Reporter: BTO Sabre Assignee: Paul Gier Priority: Critical Some artifacts are in repo but not show up in Nexus. I guess this is index issue. For example below artifact is in repo https://repository.jboss.org/nexus/content/groups/public-jboss/org/hibern... but not in Nexus https://repository.jboss.org/nexus/index.html#nexus-search;gav~org.hibern... This bug is critical because we are unable to download this artifact using jboss-public repository proxied in our Nexus. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 12 months

2
2
0 / 0

[JBoss JIRA] Created: (JBBUILD-660) extension of archetype jar gets changes from .jar to .maven-archetype when published to Nexus releases repo via mvn deploy

by Ian Springer (JIRA)

extension of archetype jar gets changes from .jar to .maven-archetype when published to Nexus releases repo via mvn deploy --------------------------------------------------------------------------------------------------------------------------- Key: JBBUILD-660 URL: https://jira.jboss.org/browse/JBBUILD-660 Project: JBoss Build System Issue Type: Bug Components: Sonatype Affects Versions: Maven Repository Nexus Rollout Reporter: Ian Springer Assignee: Paul Gier Priority: Critical I published the following artifact using 'mvn deploy' from a project with type maven-archetype: https://repository.jboss.org/nexus/content/repositories/releases/org/rhq/... Notice the jarfile's extension got changed from .jar to .maven-archetype. I'm not sure if it was the maven deploy plugin or Nexus that did this. but I suspect it was Nexus. It needs to have the extension .jar, because the archetype:generate goal assumes all archetype artifacts will have that extension. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 12 months

2
5
0 / 0

[JBoss JIRA] Created: (JBBUILD-629) Include the release comments from staged repo, in the audit.json file

by jaikiran pai (JIRA)

Include the release comments from staged repo, in the audit.json file --------------------------------------------------------------------- Key: JBBUILD-629 URL: https://jira.jboss.org/browse/JBBUILD-629 Project: JBoss Build System Issue Type: Feature Request Reporter: jaikiran pai Assignee: John Casey Right now the *.audit.json files (ex: https://repository.jboss.org/nexus/content/groups/public/org/jboss/metada...) do not include the comments that were added during the release, in the staged repo. It will be useful to have this info available in the audit file. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 12 months

3
4
0 / 0

[JBoss JIRA] Created: (JBBUILD-608) Research repository file upload size limit

by Paul Gier (JIRA)

Research repository file upload size limit ------------------------------------------ Key: JBBUILD-608 URL: https://jira.jboss.org/jira/browse/JBBUILD-608 Project: JBoss Build System Issue Type: Task Reporter: Paul Gier Assignee: Paul Gier Fix For: Repository Support 2010 It was reported during testing that the deployment fail on files greater than ~50MB. This limit is probably set in the web server configuration. The limit should be set to at least 100MB and documented in the wiki. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 12 months

1
3
0 / 0

[JBoss JIRA] Created: (JBRULES-1135) Move generation should be described in a drl

by Geoffrey De Smet (JIRA)

Move generation should be described in a drl -------------------------------------------- Key: JBRULES-1135 URL: http://jira.jboss.com/jira/browse/JBRULES-1135 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Solver Affects Versions: 4.0.0.GA Reporter: Geoffrey De Smet Assigned To: Geoffrey De Smet Fix For: FUTURE instead of MoveFactory POJO -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 12 months

1
4
0 / 0

[JBoss JIRA] Created: (JBRULES-2049) org.drools.runtime.rule StatefulRuleSession.fireAllRules(org.drools.runtime.rule.AgendaFilter af) has no AgendaFilter implementations

by Bob Shanahan (JIRA)

org.drools.runtime.rule StatefulRuleSession.fireAllRules(org.drools.runtime.rule.AgendaFilter af) has no AgendaFilter implementations ------------------------------------------------------------------------------------------------------------------------------------- Key: JBRULES-2049 URL: https://jira.jboss.org/jira/browse/JBRULES-2049 Project: JBoss Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-api, drools-core Affects Versions: 5.0.0.CR1 Environment: Java 1.5 Reporter: Bob Shanahan Assignee: Mark Proctor StatefulSession.fireAllRules(org.drools.spi.AgendaFilter af) has several implementations of AgendaFilter for filtering rules. Why aren't the AgendaFilters common? Even the Activation class between them is different, so it is not simple to workaround by wrapping org.drools.spi.AgendaFilter impls. It would be handy if there were out-of-the-box AgendaFilters for implementations of StatefulRuleSession. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

6
8
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2010