March 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-13031) EAP quickstart 'messaging-clustering-singleton' shows errors after import

by Zbyněk Červinka (Jira)

[ https://issues.redhat.com/browse/WFLY-13031?page=com.atlassian.jira.plugi... ] Zbyněk Červinka updated WFLY-13031: ----------------------------------- Affects Version/s: 18.0.1.Final > EAP quickstart 'messaging-clustering-singleton' shows errors after import > ------------------------------------------------------------------------- > > Key: WFLY-13031 > URL: https://issues.redhat.com/browse/WFLY-13031 > Project: WildFly > Issue Type: Bug > Components: Quickstarts > Affects Versions: 18.0.1.Final > Reporter: Zbyněk Červinka > Assignee: Parul Sharma > Priority: Major > Fix For: 19.0.0.Beta2 > > Attachments: Problems view.png, Project Explorer.png, jboss-ejb3.xml file.png > > > h1. EAP quickstart 'messaging-clustering-singleton' shows 3 errors in the jboss-ejb3.xml file after import: > * Referenced file contains errors (jar:file:/Applications/codereadystudio-eap-8/studio/codereadystudio.app/Contents/Eclipse/plugins/org.jboss.tools.as.catalog_3.7.0.v20190624-1620.jar!/schema/xsd/jboss-ejb-delivery-active_1_1.xsd). For more information, right click on the message in the Problems View and select "Show Details..." > * Referenced file contains errors (jar:file:/Applications/codereadystudio-eap-8/studio/codereadystudio.app/Contents/Eclipse/plugins/org.jboss.tools.as.catalog_3.7.0.v20190624-1620.jar!/schema/xsd/jboss-ejb3-2_0.xsd). For more information, right click on the message in the Problems View and select "Show Details..." > * Referenced file contains errors (jar:file:/Applications/codereadystudio-eap-8/studio/codereadystudio.app/Contents/Eclipse/plugins/org.jboss.tools.as.catalog_3.7.0.v20190624-1620.jar!/schema/xsd/jboss-ejb3-spec-2_0.xsd). For more information, right click on the message in the Problems View and select "Show Details..." -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5135) Drools Setup › Exception Handling in Drools Rule Condition

by Bishnu Shankar Pandey (Jira)

[ https://issues.redhat.com/browse/DROOLS-5135?page=com.atlassian.jira.plug... ] Bishnu Shankar Pandey updated DROOLS-5135: ------------------------------------------ Stackoverflow ID: https://stackoverflow.com/users/7726319/prog-g (was: Prog_G) > Drools Setup › Exception Handling in Drools Rule Condition > ----------------------------------------------------------- > > Key: DROOLS-5135 > URL: https://issues.redhat.com/browse/DROOLS-5135 > Project: Drools > Issue Type: Bug > Components: Guided Rule Editor > Affects Versions: 7.15.0.Final > Reporter: Bishnu Shankar Pandey > Assignee: Michael Anstis > Priority: Major > > How can we do rule wise exception handling in the drools rule condition? My scenario is how to handle scenarios when the schema of an event changes. > For example, let's say Initially I have an event that has 5 members namely name,num1,num2,num3,num4. I started creating rules for the event and the rule engine is running for some time. After that let's assume there is a scenario in which one of the class members (say num4) is removed from the event because of some reason. Now what I can do now is to change the Event class, but all the rules associated with that member will give me exceptions. The exceptions will also affect other rules which can run with the current data. Is there any way to handle exception in rule condition for specific rule and restrict it to disturb the independent rules. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5135) Drools Setup › Exception Handling in Drools Rule Condition

by Bishnu Shankar Pandey (Jira)

Bishnu Shankar Pandey created DROOLS-5135: --------------------------------------------- Summary: Drools Setup › Exception Handling in Drools Rule Condition Key: DROOLS-5135 URL: https://issues.redhat.com/browse/DROOLS-5135 Project: Drools Issue Type: Bug Components: Guided Rule Editor Affects Versions: 7.15.0.Final Reporter: Bishnu Shankar Pandey Assignee: Michael Anstis How can we do rule wise exception handling in the drools rule condition? My scenario is how to handle scenarios when the schema of an event changes. For example, let's say Initially I have an event that has 5 members namely name,num1,num2,num3,num4. I started creating rules for the event and the rule engine is running for some time. After that let's assume there is a scenario in which one of the class members (say num4) is removed from the event because of some reason. Now what I can do now is to change the Event class, but all the rules associated with that member will give me exceptions. The exceptions will also affect other rules which can run with the current data. Is there any way to handle exception in rule condition for specific rule and restrict it to disturb the independent rules. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5135) Drools Setup › Exception Handling in Drools Rule Condition

by Bishnu Shankar Pandey (Jira)

[ https://issues.redhat.com/browse/DROOLS-5135?page=com.atlassian.jira.plug... ] Bishnu Shankar Pandey updated DROOLS-5135: ------------------------------------------ Stackoverflow ID: Prog_G > Drools Setup › Exception Handling in Drools Rule Condition > ----------------------------------------------------------- > > Key: DROOLS-5135 > URL: https://issues.redhat.com/browse/DROOLS-5135 > Project: Drools > Issue Type: Bug > Components: Guided Rule Editor > Affects Versions: 7.15.0.Final > Reporter: Bishnu Shankar Pandey > Assignee: Michael Anstis > Priority: Major > > How can we do rule wise exception handling in the drools rule condition? My scenario is how to handle scenarios when the schema of an event changes. > For example, let's say Initially I have an event that has 5 members namely name,num1,num2,num3,num4. I started creating rules for the event and the rule engine is running for some time. After that let's assume there is a scenario in which one of the class members (say num4) is removed from the event because of some reason. Now what I can do now is to change the Event class, but all the rules associated with that member will give me exceptions. The exceptions will also affect other rules which can run with the current data. Is there any way to handle exception in rule condition for specific rule and restrict it to disturb the independent rules. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4868) Introduce aliases for standard configuration files

by Rostislav Svoboda (Jira)

Rostislav Svoboda created WFCORE-4868: ----------------------------------------- Summary: Introduce aliases for standard configuration files Key: WFCORE-4868 URL: https://issues.redhat.com/browse/WFCORE-4868 Project: WildFly Core Issue Type: Feature Request Reporter: Rostislav Svoboda Assignee: Jeff Mesnil Introduce aliases for standard configuration files Typing `./standalone.sh -c standalone-microprofile.xml` is so tedious Aliases for standard configs, e.g. `./standalone.sh -c mp`, would be a nice way to avoid typing long configs names. The idea comes from https://twitter.com/r_svoboda/status/1236391151483211779 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4867) Highlight the config name in start message

by Rostislav Svoboda (Jira)

[ https://issues.redhat.com/browse/WFCORE-4867?page=com.atlassian.jira.plug... ] Rostislav Svoboda commented on WFCORE-4867: ------------------------------------------- [~msvehla] fyi > Highlight the config name in start message > ------------------------------------------ > > Key: WFCORE-4867 > URL: https://issues.redhat.com/browse/WFCORE-4867 > Project: WildFly Core > Issue Type: Enhancement > Reporter: Rostislav Svoboda > Assignee: Jeff Mesnil > Priority: Major > > Highlight the config name in start message. > Config name could be highlighted > - during the beginning of the boot in {{JBoss Bootstrap Environment}} > - at the end of the boot procedure in the {{started in ...}} message > - anywhere else > The idea comes from https://twitter.com/r_svoboda/status/1236391151483211779 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4868) Introduce aliases for standard configuration files

by Rostislav Svoboda (Jira)

[ https://issues.redhat.com/browse/WFCORE-4868?page=com.atlassian.jira.plug... ] Rostislav Svoboda commented on WFCORE-4868: ------------------------------------------- [~msvehla] fyi > Introduce aliases for standard configuration files > -------------------------------------------------- > > Key: WFCORE-4868 > URL: https://issues.redhat.com/browse/WFCORE-4868 > Project: WildFly Core > Issue Type: Feature Request > Reporter: Rostislav Svoboda > Assignee: Jeff Mesnil > Priority: Major > > Introduce aliases for standard configuration files > Typing `./standalone.sh -c standalone-microprofile.xml` is so tedious > Aliases for standard configs, e.g. `./standalone.sh -c mp`, would be a nice way to avoid typing long configs names. > The idea comes from https://twitter.com/r_svoboda/status/1236391151483211779 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4867) Highlight the config name in start message

by Rostislav Svoboda (Jira)

Rostislav Svoboda created WFCORE-4867: ----------------------------------------- Summary: Highlight the config name in start message Key: WFCORE-4867 URL: https://issues.redhat.com/browse/WFCORE-4867 Project: WildFly Core Issue Type: Enhancement Reporter: Rostislav Svoboda Assignee: Jeff Mesnil Highlight the config name in start message. Config name could be highlighted - during the beginning of the boot in {{JBoss Bootstrap Environment}} - at the end of the boot procedure in the {{started in ...}} message - anywhere else The idea comes from https://twitter.com/r_svoboda/status/1236391151483211779 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13212) Boot messages related to activation of MP subsystems are inconsistent

by Rostislav Svoboda (Jira)

[ https://issues.redhat.com/browse/WFLY-13212?page=com.atlassian.jira.plugi... ] Rostislav Svoboda commented on WFLY-13212: ------------------------------------------ [~msvehla] / [~mnovak] fyi, possible JBEAP candidate. > Boot messages related to activation of MP subsystems are inconsistent > --------------------------------------------------------------------- > > Key: WFLY-13212 > URL: https://issues.redhat.com/browse/WFLY-13212 > Project: WildFly > Issue Type: Bug > Components: MP Config, MP Fault Tolerance, MP JWT, MP OpenTracing > Affects Versions: 19.0.0.Beta3 > Reporter: Rostislav Svoboda > Assignee: Jeff Mesnil > Priority: Major > > Boot messages related to activation of MP subsystems are inconsistent in package names and used wording. > - MP Config and MP JWT use {{_private}} package, the remaining do not. > - MP Config and MP JWT say {{Activating WildFly MicroProfile}}, the majority of specs says {{Activating Eclipse MicroProfile }} > - MP FT and MP OT say {{Activating MicroProfile}}, the majority of specs says {{Activating Eclipse MicroProfile }} > - MP FT "Activating ..." message ends {{subsystem.}} but should be in sync with others - {{Subsystem}} - no comma at the end, upper case for the first letter > Packages and "Activating ..." messages should sync. > {code} > 21:43:44,506 INFO [org.wildfly.extension.microprofile.config.smallrye._private] (ServerService Thread Pool -- 48) WFLYCONF0001: Activating WildFly MicroProfile Config Subsystem > 21:43:44,527 INFO [org.wildfly.extension.microprofile.jwt.smallrye._private] (ServerService Thread Pool -- 51) WFLYJWT0001: Activating WildFly MicroProfile JWT Subsystem > {code} > {code} > 21:43:44,523 INFO [org.wildfly.extension.microprofile.openapi.smallrye] (ServerService Thread Pool -- 53) WFLYMPOAI0001: Activating Eclipse MicroProfile OpenAPI Subsystem > 21:43:44,531 INFO [org.wildfly.extension.microprofile.health.smallrye] (ServerService Thread Pool -- 50) WFLYHEALTH0001: Activating Eclipse MicroProfile Health Subsystem > 21:43:44,533 INFO [org.wildfly.extension.microprofile.metrics.smallrye] (ServerService Thread Pool -- 52) WFLYMETRICS0001: Activating Eclipse MicroProfile Metrics Subsystem > 21:43:44,531 INFO [org.wildfly.extension.microprofile.faulttolerance] (ServerService Thread Pool -- 49) WFLYMPFTEXT0001: Activating MicroProfile Fault Tolerance subsystem. > {code} > CC [~brian.stansberry] / [~maeste] -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13212) Boot messages related to activation of MP subsystems are inconsistent

by Rostislav Svoboda (Jira)

Rostislav Svoboda created WFLY-13212: ---------------------------------------- Summary: Boot messages related to activation of MP subsystems are inconsistent Key: WFLY-13212 URL: https://issues.redhat.com/browse/WFLY-13212 Project: WildFly Issue Type: Bug Components: MP Config, MP Fault Tolerance, MP JWT, MP OpenTracing Affects Versions: 19.0.0.Beta3 Reporter: Rostislav Svoboda Assignee: Jeff Mesnil Boot messages related to activation of MP subsystems are inconsistent in package names and used wording. - MP Config and MP JWT use {{_private}} package, the remaining do not. - MP Config and MP JWT say {{Activating WildFly MicroProfile}}, the majority of specs says {{Activating Eclipse MicroProfile }} - MP FT and MP OT say {{Activating MicroProfile}}, the majority of specs says {{Activating Eclipse MicroProfile }} - MP FT "Activating ..." message ends {{subsystem.}} but should be in sync with others - {{Subsystem}} - no comma at the end, upper case for the first letter Packages and "Activating ..." messages should sync. {code} 21:43:44,506 INFO [org.wildfly.extension.microprofile.config.smallrye._private] (ServerService Thread Pool -- 48) WFLYCONF0001: Activating WildFly MicroProfile Config Subsystem 21:43:44,527 INFO [org.wildfly.extension.microprofile.jwt.smallrye._private] (ServerService Thread Pool -- 51) WFLYJWT0001: Activating WildFly MicroProfile JWT Subsystem {code} {code} 21:43:44,523 INFO [org.wildfly.extension.microprofile.openapi.smallrye] (ServerService Thread Pool -- 53) WFLYMPOAI0001: Activating Eclipse MicroProfile OpenAPI Subsystem 21:43:44,531 INFO [org.wildfly.extension.microprofile.health.smallrye] (ServerService Thread Pool -- 50) WFLYHEALTH0001: Activating Eclipse MicroProfile Health Subsystem 21:43:44,533 INFO [org.wildfly.extension.microprofile.metrics.smallrye] (ServerService Thread Pool -- 52) WFLYMETRICS0001: Activating Eclipse MicroProfile Metrics Subsystem 21:43:44,531 INFO [org.wildfly.extension.microprofile.faulttolerance] (ServerService Thread Pool -- 49) WFLYMPFTEXT0001: Activating MicroProfile Fault Tolerance subsystem. {code} CC [~brian.stansberry] / [~maeste] -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 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 March 2020