September 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFWIP-333) Bootable JAR - Cloud - Remove https listener and self signed certificate

by Martin Choma (Jira)

[ https://issues.redhat.com/browse/WFWIP-333?page=com.atlassian.jira.plugin... ] Martin Choma closed WFWIP-333. ------------------------------ I can verify issue was resolved in wildfly-jar-maven-plugin version Beta6. > Bootable JAR - Cloud - Remove https listener and self signed certificate > ------------------------------------------------------------------------ > > Key: WFWIP-333 > URL: https://issues.redhat.com/browse/WFWIP-333 > Project: WildFly WIP > Issue Type: Feature Request > Reporter: Jean Francois Denise > Assignee: Jean Francois Denise > Priority: Major > > In a cloud context, having https listener and generation of self signed certificate is not recommended. When cloud is enabled, https listener and ssl identity will be removed. This does align with XP 1.0 S2i builder image configuration. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-329) Bootable JAR - Cloud - Disable management console in mgmt http-interface

by Martin Choma (Jira)

[ https://issues.redhat.com/browse/WFWIP-329?page=com.atlassian.jira.plugin... ] Martin Choma closed WFWIP-329. ------------------------------ I can verify issue was resolved in wildfly-jar-maven-plugin version Beta6. > Bootable JAR - Cloud - Disable management console in mgmt http-interface > ------------------------------------------------------------------------ > > Key: WFWIP-329 > URL: https://issues.redhat.com/browse/WFWIP-329 > Project: WildFly WIP > Issue Type: Bug > Reporter: Jean Francois Denise > Assignee: Jean Francois Denise > Priority: Major > > The console is disabled for config run in EAP/XP s2i builder image. It makes sense to apply the same change for Bootable JAR when cloud is enabled. So a CLI script will run to disable it (if management interface exists): > /core-service=management/management-interface=http-interface:write-attribute(name=console-enabled,value=false) > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12586) Duplicated classes in testsuite, content slightly differs in some cases

by Parul Sharma (Jira)

[ https://issues.redhat.com/browse/WFLY-12586?page=com.atlassian.jira.plugi... ] Parul Sharma commented on WFLY-12586: ------------------------------------- As per my analysis, only WebInfLib.java is a duplicate class, other classes are running in different parts of the test suite with code changes. I think we should not consider as duplicate classes. > Duplicated classes in testsuite, content slightly differs in some cases > ----------------------------------------------------------------------- > > Key: WFLY-12586 > URL: https://issues.redhat.com/browse/WFLY-12586 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Reporter: Rostislav Svoboda > Assignee: Parul Sharma > Priority: Major > > There are duplicated classes in testsuite, content slightly differs in some cases > {code} > for i in `find . | grep '.*src.*\.java$' | sed "s,.*src/main/java/,,g" | sed "s,.*src/test/java/,,g" | sort | uniq -c | sort -n | grep "2 " | cut -d" " -f 5-`; do echo "$i"; find . | grep "$i"; echo ""; done > org/jboss/as/test/integration/deployment/classloading/war/WebInfLibClass.java > ./integration/web/src/test/java/org/jboss/as/test/integration/deployment/classloading/war/WebInfLibClass.java > ./integration/basic/src/test/java/org/jboss/as/test/integration/deployment/classloading/war/WebInfLibClass.java > org/jboss/as/test/integration/deployment/deploymentoverlay/DeploymentOverlayTestCase.java > ./integration/web/src/test/java/org/jboss/as/test/integration/deployment/deploymentoverlay/DeploymentOverlayTestCase.java > ./integration/basic/src/test/java/org/jboss/as/test/integration/deployment/deploymentoverlay/DeploymentOverlayTestCase.java > org/jboss/as/test/integration/ejb/security/EjbSecurityDomainSetup.java > ./integration/basic/src/test/java/org/jboss/as/test/integration/ejb/security/EjbSecurityDomainSetup.java > ./integration/ws/src/test/java/org/jboss/as/test/integration/ejb/security/EjbSecurityDomainSetup.java > org/jboss/as/test/integration/web/security/SecuredServlet.java > ./integration/web/src/test/java/org/jboss/as/test/integration/web/security/SecuredServlet.java > ./integration/basic/src/test/java/org/jboss/as/test/integration/web/security/SecuredServlet.java > org/jboss/as/test/integration/web/security/WebSimpleRoleMappingSecurityDomainSetup.java > ./integration/web/src/test/java/org/jboss/as/test/integration/web/security/WebSimpleRoleMappingSecurityDomainSetup.java > ./integration/basic/src/test/java/org/jboss/as/test/integration/web/security/WebSimpleRoleMappingSecurityDomainSetup.java > org/jboss/as/test/integration/web/security/WebTestsSecurityDomainSetup.java > ./integration/web/src/test/java/org/jboss/as/test/integration/web/security/WebTestsSecurityDomainSetup.java > ./integration/basic/src/test/java/org/jboss/as/test/integration/web/security/WebTestsSecurityDomainSetup.java > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-347) Bootable JAR - No context is registered on server if packaging is left on default

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/WFWIP-347?page=com.atlassian.jira.plugin... ] Darran Lofthouse commented on WFWIP-347: ---------------------------------------- +1 on the documentation. > Bootable JAR - No context is registered on server if packaging is left on default > --------------------------------------------------------------------------------- > > Key: WFWIP-347 > URL: https://issues.redhat.com/browse/WFWIP-347 > Project: WildFly WIP > Issue Type: Bug > Reporter: Jan Kasik > Assignee: Jean Francois Denise > Priority: Major > > When default packaging for app is selected (meaning no {{<packaging>}}), the app deploys but no web context is registered. {{war}} must be set as value of {{<packaging>}} in order to register web context. > Since setting of packaging is not a part of plugin configuration I find it confusing. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-347) Bootable JAR - No context is registered on server if packaging is left on default

by Jan Kasik (Jira)

[ https://issues.redhat.com/browse/WFWIP-347?page=com.atlassian.jira.plugin... ] Jan Kasik resolved WFWIP-347. ----------------------------- Resolution: Explained > Bootable JAR - No context is registered on server if packaging is left on default > --------------------------------------------------------------------------------- > > Key: WFWIP-347 > URL: https://issues.redhat.com/browse/WFWIP-347 > Project: WildFly WIP > Issue Type: Bug > Reporter: Jan Kasik > Assignee: Jean Francois Denise > Priority: Major > > When default packaging for app is selected (meaning no {{<packaging>}}), the app deploys but no web context is registered. {{war}} must be set as value of {{<packaging>}} in order to register web context. > Since setting of packaging is not a part of plugin configuration I find it confusing. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-347) Bootable JAR - No context is registered on server if packaging is left on default

by Jan Kasik (Jira)

[ https://issues.redhat.com/browse/WFWIP-347?page=com.atlassian.jira.plugin... ] Jan Kasik commented on WFWIP-347: --------------------------------- [~jdenise][~dlofthouse] Thanks for confirming this. I cloned this issue to JBEAP project since I think there should be at least be a note that packaging has to be set. > Bootable JAR - No context is registered on server if packaging is left on default > --------------------------------------------------------------------------------- > > Key: WFWIP-347 > URL: https://issues.redhat.com/browse/WFWIP-347 > Project: WildFly WIP > Issue Type: Bug > Reporter: Jan Kasik > Assignee: Jean Francois Denise > Priority: Major > > When default packaging for app is selected (meaning no {{<packaging>}}), the app deploys but no web context is registered. {{war}} must be set as value of {{<packaging>}} in order to register web context. > Since setting of packaging is not a part of plugin configuration I find it confusing. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (AG-148) Run all tests in CI

by Luis Barreiro (Jira)

[ https://issues.redhat.com/browse/AG-148?page=com.atlassian.jira.plugin.sy... ] Luis Barreiro resolved AG-148. ------------------------------ Resolution: Done > Run all tests in CI > -------------------- > > Key: AG-148 > URL: https://issues.redhat.com/browse/AG-148 > Project: Agroal > Issue Type: Task > Components: build > Affects Versions: 1.8 > Reporter: Luis Barreiro > Assignee: Luis Barreiro > Priority: Minor > Fix For: 1.9 > > > Currently, some groups don't run by default -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5633) 【looking for help】I want to load class from string instead of from source, but it always failed

by zhang shuai (Jira)

zhang shuai created DROOLS-5633: ----------------------------------- Summary: 【looking for help】I want to load class from string instead of from source, but it always failed Key: DROOLS-5633 URL: https://issues.redhat.com/browse/DROOLS-5633 Project: Drools Issue Type: Feature Request Reporter: zhang shuai Assignee: Mario Fusco I want to dynamically load rules(drl files) and java classes. And now I can load drl by the below way. But I dont know how to dynamically load java classes by String type. For example: I have a drl which is including class Person, so the Person must be existed in my project. However my service is running, I can not restart the serbice, and I have Person class in my database as String type. How can I load the String Person to kiebase? please help me, thank you very much! {code:java} public static void loadRulesFromStr(InternalKnowledgeBase kBase, List<String> drls) { KnowledgeBuilderConfiguration kbc = KnowledgeBuilderFactory.newKnowledgeBuilderConfiguration(); KnowledgeBuilder kBuilder = KnowledgeBuilderFactory.newKnowledgeBuilder(kbc); for (String drl : drls) { kBuilder.add(ResourceFactory.newByteArrayResource(drl.getBytes()), ResourceType.DRL); } if (kBuilder.hasErrors()) { System.out.println(kBuilder.getErrors().toString()); } kBase.addPackages(kBuilder.getKnowledgePackages()); } {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (AG-148) Run all tests in CI

by Luis Barreiro (Jira)

Luis Barreiro created AG-148: -------------------------------- Summary: Run all tests in CI Key: AG-148 URL: https://issues.redhat.com/browse/AG-148 Project: Agroal Issue Type: Task Components: build Affects Versions: 1.8 Reporter: Luis Barreiro Assignee: Luis Barreiro Fix For: 1.9 Currently, some groups don't run by default -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ELY-2020) Revisit code style for tool / CredentialStoreCommand

by Darran Lofthouse (Jira)

Darran Lofthouse created ELY-2020: ------------------------------------- Summary: Revisit code style for tool / CredentialStoreCommand Key: ELY-2020 URL: https://issues.redhat.com/browse/ELY-2020 Project: WildFly Elytron Issue Type: Task Components: Command-Line Tool Affects Versions: 1.13.0.CR4 Reporter: Darran Lofthouse Assignee: Darran Lofthouse This should probably wait until after ELY-1842 as refactoring before will cause more problems. Working on ELY-1842 another engineer has also worked on an RFE for different reasons to adjust the credential store, the current code has a long method building up with the options for the command line - if multiple engineers work on this code it leads to conflicts easily but is also hard to unravel to correct the conflicts. As the scope of CredentialStoreCommand has expanded since it's original implementation which was very tightly constrained we probably need to break this up into more logical chunks, also many variables just have a very short name which keeps the code concise but if you have not bee in the code for a while it is hard to see the purpose of each variable to we should expand the variable names to be more meaningful. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 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 September 2020