January 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-744) Rule Generation Feature Request

by Michael Biarnes Kiefer (JIRA)

[ https://issues.jboss.org/browse/DROOLS-744?page=com.atlassian.jira.plugin... ] Michael Biarnes Kiefer updated DROOLS-744: ------------------------------------------ Fix Version/s: 6.4.0.CR1 (was: 6.4.0.Beta1) > Rule Generation Feature Request > ------------------------------- > > Key: DROOLS-744 > URL: https://issues.jboss.org/browse/DROOLS-744 > Project: Drools > Issue Type: Feature Request > Components: core engine, kie server > Affects Versions: 6.2.0.Final > Reporter: Justin Holmes > Assignee: Mario Fusco > Fix For: 6.4.0.CR1 > > > As a developer using Drools, I want a rule generation java api that supports control logic in the rule templates (e.g. for loops, if/else) and integrates with the rule workbench in order to build highly dynamic business rules driven systems. > The initial thought process around implementation is to build two things 1) a simple way to author mvel templates in business central, the existing text editor could be used at first and 2) a simple embedded java api in it's own maven module which can checkout the git project that has the mvel template, apply a set of domain objects to the template, check in the resulting rule files to the local git repo and then push the changes back to business central. This allows us to leverage the power of the existing MVEL and JGit tech stack while pushing the complexity to a java api, where we are stronger than the workbench itself. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-709) fuse-bxms-integ list of build/release issues

by Michael Biarnes Kiefer (JIRA)

[ https://issues.jboss.org/browse/DROOLS-709?page=com.atlassian.jira.plugin... ] Michael Biarnes Kiefer updated DROOLS-709: ------------------------------------------ Fix Version/s: 6.4.0.CR1 (was: 6.4.0.Beta1) > fuse-bxms-integ list of build/release issues > -------------------------------------------- > > Key: DROOLS-709 > URL: https://issues.jboss.org/browse/DROOLS-709 > Project: Drools > Issue Type: Bug > Reporter: Geoffrey De Smet > Assignee: Edson Tirelli > Priority: Blocker > Fix For: 6.4.0.CR1 > > > Here's a summary of the issues discussed in e-mail so we can track them. > 1) fuse-bxms-integ violates Red Hat naming: > We can't use a product name ("Fuse", "bxms") for community code. > The repository contains community glue code between camel and kie, > so for example "camel-kie-integ" would be better. > Is drools-camel open source? > If yes, then we want the community to be able to use it and report issues before we release the product version. > 2) The artifacts of fuse-bxms-integ all still use the groupId "org.kie", > but supposedly have their a different version numbering than org.kie's artifacts. > 2 artifacts in the same groupId must use the exact same version numbering and release lifecycle! > So the groupId must be changed before its released. > 3) fuse-bxms-integ will use it's own version numbering, so it should not use kie's "6.2.0.Final" > Either it uses a neutral number, such as "1.0.0.Final" > or it defines a pattern based on it's kie and it's camel dependency. For example "6.2.0.Final-2.14.1.Final" (bad example, violates OSGi guidelines). > Calling it "6.2.0.Final" is just asking for confusion and trouble, > because productization scripts will presume it's 100% equal to the kie version. > 4) Now one seems to have the faintest idea how we'll handle branching: think camel 2.14.x, camel 2.13.x, kie 6.2.x, camel 2.12.x, kie 6.1.x, ... > 5) // Not valid > 6) Renaming the java packages according to the new groupId/artifactId we will choose (as we did in the past with all other projects) and also fix the OSGi manifest and features.xml files accordingly. > 7) migrating the optaplanner-camel module in the new integration project. > Note: ge0ffrey will migrate optaplanner-camel after the other issues in this list are solved to avoid breaking users now. > 8) It's artifacts are currently: > - no longer extending droolsjbpm-parent(-with-dependencies) > - no longer in the kie-bom > and that the repo is no longer in our github organization or git-clone-others script, but it is part of our release. > So it's already quite different than in 6.1. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1023) Change kmodule.xsd targetNamespace to become versionless (to avoid hardcoding "6.0.0" in it)

by Michael Biarnes Kiefer (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1023?page=com.atlassian.jira.plugi... ] Michael Biarnes Kiefer updated DROOLS-1023: ------------------------------------------- Fix Version/s: 6.4.0.CR1 (was: 6.4.0.Beta1) > Change kmodule.xsd targetNamespace to become versionless (to avoid hardcoding "6.0.0" in it) > -------------------------------------------------------------------------------------------- > > Key: DROOLS-1023 > URL: https://issues.jboss.org/browse/DROOLS-1023 > Project: Drools > Issue Type: Enhancement > Components: core engine > Affects Versions: 6.3.0.Final > Reporter: Geoffrey De Smet > Assignee: Geoffrey De Smet > Fix For: 6.4.0.CR1 > > > Switch namespace to "http://www.drools.org/xsd/kmodule". > But also make sure that the old namespace "http://jboss.org/kie/6.0.0/kmodule" still works. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1013) Error jitting a compareTo constraint

by Michael Biarnes Kiefer (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1013?page=com.atlassian.jira.plugi... ] Michael Biarnes Kiefer updated DROOLS-1013: ------------------------------------------- Fix Version/s: 6.4.0.CR1 (was: 6.4.0.Beta1) > Error jitting a compareTo constraint > ------------------------------------ > > Key: DROOLS-1013 > URL: https://issues.jboss.org/browse/DROOLS-1013 > Project: Drools > Issue Type: Bug > Reporter: Mario Fusco > Assignee: Mario Fusco > Fix For: 6.4.0.CR1 > > > When the implementation of the Comparable interface is not directly declared by a Class, but the Class implements another interface that transitively extends Comparable the jitting of a constraint doing a compareTo on that class fails with the following exception: > {code} > Exception in thread "Thread-0" java.lang.NoSuchMethodError: java.time.LocalDateTime.compareTo(Ljava/time/LocalDateTimeI > at ConditionEvaluator8566b06b2be943a7ba50f1700fa7b033.evaluate(Unknown Source) > at org.drools.core.rule.constraint.MvelConstraint.evaluate(MvelConstraint.java:248) > at org.drools.core.rule.constraint.MvelConstraint.isAllowed(MvelConstraint.java:204) > at org.drools.core.reteoo.AlphaNode.assertObject(AlphaNode.java:141) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1034) Kie server test improvement for Oracle RAC

by Jakub Schwan (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1034?page=com.atlassian.jira.plugi... ] Jakub Schwan updated DROOLS-1034: --------------------------------- Description: Sometimes some tests failed on Oracle RAC database due invalid id ordering from db. Some older data has higher id then the newer data. It's caused by how Oracle RAC assigns IDs. On other databases tests run fine. was: Sometimes some tests failed on Oracle RAC database due invalid id ordering from db. Some older data has higher id then the newer data. It's caused by identifying of Oracle RAC. On other databases tests run fine. > Kie server test improvement for Oracle RAC > ------------------------------------------ > > Key: DROOLS-1034 > URL: https://issues.jboss.org/browse/DROOLS-1034 > Project: Drools > Issue Type: Bug > Components: kie server > Affects Versions: 6.3.0.Final > Environment: Oracle 11g R2 RAC > Reporter: Jakub Schwan > Assignee: Jakub Schwan > Labels: reported-by-qe > > Sometimes some tests failed on Oracle RAC database due invalid id ordering from db. Some older data has higher id then the newer data. It's caused by how Oracle RAC assigns IDs. > On other databases tests run fine. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1034) Kie server test improvement for Oracle RAC

by Jakub Schwan (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1034?page=com.atlassian.jira.plugi... ] Jakub Schwan updated DROOLS-1034: --------------------------------- Affects Version/s: 6.3.0.Final > Kie server test improvement for Oracle RAC > ------------------------------------------ > > Key: DROOLS-1034 > URL: https://issues.jboss.org/browse/DROOLS-1034 > Project: Drools > Issue Type: Bug > Components: kie server > Affects Versions: 6.3.0.Final > Environment: Oracle 11g R2 RAC > Reporter: Jakub Schwan > Assignee: Jakub Schwan > Labels: reported-by-qe > > Sometimes some tests failed on Oracle RAC database due invalid id ordering from db. Some older data has higher id then the newer data. It's caused by identifying of Oracle RAC. > On other databases tests run fine. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1034) Kie server test improvement for Oracle RAC

by Jakub Schwan (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1034?page=com.atlassian.jira.plugi... ] Jakub Schwan updated DROOLS-1034: --------------------------------- Issue Type: Bug (was: Feature Request) > Kie server test improvement for Oracle RAC > ------------------------------------------ > > Key: DROOLS-1034 > URL: https://issues.jboss.org/browse/DROOLS-1034 > Project: Drools > Issue Type: Bug > Components: kie server > Environment: Oracle 11g R2 RAC > Reporter: Jakub Schwan > Assignee: Jakub Schwan > Labels: reported-by-qe > > Sometimes some tests failed on Oracle RAC database due invalid id ordering from db. Some older data has higher id then the newer data. It's caused by identifying of Oracle RAC. > On other databases tests run fine. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1034) Kie server test improvement for Oracle RAC

by Jakub Schwan (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1034?page=com.atlassian.jira.plugi... ] Jakub Schwan updated DROOLS-1034: --------------------------------- Labels: reported-by-qe (was: ) > Kie server test improvement for Oracle RAC > ------------------------------------------ > > Key: DROOLS-1034 > URL: https://issues.jboss.org/browse/DROOLS-1034 > Project: Drools > Issue Type: Bug > Components: kie server > Environment: Oracle 11g R2 RAC > Reporter: Jakub Schwan > Assignee: Jakub Schwan > Labels: reported-by-qe > > Sometimes some tests failed on Oracle RAC database due invalid id ordering from db. Some older data has higher id then the newer data. It's caused by identifying of Oracle RAC. > On other databases tests run fine. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1313) User with Slash char in LDAP name cannot log in through security-realm

by Hynek Švábek (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1313?page=com.atlassian.jira.plugi... ] Hynek Švábek moved WFLY-6037 to WFCORE-1313: -------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-1313 (was: WFLY-6037) Component/s: Security (was: Security) > User with Slash char in LDAP name cannot log in through security-realm > ---------------------------------------------------------------------- > > Key: WFCORE-1313 > URL: https://issues.jboss.org/browse/WFCORE-1313 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Hynek Švábek > Assignee: Darran Lofthouse > > According to LDAP specification [1], DN can contain slash char without escaping, etc. > I am not able to log in to management console with username "Slash/Char". But I would be able to log in there. > I can see this in Wireshark > {code} > LDAPMessage bindRequest(1) ""uid=Slash/Char",ou=People,o=LdapRealmSpecialNameManualTest7d339efa,o=primary,dc=jboss,dc=org" simple > LDAPMessage bindResponse(1) invalidDNSyntax (Incorrect DN given : "uid=Slash/Char",ou=People,o=LdapRealmSpecialNameManualTest7d339efa,o=primary,dc=jboss,dc=org (0x22 0x75 0x69 0x64 0x3D 0x53 0x6C 0x61 0x73 0x68 0x2F 0x43 0x68 0x61 0x72 0x2 > {code} > You can see there quotation marks around *uid=Slash/Char*. > In my opinion problem can be somewhere around this > {code} > javax.naming.NameImpl.stringifyComp(String comp) > {code} > [1] https://tools.ietf.org/html/rfc2253#section-3 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1304) WFLYCTL0013: Operation ("clean-obsolete-content") failed .. StringIndexOutOfBoundsException when OS puts metadata files in content repo

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1304?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on WFCORE-1304: ------------------------------------------------- Chao Wang <chaowan(a)redhat.com> changed the Status of [bug 1299189|https://bugzilla.redhat.com/show_bug.cgi?id=1299189] from ASSIGNED to POST > WFLYCTL0013: Operation ("clean-obsolete-content") failed .. StringIndexOutOfBoundsException when OS puts metadata files in content repo > --------------------------------------------------------------------------------------------------------------------------------------- > > Key: WFCORE-1304 > URL: https://issues.jboss.org/browse/WFCORE-1304 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Brad Maxwell > Assignee: Chao Wang > > Mac OS can put .DS_Store files into the content repo directory. This can also be reproduced on Linux by creating a file under the content dir and when clean-obsolete-content() runs it will log this error. It seems it runs every 10 minutes. > {code} > 22:59:48,289 INFO [org.jboss.as.repository] (ServerService Thread Pool -- 1) WFLYDR0009: Content /Users/bradley/Desktop/wildfly-10.0.0.CR5/standalone/data/content/9b/.DS_Store is obsolete and will be removed > 22:59:48,290 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 1) WFLYCTL0013: Operation ("clean-obsolete-content") failed - address: ([]): java.lang.StringIndexOutOfBoundsException: String index out of range: 11 > at java.lang.String.charAt(String.java:658) > at org.jboss.as.repository.HashUtil.hexStringToByteArray(HashUtil.java:62) > at org.jboss.as.repository.ContentReference.getHash(ContentReference.java:68) > at org.jboss.as.repository.ContentRepository$Factory$ContentRepositoryImpl.removeContent(ContentRepository.java:365) > at org.jboss.as.repository.ContentRepository$Factory$ContentRepositoryImpl.markAsObsolete(ContentRepository.java:427) > at org.jboss.as.repository.ContentRepository$Factory$ContentRepositoryImpl.cleanObsoleteContent(ContentRepository.java:403) > at org.jboss.as.server.operations.CleanObsoleteContentHandler.execute(CleanObsoleteContentHandler.java:76) > at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:890) > at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:659) > at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:370) > at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1344) > at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:392) > at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:204) > at org.jboss.as.controller.ModelControllerImpl$3.execute(ModelControllerImpl.java:659) > at org.jboss.as.controller.ModelControllerImpl$3.execute(ModelControllerImpl.java:649) > at org.jboss.as.server.deployment.ContentRepositoryCleaner.cleanObsoleteContent(ContentRepositoryCleaner.java:132) > at org.jboss.as.server.deployment.ContentRepositoryCleaner$ContentRepositoryCleanerTask.run(ContentRepositoryCleaner.java:67) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) > at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) > at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > at org.jboss.threads.JBossThread.run(JBossThread.java:320) > 22:59:48,292 ERROR [org.jboss.as.server] (ServerService Thread Pool -- 1) WFLYSRV0216: Error cleaning obsolete content WFLYCTL0158: Operation handler failed: java.lang.StringIndexOutOfBoundsException: String index out of range: 11 > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
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 January 2016