April 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-4915) Tighten up the dependency tree of subsystem-test

by Brian Stansberry (Jira)

Brian Stansberry created WFCORE-4915: ---------------------------------------- Summary: Tighten up the dependency tree of subsystem-test Key: WFCORE-4915 URL: https://issues.redhat.com/browse/WFCORE-4915 Project: WildFly Core Issue Type: Task Components: Test Suite Reporter: Brian Stansberry Assignee: Brian Stansberry In general I'd like to tighten (aka eliminate) up the use of transitive dependencies when various WildFly and WildFly Core maven modules depend on each other. Things should be explicit so unwanted coupling cannot creep in. The subsystem-test module is important in this regard as pretty much all extension modules depend on it's pom. So I want it and its children and its direct dependencies to only depend on other wf core modules directly, no transitive deps allowed. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13361) Upgrade jboss-ejb-client to 4.0.32.Final

by Tomasz Adamski (Jira)

[ https://issues.redhat.com/browse/WFLY-13361?page=com.atlassian.jira.plugi... ] Tomasz Adamski reassigned WFLY-13361: ------------------------------------- Assignee: Tomasz Adamski (was: Brian Stansberry) > Upgrade jboss-ejb-client to 4.0.32.Final > ---------------------------------------- > > Key: WFLY-13361 > URL: https://issues.redhat.com/browse/WFLY-13361 > Project: WildFly > Issue Type: Component Upgrade > Reporter: Tomasz Adamski > Assignee: Tomasz Adamski > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4908) The write-attribute operation does not work on a hosts JVM resource

by James Perkins (Jira)

[ https://issues.redhat.com/browse/WFCORE-4908?page=com.atlassian.jira.plug... ] James Perkins commented on WFCORE-4908: --------------------------------------- [~jdenise] Oops you're correct are correct. I left off the {{value}} attribute. However it seems odd the command succeeds at all. It should fail with either an invalid attribute name and/or the missing value attribute. Also as [~soul2zimate] says I think the tab complete is a bit misleading as that's what I was relying too heavily on :) That is a separate issue though. > The write-attribute operation does not work on a hosts JVM resource > ------------------------------------------------------------------- > > Key: WFCORE-4908 > URL: https://issues.redhat.com/browse/WFCORE-4908 > Project: WildFly Core > Issue Type: Bug > Components: CLI, Management > Reporter: James Perkins > Assignee: Jeff Mesnil > Priority: Major > Labels: domain-mode > > Under a hosts server config, {{/host=master/server-config=server-one/}}, there is a {{jvm}} resource. On this resource the {{write-attribute}} operation does not work expected. > {code} > [domain@embedded /] /host=master/server-config=server-one/jvm=default:add > { > "outcome" => "success", > "result" => undefined, > "server-groups" => undefined > } > [domain@embedded /] /host=master/server-config=server-one/jvm=default:write-attribute(name=jvm-options["-Xlog:gc*:file=${jboss.domain.servers.dir}/server-two/log/gc.log"]) > { > "outcome" => "success", > "result" => undefined, > "server-groups" => undefined > } > [domain@embedded /] /host=master/server-config=server-one/jvm=default:read-resource > { > "outcome" => "success", > "result" => { > "agent-lib" => undefined, > "agent-path" => undefined, > "debug-enabled" => undefined, > "debug-options" => undefined, > "env-classpath-ignored" => undefined, > "environment-variables" => undefined, > "heap-size" => undefined, > "java-agent" => undefined, > "java-home" => undefined, > "jvm-options" => undefined, > "launch-command" => undefined, > "max-heap-size" => undefined, > "max-permgen-size" => undefined, > "permgen-size" => undefined, > "stack-size" => undefined, > "type" => undefined > } > } > {code} > As you can see from the above command does not update the {{jvm-options}}. However if you use the {{add-jvm-option}} operation that does work. It seems the {{write-attribute}} operation should also work. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4746) UX for DMN "quick test" tool

by Elizabeth Clayton (Jira)

[ https://issues.redhat.com/browse/DROOLS-4746?page=com.atlassian.jira.plug... ] Elizabeth Clayton commented on DROOLS-4746: ------------------------------------------- [~karreiro][~danielezonca][~tirelli] I updated the click-thru based on feedback from [~danielezonca]. Changes include: - Grouped input sections that are collapsible, with labels that present an icon to describe the node type. - Grouped input section labels that are hyperlinked and will navigate the user to the model, with the respective node properties panel open. - Open "inspect" panel via 3 means: Left-click select the table, right-click contextual menu on table header cells, toolbar button. - Changed "boxed expression" language in the panel title and tooltips to "Decision Logic" but needs input/review from [~stetson.robinson] or respective content specialist. Updated click-thru: https://marvelapp.com/7208d3a > UX for DMN "quick test" tool > ---------------------------- > > Key: DROOLS-4746 > URL: https://issues.redhat.com/browse/DROOLS-4746 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Elizabeth Clayton > Assignee: Elizabeth Clayton > Priority: Major > Labels: UX, UXTeam, drools-tools > Attachments: Screen Shot 2020-04-08 at 4.34.49 PM.png, Screen Shot 2020-04-08 at 5.01.51 PM.png, Screen Shot 2020-04-09 at 9.29.34 AM.png, decision-logic-2-2.png, decision-logic-3-2.png > > > As a DMN author, I'd like to probe the DMN model during the authoring phase without leaving the DMN Editor. Actually, it's really important to explore the DMN model to understand with values are required by the test. > When the user run the test he can get back the results of the DMN execution. > Moreover, it would be handy to add those input/output to an existing (or new) test scenario. > *Acceptance criteria* > Users are able to: > * Execute a single node boxed expression by providing node inputs (within the DMN editor.) > * Explore the DMN model and provide inputs necessary to run a scenario test. > * Obtain results (Expected) within the DMN editor once the test is run. > Notes: > * Try to dissociate this feature from the "test scenario" concept and think of this more as a partial execution. When we're thinking about the concept of a "test scenario", we think about input values and expected outputs... however, in this new component, users will be able to provide inputs and just check the current output. > * Out of scope: Saving or exporting the "quick test." -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13302) Add ARM64 versions for libartemis-native.so and libwfssl.so

by Farah Juma (Jira)

[ https://issues.redhat.com/browse/WFLY-13302?page=com.atlassian.jira.plugi... ] Farah Juma commented on WFLY-13302: ----------------------------------- WildFly OpenSSL does already have a [linux-aarch64|https://github.com/wildfly-security/wildfly-openssl/tree/ma...] module that can be used to build the aarch64 binary for libwfssl.so. Currently, for WildFly OpenSSL releases, we only perform native builds on Linux, Windows, Solaris, and Mac. I've created an issue to track getting the aarch64 binary included: https://issues.redhat.com/browse/WFSSL-32 > Add ARM64 versions for libartemis-native.so and libwfssl.so > ----------------------------------------------------------- > > Key: WFLY-13302 > URL: https://issues.redhat.com/browse/WFLY-13302 > Project: WildFly > Issue Type: Feature Request > Components: Build System > Affects Versions: 19.0.0.Final > Reporter: Martin Grigorov > Assignee: Farah Juma > Priority: Major > > Hello WildFly team, > I'd like to ask you to add arm64/aarch64 versions of the libartemis-native.so and libwfssl.so binaries to the release distribution. > The TGZ download from https://wildfly.org/downloads/ has the following .so files: > {code} > wildfly-19.0.0.Final $ find ./ -name "*.so" > ./modules/system/layers/base/org/apache/activemq/artemis/journal/main/lib/linux-i686/libartemis-native-32.so > ./modules/system/layers/base/org/apache/activemq/artemis/journal/main/lib/linux-x86_64/libartemis-native-64.so > ./modules/system/layers/base/org/wildfly/openssl/main/lib/linux-x86_64/libwfssl.so > ./modules/system/layers/base/org/wildfly/openssl/main/lib/linux-i386/libwfssl.so > ./modules/system/layers/base/org/wildfly/openssl/main/lib/solaris-x86_64/libwfssl.so > {code} > Since recently there is a TeamCity agent running on Ubuntu 18.04.4 ARM64: https://ci.wildfly.org/viewType.html?buildTypeId=WF_MasterLinuxArm64OpenJ911 > I guess it could be used to build those binaries too -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11316) Remove unused dependencies from org.jberet.jberet-core

by Ranabir Chakraborty (Jira)

[ https://issues.redhat.com/browse/WFLY-11316?page=com.atlassian.jira.plugi... ] Ranabir Chakraborty commented on WFLY-11316: -------------------------------------------- [~yersan] are you working on this issue? > Remove unused dependencies from org.jberet.jberet-core > ------------------------------------------------------ > > Key: WFLY-11316 > URL: https://issues.redhat.com/browse/WFLY-11316 > Project: WildFly > Issue Type: Bug > Components: Batch > Reporter: Yeray Borges Santana > Assignee: Yeray Borges Santana > Priority: Optional > > Analysis of org.jberet.jberet-core shows: > * org.jboss.jts is unused > * jberet only uses javax.enterprise.api, javax.inject.api, javax.annotation.api and javax.batch.api from javaee.api, maybe we could reduce the final size removing javaee.api and add only the required modules. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4914) (7.3.z) Updating mockserver to 5.9.0. Exclusion of dependency from xom.io7m

by Ilia Vassilev (Jira)

Ilia Vassilev created WFCORE-4914: ------------------------------------- Summary: (7.3.z) Updating mockserver to 5.9.0. Exclusion of dependency from xom.io7m Key: WFCORE-4914 URL: https://issues.redhat.com/browse/WFCORE-4914 Project: WildFly Core Issue Type: Task Reporter: Ilia Vassilev Assignee: Panagiotis Sotiropoulos Fix For: 11.0.0.Beta10, 11.0.0.Final Updating mockserver in order to update netty-codec-http version used. Exclusion of dependency from xom.io7m (in order to exclude netty-codec-http version used) -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13098) Excluding a test scopped dependency from io7m.xom ...

by Ilia Vassilev (Jira)

[ https://issues.redhat.com/browse/WFLY-13098?page=com.atlassian.jira.plugi... ] Ilia Vassilev updated WFLY-13098: --------------------------------- Labels: downstream_dependency (was: ) > Excluding a test scopped dependency from io7m.xom ... > ----------------------------------------------------- > > Key: WFLY-13098 > URL: https://issues.redhat.com/browse/WFLY-13098 > Project: WildFly > Issue Type: Task > Reporter: Panagiotis Sotiropoulos > Assignee: Panagiotis Sotiropoulos > Priority: Major > Labels: downstream_dependency > Fix For: 20.0.0.Beta1 > > > Excluding a test scopped dependency from io7m.xom (in order to exclude netty-codec-http version used) ... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10612) Include EJB's IIOP Binding when EJB is deployed logging

by Brad Maxwell (Jira)

[ https://issues.redhat.com/browse/WFLY-10612?page=com.atlassian.jira.plugi... ] Brad Maxwell updated WFLY-10612: -------------------------------- Attachment: WFLY-10612.jar > Include EJB's IIOP Binding when EJB is deployed logging > ------------------------------------------------------- > > Key: WFLY-10612 > URL: https://issues.redhat.com/browse/WFLY-10612 > Project: WildFly > Issue Type: Enhancement > Components: IIOP > Affects Versions: 12.0.0.Final > Reporter: Brad Maxwell > Assignee: Tomasz Adamski > Priority: Major > Attachments: WFLY-10612.jar > > > It would be useful when EJBs configured with IIOP enabled or when enabled by default for all, that it log the binding for the IIOP interface as it is different from the JNDI bindings. > <iiop enable-by-default="true" use-qualified-name="true"/> > {code} > INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) WFLYEJB0473: JNDI bindings for session bean named 'HelloSessionBean' in deployment unit 'deployment "iiop-eap7.jar"' are as follows: > java:global/iiop-eap7/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloSessionBean > java:app/iiop-eap7/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloSessionBean > java:module/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloSessionBean > java:global/iiop-eap7/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloRemoteHome > java:app/iiop-eap7/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloRemoteHome > java:module/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloRemoteHome > java:jboss/exported/iiop-eap7/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloRemoteHome > java:global/iiop-eap7/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloRemote > java:app/iiop-eap7/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloRemote > java:module/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloRemote > java:jboss/exported/iiop-eap7/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloRemote > {code} > Something like this when use-qualified-name="true" > {code} > IIOP bindings for for session bean named 'HelloSessionBean' in deployment unit 'deployment "iiop-eap7.jar"' are as follows: > iiop-eap7/HelloSessionBean > {code} > or use-qualified-name="false" > {code} > IIOP bindings for for session bean named 'HelloSessionBean' in deployment unit 'deployment "iiop-eap7.jar"' are as follows: > HelloSessionBean > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13256) Upgrade bouncycastle to 1.65.0

by Ashley Abdel-Sayed (Jira)

[ https://issues.redhat.com/browse/WFLY-13256?page=com.atlassian.jira.plugi... ] Ashley Abdel-Sayed commented on WFLY-13256: ------------------------------------------- [~brian.stansberry] I'm still trying to determine if the issue is PicketLink related. I'm working on finishing up another task then I'll return to investigating this. > Upgrade bouncycastle to 1.65.0 > ------------------------------ > > Key: WFLY-13256 > URL: https://issues.redhat.com/browse/WFLY-13256 > Project: WildFly > Issue Type: Component Upgrade > Components: Build System, Server > Reporter: Bartosz Spyrko > Assignee: Brian Stansberry > Priority: Blocker > Labels: downstream_dependency > Fix For: 20.0.0.Beta1 > > Attachments: handshake-error.log, handshake-success.log > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 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 April 2020