June 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-1216) Minus operator in Elytron SASL mechanism selector does not prevent mechanism from occuring later

by Ondrej Lukas (JIRA)

Ondrej Lukas created ELY-1216: --------------------------------- Summary: Minus operator in Elytron SASL mechanism selector does not prevent mechanism from occuring later Key: ELY-1216 URL: https://issues.jboss.org/browse/ELY-1216 Project: WildFly Elytron Issue Type: Bug Reporter: Ondrej Lukas Assignee: Darran Lofthouse Priority: Critical Minus operatar should work as following: _The - operator deletes all entries that match the given name or predicate, preventing them from occurring later._ [1] When SASL mechanism selector includes {{-}} operator for some mechanism and this mechanism is added again then this mechanism can be used. It means it violates 'preventing them from occurring later'. e.g. {{PLAIN}} mechanism can be incorrectly used when selectors like {{selector="-PLAIN PLAIN"}} or {{selector="-PLAIN #ALL"}} are used for client. [1] https://issues.jboss.org/browse/EAP7-567?focusedCommentId=13408238&page=c... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1388) Drools Sample.drl broken with Eclipse Neon

by Vincenzo D'Amore (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1388?page=com.atlassian.jira.plugi... ] Vincenzo D'Amore closed DROOLS-1388. ------------------------------------ Release Notes Text: The bug was related to a local misconfiguration Resolution: Rejected > Drools Sample.drl broken with Eclipse Neon > ------------------------------------------ > > Key: DROOLS-1388 > URL: https://issues.jboss.org/browse/DROOLS-1388 > Project: Drools > Issue Type: Bug > Components: eclipse plugin > Affects Versions: 6.5.0.Final > Reporter: Vincenzo D'Amore > Assignee: Robert (Bob) Brodt > > Unable to complete the example presented in the documentation "[Installing Drools Tooling|https://nheron.gitbooks.io/droolsonboarding/content/gettingStarted/installing_drools_tooling.html]" > Trying to run DroolsTest.java sample I get the following errors: > {code:java} > java.lang.RuntimeException: Error while creating KieBase[Message [id=1, level=ERROR, path=Sample.drl, line=15, column=0 > text=Rule Compilation error Only a type can be imported. com.sample.DroolsTest.Message resolves to a package > Only a type can be imported. org.drools.core.spi.KnowledgeHelper resolves to a package > KnowledgeHelper cannot be resolved to a type > org.kie.api.runtime.rule.FactHandle cannot be resolved to a type > java.lang.Exception cannot be resolved to a type > org.kie.api.runtime.rule.RuleContext cannot be resolved to a type], Message [id=2, level=ERROR, path=Sample.drl, line=5, column=0 > text=Rule Compilation error Only a type can be imported. com.sample.DroolsTest.Message resolves to a package > Only a type can be imported. org.drools.core.spi.KnowledgeHelper resolves to a package > KnowledgeHelper cannot be resolved to a type > com.sample.DroolsTest.Message cannot be resolved to a type > org.kie.api.runtime.rule.FactHandle cannot be resolved to a type > org.kie.api.runtime.rule.FactHandle cannot be resolved to a type > java.lang.Exception cannot be resolved to a type > org.kie.api.runtime.rule.RuleContext cannot be resolved to a type > Message.GOODBYE cannot be resolved to a type > org.drools.core.util.bitmask.AllSetBitMask cannot be resolved to a type > com.sample.DroolsTest.Message cannot be resolved to a type]] > at org.drools.compiler.kie.builder.impl.KieContainerImpl.getKieBase(KieContainerImpl.java:450) > at org.drools.compiler.kie.builder.impl.KieContainerImpl.newKieSession(KieContainerImpl.java:604) > at org.drools.compiler.kie.builder.impl.KieContainerImpl.newKieSession(KieContainerImpl.java:575) > at com.sample.DroolsTest.main(DroolsTest.java:17) > {code} > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2896) Revisit CLI Ctrl-C handling

by Jean-Francois Denise (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2896?page=com.atlassian.jira.plugi... ] Jean-Francois Denise updated WFCORE-2896: ----------------------------------------- Description: Ctrl-C typed in the CLI behaviour: - If auto-connect is enabled (-c option). If prompt occurs for credentials, typing Ctrl-C should exit the CLI process - As soon as we have reached the CLI prompt, any prompting is bound to a command execution (eg: connect, reload, ...), in that case Ctrl-C shouldn't exit the process. It should interrupt the command - Ctrl-C typed for long running command should only interrupt the command. - Ctrl-C typed when pausing long output should only interrupt output pause. - Ctrl-C typed in the terminal without command running exit the CLI process. was: Ctrl-C typed in the CLI behaviour: - If auto-connect is enabled (-c option). If prompt occurs for credentials, typing Ctrl-C should exit the CLI process - As soon as we have reached the CLI prompt, any prompting is bound to a command execution (eg: connect, reload, ...), in that case Ctrl-C shouldn't exit the process. It should interrupt the command - Ctrl-C typed for long running command should only interrupt the command. - Ctrl-C typed when pausing long output should only interrupt output pause. > Revisit CLI Ctrl-C handling > --------------------------- > > Key: WFCORE-2896 > URL: https://issues.jboss.org/browse/WFCORE-2896 > Project: WildFly Core > Issue Type: Enhancement > Components: CLI > Reporter: Jean-Francois Denise > Assignee: Jean-Francois Denise > > Ctrl-C typed in the CLI behaviour: > - If auto-connect is enabled (-c option). If prompt occurs for credentials, typing Ctrl-C should exit the CLI process > - As soon as we have reached the CLI prompt, any prompting is bound to a command execution (eg: connect, reload, ...), in that case Ctrl-C shouldn't exit the process. It should interrupt the command > - Ctrl-C typed for long running command should only interrupt the command. > - Ctrl-C typed when pausing long output should only interrupt output pause. > - Ctrl-C typed in the terminal without command running exit the CLI process. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2896) Revisit CLI Ctrl-C handling

by Jean-Francois Denise (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2896?page=com.atlassian.jira.plugi... ] Jean-Francois Denise commented on WFCORE-2896: ---------------------------------------------- [~rhusar], that is an interesting feedback. We were thinking to keep the existing behaviour (a lot of habit there) but this is something we could make configurable. You would just have to setup your CLI instance via XML or new command. > Revisit CLI Ctrl-C handling > --------------------------- > > Key: WFCORE-2896 > URL: https://issues.jboss.org/browse/WFCORE-2896 > Project: WildFly Core > Issue Type: Enhancement > Components: CLI > Reporter: Jean-Francois Denise > Assignee: Jean-Francois Denise > > Ctrl-C typed in the CLI behaviour: > - If auto-connect is enabled (-c option). If prompt occurs for credentials, typing Ctrl-C should exit the CLI process > - As soon as we have reached the CLI prompt, any prompting is bound to a command execution (eg: connect, reload, ...), in that case Ctrl-C shouldn't exit the process. It should interrupt the command > - Ctrl-C typed for long running command should only interrupt the command. > - Ctrl-C typed when pausing long output should only interrupt output pause. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2896) Revisit CLI Ctrl-C handling

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2896?page=com.atlassian.jira.plugi... ] Radoslav Husar commented on WFCORE-2896: ---------------------------------------- How about the case when nothing is being executed? CTRL+C currently exits the process. I would prefer bash-like behavior, i.e. discarding what is typed and start a new line and to exit, feed EOL (CTRL+D). > Revisit CLI Ctrl-C handling > --------------------------- > > Key: WFCORE-2896 > URL: https://issues.jboss.org/browse/WFCORE-2896 > Project: WildFly Core > Issue Type: Enhancement > Components: CLI > Reporter: Jean-Francois Denise > Assignee: Jean-Francois Denise > > Ctrl-C typed in the CLI behaviour: > - If auto-connect is enabled (-c option). If prompt occurs for credentials, typing Ctrl-C should exit the CLI process > - As soon as we have reached the CLI prompt, any prompting is bound to a command execution (eg: connect, reload, ...), in that case Ctrl-C shouldn't exit the process. It should interrupt the command > - Ctrl-C typed for long running command should only interrupt the command. > - Ctrl-C typed when pausing long output should only interrupt output pause. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1590) The behavior of rule flow is different in drools 6.4.0 Final and 6.5.0 Final

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1590?page=com.atlassian.jira.plugi... ] Mario Fusco resolved DROOLS-1590. --------------------------------- Resolution: Rejected The system is behaving as per design > The behavior of rule flow is different in drools 6.4.0 Final and 6.5.0 Final > ---------------------------------------------------------------------------- > > Key: DROOLS-1590 > URL: https://issues.jboss.org/browse/DROOLS-1590 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 6.5.0.Final > Reporter: GaoShengwei GaoShengwei > Assignee: Mario Fusco > Attachments: BaiduHi_2017-5-31_18-1-18.png, BaiduHi_2017-5-31_18-2-54.png > > > I am using drools 6.5.0 Final. When I run sample code of section "starting a ruleflow from a rule" in documentation (https://nheron.gitbooks.io/droolsonboarding/content/gettingStarted/lesson...), the output sequence is different from the screenshot. > But when I switched to drools version to 6.4.0 Final, the output sequence was extactly same with screenshot. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1388) Drools Sample.drl broken with Eclipse Neon

by Nicolas Heron (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1388?page=com.atlassian.jira.plugi... ] Nicolas Heron commented on DROOLS-1388: --------------------------------------- Can you close that jira as you found the problem ? Hope the book helps regards > Drools Sample.drl broken with Eclipse Neon > ------------------------------------------ > > Key: DROOLS-1388 > URL: https://issues.jboss.org/browse/DROOLS-1388 > Project: Drools > Issue Type: Bug > Components: eclipse plugin > Affects Versions: 6.5.0.Final > Reporter: Vincenzo D'Amore > Assignee: Robert (Bob) Brodt > > Unable to complete the example presented in the documentation "[Installing Drools Tooling|https://nheron.gitbooks.io/droolsonboarding/content/gettingStarted/installing_drools_tooling.html]" > Trying to run DroolsTest.java sample I get the following errors: > {code:java} > java.lang.RuntimeException: Error while creating KieBase[Message [id=1, level=ERROR, path=Sample.drl, line=15, column=0 > text=Rule Compilation error Only a type can be imported. com.sample.DroolsTest.Message resolves to a package > Only a type can be imported. org.drools.core.spi.KnowledgeHelper resolves to a package > KnowledgeHelper cannot be resolved to a type > org.kie.api.runtime.rule.FactHandle cannot be resolved to a type > java.lang.Exception cannot be resolved to a type > org.kie.api.runtime.rule.RuleContext cannot be resolved to a type], Message [id=2, level=ERROR, path=Sample.drl, line=5, column=0 > text=Rule Compilation error Only a type can be imported. com.sample.DroolsTest.Message resolves to a package > Only a type can be imported. org.drools.core.spi.KnowledgeHelper resolves to a package > KnowledgeHelper cannot be resolved to a type > com.sample.DroolsTest.Message cannot be resolved to a type > org.kie.api.runtime.rule.FactHandle cannot be resolved to a type > org.kie.api.runtime.rule.FactHandle cannot be resolved to a type > java.lang.Exception cannot be resolved to a type > org.kie.api.runtime.rule.RuleContext cannot be resolved to a type > Message.GOODBYE cannot be resolved to a type > org.drools.core.util.bitmask.AllSetBitMask cannot be resolved to a type > com.sample.DroolsTest.Message cannot be resolved to a type]] > at org.drools.compiler.kie.builder.impl.KieContainerImpl.getKieBase(KieContainerImpl.java:450) > at org.drools.compiler.kie.builder.impl.KieContainerImpl.newKieSession(KieContainerImpl.java:604) > at org.drools.compiler.kie.builder.impl.KieContainerImpl.newKieSession(KieContainerImpl.java:575) > at com.sample.DroolsTest.main(DroolsTest.java:17) > {code} > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1590) The behavior of rule flow is different in drools 6.4.0 Final and 6.5.0 Final

by Nicolas Heron (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1590?page=com.atlassian.jira.plugi... ] Nicolas Heron commented on DROOLS-1590: --------------------------------------- Hi, In version 6.5 the logging with the callbak is a little different. So the rule logging is done after the rule flow group logging is done. It is annoying but there is no bug. see "The Rule xxx can be fired in agenda " => it means it is done during the agenda of the rule-flow group I will try to update the gitbook Hope the book helps you ! Regards Nicolas > The behavior of rule flow is different in drools 6.4.0 Final and 6.5.0 Final > ---------------------------------------------------------------------------- > > Key: DROOLS-1590 > URL: https://issues.jboss.org/browse/DROOLS-1590 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 6.5.0.Final > Reporter: GaoShengwei GaoShengwei > Assignee: Mario Fusco > Attachments: BaiduHi_2017-5-31_18-1-18.png, BaiduHi_2017-5-31_18-2-54.png > > > I am using drools 6.5.0 Final. When I run sample code of section "starting a ruleflow from a rule" in documentation (https://nheron.gitbooks.io/droolsonboarding/content/gettingStarted/lesson...), the output sequence is different from the screenshot. > But when I switched to drools version to 6.4.0 Final, the output sequence was extactly same with screenshot. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ELY-1215) Elytron sasl-authentication-factory does not offer mechanisms in configured order

by Ondrej Lukas (JIRA)

Ondrej Lukas created ELY-1215: --------------------------------- Summary: Elytron sasl-authentication-factory does not offer mechanisms in configured order Key: ELY-1215 URL: https://issues.jboss.org/browse/ELY-1215 Project: WildFly Elytron Issue Type: Bug Reporter: Ondrej Lukas Assignee: Darran Lofthouse Priority: Critical Attachments: wireshark.png Application server does not offer SASL mechanisms in order defined in Elytron sasl-authentication-factory. See Steps to Reproduce for more details. Screenshot from wireshark 'follow TCP stream' is attached. {{JBOSS-LOCAL-USER}} is offered before {{DIGEST-MD5}}. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ELY-1215) Elytron sasl-authentication-factory does not offer mechanisms in configured order

by Ondrej Lukas (JIRA)

[ https://issues.jboss.org/browse/ELY-1215?page=com.atlassian.jira.plugin.s... ] Ondrej Lukas updated ELY-1215: ------------------------------ Attachment: wireshark.png > Elytron sasl-authentication-factory does not offer mechanisms in configured order > --------------------------------------------------------------------------------- > > Key: ELY-1215 > URL: https://issues.jboss.org/browse/ELY-1215 > Project: WildFly Elytron > Issue Type: Bug > Affects Versions: 1.1.0.Beta47 > Reporter: Ondrej Lukas > Assignee: Darran Lofthouse > Priority: Critical > Attachments: wireshark.png > > > Application server does not offer SASL mechanisms in order defined in Elytron sasl-authentication-factory. See Steps to Reproduce for more details. > Screenshot from wireshark 'follow TCP stream' is attached. {{JBOSS-LOCAL-USER}} is offered before {{DIGEST-MD5}}. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira June 2017