April 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-5223) User cannot open malformed scesim file. Loading popup is spining infinitive times

by Daniele Zonca (Jira)

[ https://issues.redhat.com/browse/DROOLS-5223?page=com.atlassian.jira.plug... ] Daniele Zonca reassigned DROOLS-5223: ------------------------------------- Assignee: Yeser Amer (was: Daniele Zonca) > User cannot open malformed scesim file. Loading popup is spining infinitive times > --------------------------------------------------------------------------------- > > Key: DROOLS-5223 > URL: https://issues.redhat.com/browse/DROOLS-5223 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.33.0.Final, 7.34.0.Final, 7.35.0.Final > Reporter: Anna Dupliak > Assignee: Yeser Amer > Priority: Major > Labels: drools-tools > Attachments: Traffic.scesim > > > If user import Scesim file that have xml tag unclosed, > then user gets warning, but loading popup is not disappearing > and user cannot proceed. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12709) Add MP REST Client TCK to WildFly testsuite

by Ingo Weiss (Jira)

[ https://issues.redhat.com/browse/WFLY-12709?page=com.atlassian.jira.plugi... ] Ingo Weiss updated WFLY-12709: ------------------------------ Labels: downstream_dependency (was: ) > Add MP REST Client TCK to WildFly testsuite > ------------------------------------------- > > Key: WFLY-12709 > URL: https://issues.redhat.com/browse/WFLY-12709 > Project: WildFly > Issue Type: Task > Components: REST > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Priority: Major > Labels: downstream_dependency > Fix For: 20.0.0.Beta1 > > > The MP REST Client TCK is currently part of the RESTEasy testsuite. It should be added to the WildFly testsuite too. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 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] gave me feedback and verified which fields to use for this example. He suggested adding grouping label, so I've added that and made them expand/collapsible. I also added a node type icon to make it more understandable which node/type the inputs relate to. One concept was to also make that grouping label a link that could navigate the user back to that node, wdyt? Here's a quick mock: !Screen Shot 2020-04-09 at 9.29.34 AM.png|thumbnail! I'll update the click-thru accordingly if this looks okay to you, please let me know thanks! :) > 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)

4 years, 6 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 updated DROOLS-4746: -------------------------------------- Attachment: Screen Shot 2020-04-09 at 9.29.34 AM.png > 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)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5229) DMNValidate mojo fails XMLSchema validation with included models

by Guilherme Gomes (Jira)

[ https://issues.redhat.com/browse/DROOLS-5229?page=com.atlassian.jira.plug... ] Guilherme Gomes updated DROOLS-5229: ------------------------------------ Priority: Major (was: Minor) > DMNValidate mojo fails XMLSchema validation with included models > ---------------------------------------------------------------- > > Key: DROOLS-5229 > URL: https://issues.redhat.com/browse/DROOLS-5229 > Project: Drools > Issue Type: Bug > Affects Versions: 7.34.0.Final > Reporter: Tracy Hires > Assignee: Guilherme Gomes > Priority: Major > Attachments: ValidateDMN Mojo Failure.png, xml_validation_error.zip > > > The attached DMN decision project was built using Business Central 7.34.0.Final. In this project, the dmn model `Math Functions.dmn` invokes business knowledge model `Quotient` from dmn model `Divide.dmn`. Invoking the ValidateDMN mojo (enabled by default) from the kie-maven-plugin fails XML Validation. One can get past this error by disabling DMNValidation with the following configuration in the pom (though disabling DMNValidation for an XML Schema validation also prevents finding FEEL parser errors): > ``` > <build> > <plugins> > <plugin> > <groupId>org.kie</groupId> > <artifactId>kie-maven-plugin</artifactId> > <version>7.34.0.Final</version> > <extensions>true</extensions> >  > <configuration> > <validateDMN>disabled</validateDMN> > </configuration> > </plugin> > </plugins> > </build> > ``` > When one combines the two dmn models into a single model, the XML Validation succeeds (this example is not supplied, but is trivial to re-build). -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13362) Distributable session attribute ID generation is unnecessarily expensive

by Paul Ferraro (Jira)

Paul Ferraro created WFLY-13362: ----------------------------------- Summary: Distributable session attribute ID generation is unnecessarily expensive Key: WFLY-13362 URL: https://issues.redhat.com/browse/WFLY-13362 Project: WildFly Issue Type: Task Components: Clustering Affects Versions: 19.0.0.Final Reporter: Paul Ferraro Assignee: Paul Ferraro Session attribute identifiers only need to be unique within a given session. Thus, UUID.randomUUID() is overkill. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

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

by Tomasz Adamski (Jira)

Tomasz Adamski created WFLY-13361: ------------------------------------- Summary: 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: Brian Stansberry -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

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

by Ranabir Chakraborty (Jira)

[ https://issues.redhat.com/browse/WFLY-10612?page=com.atlassian.jira.plugi... ] Ranabir Chakraborty commented on WFLY-10612: -------------------------------------------- [~bmaxwell] is this issue still there ? > 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 > > 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)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13360) Log WARN when EJB does not implement Business interface and is not compliant with EJB 3.2 spec

by Panagiotis Sotiropoulos (Jira)

[ https://issues.redhat.com/browse/WFLY-13360?page=com.atlassian.jira.plugi... ] Panagiotis Sotiropoulos commented on WFLY-13360: ------------------------------------------------ Adding a multi-version testcase : https://github.com/jboss-set/eap-additional-testsuite/pull/134 > Log WARN when EJB does not implement Business interface and is not compliant with EJB 3.2 spec > ---------------------------------------------------------------------------------------------- > > Key: WFLY-13360 > URL: https://issues.redhat.com/browse/WFLY-13360 > Project: WildFly > Issue Type: Bug > Reporter: Panagiotis Sotiropoulos > Assignee: Panagiotis Sotiropoulos > Priority: Major > > From the specification every business interface need to be declared explicitly as a business interface by @Remote or @Local annotation or deployment descriptor. > EJB 3.2 specification > 4.9.7 Session Bean’s Business Interface > - The bean class must implement the interface or the interface must be designated as a local or remote business interface of the bean by means of the Local or Remote annotation or in the deployment descriptor. > - All business interfaces must be explicitly designated as such if any of the following is true: > - the bean exposes a no-interface view > - any interface of the bean class is explicitly designated as a business interface of the bean by either of the following means: > - using the Local or Remote annotation with a non-empty value on the bean class > - using the Local or Remote annotation on the interface > - in the deployment descriptor > If EJB A implements I and EJB B extends A , EJB B must also declare it implements I in order to be spec compliant: > public interface I {...} > > @Stateless > public class A implements I {...} > > @Stateless > public class B extends A {...} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13360) Log WARN when EJB does not implement Business interface and is not compliant with EJB 3.2 spec

by Panagiotis Sotiropoulos (Jira)

Panagiotis Sotiropoulos created WFLY-13360: ---------------------------------------------- Summary: Log WARN when EJB does not implement Business interface and is not compliant with EJB 3.2 spec Key: WFLY-13360 URL: https://issues.redhat.com/browse/WFLY-13360 Project: WildFly Issue Type: Bug Reporter: Panagiotis Sotiropoulos Assignee: Panagiotis Sotiropoulos -- This message was sent by Atlassian Jira (v7.13.8#713008)

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