July 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-2726) optaplanner with aws lambda

by Adeela Huma (JIRA)

Adeela Huma created DROOLS-2726: ----------------------------------- Summary: optaplanner with aws lambda Key: DROOLS-2726 URL: https://issues.jboss.org/browse/DROOLS-2726 Project: Drools Issue Type: Feature Request Affects Versions: 7.7.0.Final Reporter: Adeela Huma Assignee: Edson Tirelli Reporting the bug from stack overflow discussion: https://stackoverflow.com/questions/51273121/optaplanner-with-aws-lambda -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-712) Endpoint doesn't respond JSON requests

by Tibor Zimányi (JIRA)

[ https://issues.jboss.org/browse/DROOLS-712?page=com.atlassian.jira.plugin... ] Tibor Zimányi closed DROOLS-712. -------------------------------- Resolution: Out of Date > Endpoint doesn't respond JSON requests > -------------------------------------- > > Key: DROOLS-712 > URL: https://issues.jboss.org/browse/DROOLS-712 > Project: Drools > Issue Type: Bug > Affects Versions: 6.2.0.CR4 > Environment: jboss 7.1.1 on windows 7 > Reporter: bala K > Assignee: Mark Proctor > > I am using latest version of kie-server-6.2.CR4 only,war downloaded from the https://repository.jboss.org/nexus/content/groups/public/org/kie/kie-serv... > with xml request getting proper response,but when ever try to use JSON request throwing the below expection. > error: > ==== > com.thoughtworks.xstream.io.StreamException: : only whitespace content > allowed before start tag and not { (position: START_DOCUMENT seen {... @1:1) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-973) Endpoint doesn't respond JSON requests

by Tibor Zimányi (JIRA)

[ https://issues.jboss.org/browse/DROOLS-973?page=com.atlassian.jira.plugin... ] Tibor Zimányi closed DROOLS-973. -------------------------------- Resolution: Out of Date > Endpoint doesn't respond JSON requests > -------------------------------------- > > Key: DROOLS-973 > URL: https://issues.jboss.org/browse/DROOLS-973 > Project: Drools > Issue Type: Sub-task > Components: core engine > Affects Versions: 6.3.0.Final > Environment: Drools 6.3.0 Final, CentOS 6.4, WildFly. > Reporter: 재우 이 > Assignee: Mario Fusco > > The below erros occured again in drools 6.3.0. > ------------------------------------------------------------------------------------- > DROOLS-712 > I am using latest version of kie-server-6.2.CR4 only,war downloaded from the https://repository.jboss.org/nexus/content/groups/public/org/kie/kie-serv... > with xml request getting proper response,but when ever try to use JSON request throwing the below expection. > error: > ==== > com.thoughtworks.xstream.io.StreamException: : only whitespace content > allowed before start tag and not { (position: START_DOCUMENT seen {... @1:1) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-2656) PNGs for the toolbox icons for the different connector types.

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2656?page=com.atlassian.jira.plugi... ] Michael Anstis updated DROOLS-2656: ----------------------------------- Attachment: edit.svg > PNGs for the toolbox icons for the different connector types. > ------------------------------------------------------------- > > Key: DROOLS-2656 > URL: https://issues.jboss.org/browse/DROOLS-2656 > Project: Drools > Issue Type: Sub-task > Reporter: Liz Clayton > Assignee: Brian Dellascio > Labels: IconRequest, UX, UXTeam, VisualDesign, drools-tools > Attachments: edit.svg > > > PNGs for the toolbox icons for the different connector types. > Their appearance can be seen in https://www.omg.org/spec/DMN/1.1/PDF (page 30, "Association", "Information Requirement", "Knowledge Requirement" and "Authority Requirement"). They'll only be used as icons on the toolbox (see screenshot attached). Could you please also remind me of the BAPL for the new "Node" SVGs (I'll need to make PNGs of those too for the same "toolbox" purpose.. unless UX have a tool to convert SVG to PNG?) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-2656) PNGs for the toolbox icons for the different connector types.

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2656?page=com.atlassian.jira.plugi... ] Michael Anstis commented on DROOLS-2656: ---------------------------------------- Hi [~bdellasc] I've attached "edit.svg" which is a SVG for an existing toolbox icon. It looks like Stunner scales them to 15x15 with a border of 5 (but bizarrely 20x20 in total, so really IMO the border is 2.5). You'll notice how I've not mentioned the scale of these measurements (pixels, centimetres, miles etc).. that's because simply put I do not know. I'd guess they simply follow the same scale system as the HTML canvas, but TBH I think if you make the connector icons the same size as the SVG above it'll be fine. > PNGs for the toolbox icons for the different connector types. > ------------------------------------------------------------- > > Key: DROOLS-2656 > URL: https://issues.jboss.org/browse/DROOLS-2656 > Project: Drools > Issue Type: Sub-task > Reporter: Liz Clayton > Assignee: Brian Dellascio > Labels: IconRequest, UX, UXTeam, VisualDesign, drools-tools > Attachments: edit.svg > > > PNGs for the toolbox icons for the different connector types. > Their appearance can be seen in https://www.omg.org/spec/DMN/1.1/PDF (page 30, "Association", "Information Requirement", "Knowledge Requirement" and "Authority Requirement"). They'll only be used as icons on the toolbox (see screenshot attached). Could you please also remind me of the BAPL for the new "Node" SVGs (I'll need to make PNGs of those too for the same "toolbox" purpose.. unless UX have a tool to convert SVG to PNG?) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-962) Kie-CI integration with Applications using Guava

by Tibor Zimányi (JIRA)

[ https://issues.jboss.org/browse/DROOLS-962?page=com.atlassian.jira.plugin... ] Tibor Zimányi commented on DROOLS-962: -------------------------------------- Is this still relevant? I checked and there is Guava 20 used on master branch. > Kie-CI integration with Applications using Guava > ------------------------------------------------ > > Key: DROOLS-962 > URL: https://issues.jboss.org/browse/DROOLS-962 > Project: Drools > Issue Type: Bug > Components: core engine, tools > Affects Versions: 6.2.0.Final > Environment: Drools WB - 6.2.0.Final > Tomcat 7/8 > Reporter: Jebuselwyn Martin > Assignee: Mario Fusco > Fix For: 6.2.0.Final > > > Unable to start application with the 'kie-ci' dependency due to the older version of Guava transitively pulled from maven libraries. > Caused by: java.lang.IllegalAccessError: tried to access method com.google.common.collect.MapMaker.makeComputingMap(Lcom/google/common/base/Function;)Ljava/util/concurrent/ConcurrentMap; from class com.google.inject.internal.Annotations$AnnotationChecker > at com.google.inject.internal.Annotations$AnnotationChecker.<init>(Annotations.java:104) > at com.google.inject.internal.Annotations.<clinit>(Annotations.java:122) > at com.google.inject.Key.ensureRetainedAtRuntime(Key.java:362) > at com.google.inject.Key.strategyFor(Key.java:354) > at com.google.inject.Key.get(Key.java:222) > at org.eclipse.sisu.wire.ParameterKeys.<clinit>(ParameterKeys.java:28) > at org.eclipse.sisu.wire.DependencyAnalyzer.<init>(DependencyAnalyzer.java:92) > at org.eclipse.sisu.wire.ElementAnalyzer.<init>(ElementAnalyzer.java:87) > at org.eclipse.sisu.wire.WireModule.configure(WireModule.java:74) > at com.google.inject.spi.Elements$RecordingBinder.install(Elements.java:229) > at com.google.inject.spi.Elements.getElements(Elements.java:103) > at com.google.inject.internal.InjectorShell$Builder.build(InjectorShell.java:136) > at com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:104) > at com.google.inject.Guice.createInjector(Guice.java:94) > at com.google.inject.Guice.createInjector(Guice.java:71) > at com.google.inject.Guice.createInjector(Guice.java:61) > More details here: > https://groups.google.com/forum/#!topic/drools-setup/Mq6dW_fhQ9I -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-939) Refactor jBPM and Drools to separate commonly used classes into shared modules

by Tibor Zimányi (JIRA)

[ https://issues.jboss.org/browse/DROOLS-939?page=com.atlassian.jira.plugin... ] Tibor Zimányi closed DROOLS-939. -------------------------------- Resolution: Won't Do Closing this as it is a very old issue and has very broad scope. > Refactor jBPM and Drools to separate commonly used classes into shared modules > ------------------------------------------------------------------------------ > > Key: DROOLS-939 > URL: https://issues.jboss.org/browse/DROOLS-939 > Project: Drools > Issue Type: Task > Components: core engine > Affects Versions: 6.3.0.Final > Reporter: Marco Rietveld > Assignee: Mario Fusco > Original Estimate: 8 weeks > Remaining Estimate: 8 weeks > > There are a number of {{drools-core}} and {{drools-compiler}} classes that are being used in the jBPM modules. > In order to make both drools _and_ jBPM development more efficient, we want to refactor those shared classes out of the {{drools-core}} and {{drools-compiler}} modules into shared "{{kie-}}" modules. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-1233) Memory references to removed facts are retained for certain rules

by Tibor Zimányi (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1233?page=com.atlassian.jira.plugi... ] Tibor Zimányi closed DROOLS-1233. --------------------------------- Resolution: Duplicate Issue Closing this as it is marked as a duplicate. > Memory references to removed facts are retained for certain rules > ----------------------------------------------------------------- > > Key: DROOLS-1233 > URL: https://issues.jboss.org/browse/DROOLS-1233 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 6.4.0.Final > Reporter: Jon Kranes > Assignee: Mario Fusco > Attachments: drools-memory-test.zip, gc-root.jpg, gc-root.tiff, heap-dump.jpg, heap-dump.tiff > > > Given a simple rule of a specific pattern, Drools maintains references in a stateful session to fact objects even after the facts have been withdrawn from working memory. > For example, given the following rule: > {code} > rule "TestRule" > when > $tc : TestClass() > not TestClass2(name == $tc.name) > then > insert(new TestClass2($tc.getName())); > end > {code} > Drools will maintain an internal reference to instances of TestClass even after they have been explicitly deleted from the session. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-3396) Provide certificate authority integration

by Martin Choma (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3396?page=com.atlassian.jira.plugi... ] Martin Choma commented on WFCORE-3396: -------------------------------------- I think tests well cover the area. However it would be better if tests were located in WFCore/WF for testing Elytron subsystem part as well. Several questions which pop up: - what is maintability of mock messages. For new version clone of test will be created? - How are we going to deal with new versions of Lets Encrypt API. Does LE keep backward compatibility? > Provide certificate authority integration > ----------------------------------------- > > Key: WFCORE-3396 > URL: https://issues.jboss.org/browse/WFCORE-3396 > Project: WildFly Core > Issue Type: Feature Request > Components: Security > Affects Versions: 4.0.0.Alpha2 > Reporter: Martin Choma > Assignee: Farah Juma > > Let's Encrypt provide API to fully automate (gain/renew) certificate retrieval using ACME protocol. Integrate this capability into wildfly. > This can simplify administrator work. No need to perform certification renewal routine tasks. > This is follow up on WFCORE-3305 and piece of bigger task "Simplify SSL configuration in wildfly". That said it is just "User experience" issue. Administrator still can work with Let's Encrypt by third party client and just reference wildfly to this certificate. > [1] Latest draft: https://tools.ietf.org/html/draft-ietf-acme-acme-10 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-2725) Executable model cannot handle fieldnames with second letter in uppercase

by Tibor Zimányi (JIRA)

Tibor Zimányi created DROOLS-2725: ------------------------------------- Summary: Executable model cannot handle fieldnames with second letter in uppercase Key: DROOLS-2725 URL: https://issues.jboss.org/browse/DROOLS-2725 Project: Drools Issue Type: Bug Components: core engine Affects Versions: 7.8.0.Final Reporter: Tibor Zimányi Assignee: Mario Fusco Having a test case like this [1], the executable model fails with: "java.lang.AssertionError: [Message [id=1, kieBase=defaultKieBase, level=ERROR, path=r0.drl, line=-1, column=0 text=Unable to parse left part of expression: aBcde == "test"]]" [1] https://gist.github.com/baldimir/7b4067d74d5fe32b0cb2360de14fd344 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

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 July 2018