December 2020 - jboss-jira - Jboss List Archives

[Red Hat JIRA] (WFLY-14132) jboss-ejb3.xml is ignored for exploded deployments

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-14132?page=com.atlassian.jira.plugi... ] Brian Stansberry reassigned WFLY-14132: --------------------------------------- Assignee: Cheng Fang (was: Brian Stansberry) > jboss-ejb3.xml is ignored for exploded deployments > -------------------------------------------------- > > Key: WFLY-14132 > URL: https://issues.redhat.com/browse/WFLY-14132 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 14.0.1.Final, JBoss AS7 7.1.1.Final, 21.0.1.Final > Reporter: Jan-Willem Gmelig Meyling > Assignee: Cheng Fang > Priority: Major > Labels: ejb-jar.xml, jboss-ejb3.xml > > {{EjbJarParsingDeploymentUnitProcessor}} distinguishes between a WAR and JAR deployment based on the file extension of the name of the deployment root. For exploded deployments however, this deployment root may be a folder without any file extension. As a result the logic fails to detect either a JAR or WAR file and the {{ejb-jar.xml}} and {{jboss-ejb3.xml}} files are ignored. A better way could be to determine the extension from the name of {{DeploymentUnit}} instead. > Code from: [https://github.com/wildfly/wildfly/blob/master/ejb3/src/main/java/org/jbo...] > {code:java} > private static VirtualFile getDescriptor(final VirtualFile deploymentRoot, final String descriptorName) { > // Locate the descriptor > final VirtualFile descriptor; > // EJB 3.1 FR 20.4 Enterprise Beans Packaged in a .war > if (isWar(deploymentRoot)) { > // it's a .war file, so look for the ejb-jar.xml in WEB-INF > descriptor = deploymentRoot.getChild(WEB_INF + "/" + descriptorName); > } else if (deploymentRoot.getName().toLowerCase(Locale.ENGLISH).endsWith(JAR_FILE_EXTENSION)) { > descriptor = deploymentRoot.getChild(META_INF + "/" + descriptorName); > } else { > // neither a .jar nor a .war. Return > return null; > } > if (descriptor == null || !descriptor.exists()) { > // no descriptor found, nothing to do! > return null; > } > return descriptor; > } > {code} > > I encountered this issue on WildFly 14.0.1.Final, but the code is also present in the current master and goes back to versions as early as 7.1. -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 5 months

1
0
0 / 0

[Red Hat JIRA] (ELY-2042) ElytronXMLParser is not configuring maximum-cert-path in X509RevocationTrustManager

by Sonia Zaldana (Jira)

[ https://issues.redhat.com/browse/ELY-2042?page=com.atlassian.jira.plugin.... ] Sonia Zaldana updated ELY-2042: ------------------------------- Git Pull Request: https://github.com/wildfly-security/wildfly-elytron/pull/1468 > ElytronXMLParser is not configuring maximum-cert-path in X509RevocationTrustManager > ----------------------------------------------------------------------------------- > > Key: ELY-2042 > URL: https://issues.redhat.com/browse/ELY-2042 > Project: WildFly Elytron > Issue Type: Bug > Reporter: Sonia Zaldana > Assignee: Sonia Zaldana > Priority: Major > > The ElytronXMLParser is parsing the maximum-cert-path attribute corresponding to a trust-manager resource, but it is not propagating that value to the X509RevocationTrustManager. As a result, a trust manager configured on the client side always has the default value of 5. -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 5 months

1
0
0 / 0

[Red Hat JIRA] (JBJCA-1410) Oracle UCP support: notify OracleConnection about begin and end of the requestion

by Tomasz Adamski (Jira)

[ https://issues.redhat.com/browse/JBJCA-1410?page=com.atlassian.jira.plugi... ] Tomasz Adamski resolved JBJCA-1410. ----------------------------------- Resolution: Done > Oracle UCP support: notify OracleConnection about begin and end of the requestion > --------------------------------------------------------------------------------- > > Key: JBJCA-1410 > URL: https://issues.redhat.com/browse/JBJCA-1410 > Project: IronJacamar > Issue Type: Feature Request > Reporter: Tomasz Adamski > Assignee: Tomasz Adamski > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 5 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14136) Activate MP Rest Client TCK with -Dts.ee9 profile; resolve failures

by Brian Stansberry (Jira)

Brian Stansberry created WFLY-14136: --------------------------------------- Summary: Activate MP Rest Client TCK with -Dts.ee9 profile; resolve failures Key: WFLY-14136 URL: https://issues.redhat.com/browse/WFLY-14136 Project: WildFly Issue Type: Task Components: MP REST Client Reporter: Brian Stansberry Assignee: Alessio Soldano When the ee-9 modules were added I thought I had enabled the MP Rest Client TCK when the -Dts.ee9 profile was executed. It turns out I had not. The profile does the various set up work but the default-test surefire execution was not enabled, so the tests aren't actually run. I discovered this when working on WFLY-14049. I believe 16 test will fail if it is enabled, so part of this task is to sort out what that's about. -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 5 months

1
0
0 / 0

[Red Hat JIRA] (WFCORE-5200) Include the wildfly-openssl ppc64le binding

by Farah Juma (Jira)

[ https://issues.redhat.com/browse/WFCORE-5200?page=com.atlassian.jira.plug... ] Farah Juma resolved WFCORE-5200. -------------------------------- Resolution: Rejected > Include the wildfly-openssl ppc64le binding > ------------------------------------------- > > Key: WFCORE-5200 > URL: https://issues.redhat.com/browse/WFCORE-5200 > Project: WildFly Core > Issue Type: Enhancement > Components: Build System, Security > Reporter: Vladimir Dosoudil > Assignee: Farah Juma > Priority: Major > > The wildfly-openssl project source code include ppc64le bindings; we should include them. > https://github.com/wildfly-security/wildfly-openssl-natives/tree/master/l... > The code was there for a while (at least since 1.0.8 release) but it doesn't look like that variant was built and pushed to nexus: > https://repository.jboss.org/org/wildfly/openssl/ -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 5 months

1
0
0 / 0

[Red Hat JIRA] (DROOLS-5867) Update ApplyPmmlModelCommand to manage both PMML implementations

by Gabriele Cardosi (Jira)

Gabriele Cardosi created DROOLS-5867: ---------------------------------------- Summary: Update ApplyPmmlModelCommand to manage both PMML implementations Key: DROOLS-5867 URL: https://issues.redhat.com/browse/DROOLS-5867 Project: Drools Issue Type: Task Reporter: Gabriele Cardosi Assignee: Gabriele Cardosi Currently, ApplyPmmlModelCommand (inside drools) invoke directly the legacy PMML delegate (ApplyPmmlModelCommandExecutorImpl). # code a PMML-trusty implementation of ApplyPmmlModelCommandExecutor (needed ?) # modify ApplyPmmlModelCommand to switch between implementations. -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 5 months

1
0
0 / 0

[Red Hat JIRA] (DROOLS-5862) Enable new impl by default

by Gabriele Cardosi (Jira)

Gabriele Cardosi created DROOLS-5862: ---------------------------------------- Summary: Enable new impl by default Key: DROOLS-5862 URL: https://issues.redhat.com/browse/DROOLS-5862 Project: Drools Issue Type: Feature Request Reporter: Gabriele Cardosi Assignee: Gabriele Cardosi Inside PMMLAssemblerService(s) switch default values (legacy/new) -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 5 months

1
0
0 / 0

[Red Hat JIRA] (DROOLS-5871) DrlDumper does not generate the accumulate import

by Hiroko Miura (Jira)

Hiroko Miura created DROOLS-5871: ------------------------------------ Summary: DrlDumper does not generate the accumulate import Key: DROOLS-5871 URL: https://issues.redhat.com/browse/DROOLS-5871 Project: Drools Issue Type: Bug Components: core engine Affects Versions: 7.44.0.Final, 7.46.0.Final Reporter: Hiroko Miura Assignee: Mario Fusco Attachments: import-accumulate-test.zip DrlDumper is not printing out the accumulate import. Here is an example code of PackageDescrBuilder. {noformat} PackageDescr packageDescr = DescrFactory.newPackage().name("examples.drools") .newImport().target("java.math.BigDecimal").end() .newAccumulateImport().target("examples.drools.accumulate.OriginalFunction").functionName("originalFunction").end() .newRule().name("Test Rule") .lhs() .accumulate() .source().pattern().type("TargetFact").id("$target", false) .end() .end() .function("originalFunction", "$accumulateResult", false, "$target.hoge") .constraint("true") .end() .end() .rhs("System.out.println($accumulateResult);") .end() .end().getDescr(); String drl = new DrlDumper().dump(packageDescr); {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 5 months

1
0
0 / 0

[Red Hat JIRA] (DROOLS-5869) Running tests should not affect incremental build

by Toni Rikkola (Jira)

[ https://issues.redhat.com/browse/DROOLS-5869?page=com.atlassian.jira.plug... ] Toni Rikkola moved RHDM-1515 to DROOLS-5869: -------------------------------------------- Project: Drools (was: Red Hat Decision Manager) Key: DROOLS-5869 (was: RHDM-1515) Workflow: GIT Pull Request workflow (was: CDW with docs v1) Docs QE Status: NEW Component/s: core engine (was: Decision Central) Affects Build: (was: CR1) Affects Version/s: (was: 7.9.1.GA) QE Status: NEW > Running tests should not affect incremental build > ------------------------------------------------- > > Key: DROOLS-5869 > URL: https://issues.redhat.com/browse/DROOLS-5869 > Project: Drools > Issue Type: Bug > Components: core engine > Reporter: Tomas David > Assignee: Toni Rikkola > Priority: Major > Labels: drools-tools > > For a Scenario Simulation that tests DRL rule and facts having an enum property a seemingly class-loading issue occurs in Business Central. > The ultimate error is in the DRL file validation. Please see DROOLS-5458 for more details. -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 5 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14156) Remove MicroProfile REST Client from Wildfly ee

by Emmanuel Hugonnet (Jira)

[ https://issues.redhat.com/browse/WFLY-14156?page=com.atlassian.jira.plugi... ] Emmanuel Hugonnet moved EAP7-1590 to WFLY-14156: ------------------------------------------------ Project: WildFly (was: JBoss EAP Planning for version 7 and above) Key: WFLY-14156 (was: EAP7-1590) Issue Type: Feature Request (was: Requirement) Workflow: GIT Pull Request workflow (was: EAP Agile Workflow 2.0) Component/s: MP REST Client REST (was: MicroProfile) (was: REST) EAP PT Feature Implementation (FI): (was: TODO) Fix Version/s: (was: 7.4.0.Beta) EAP PT Pre-Checked (PC): (was: TODO) Target Release: (was: 7.4.0.GA) EAP PT Community Docs (CD): (was: TODO) EAP PT Product Docs (PD): (was: New) EAP PT Test Dev (TD): (was: TODO) EAP PT Docs Analysis (DA): (was: TODO) EAP PT Test Plan (TP): (was: TODO) EAP PT Analysis Document (AD): (was: TODO) > Remove MicroProfile REST Client from Wildfly ee > ----------------------------------------------- > > Key: WFLY-14156 > URL: https://issues.redhat.com/browse/WFLY-14156 > Project: WildFly > Issue Type: Feature Request > Components: MP REST Client, REST > Reporter: Emmanuel Hugonnet > Assignee: Emmanuel Hugonnet > Priority: Blocker > Labels: EAP-CD22 > > The MicroProfile REST Client functionalities are expected to be provided in EAP XP only. -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2020