June 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (LOGTOOL-92) Add a @Suppressed annotation to add suppressed exceptions to a Throwable return type

by James Perkins (JIRA)

James Perkins created LOGTOOL-92: ------------------------------------ Summary: Add a @Suppressed annotation to add suppressed exceptions to a Throwable return type Key: LOGTOOL-92 URL: https://issues.jboss.org/browse/LOGTOOL-92 Project: Log Tool Issue Type: Enhancement Reporter: James Perkins Assignee: James Perkins Add a {{@Supressed}} annotation which will add suppressed throwables, {{Throwable.addSuppressed}}, to an Throwable return type. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4848) Ignore failing legacy messaging transformer tests

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-4848?page=com.atlassian.jira.plugin.... ] James Perkins updated WFLY-4848: -------------------------------- Summary: Ignore failing legacy messaging transformer tests (was: Messaging transformer tests are failing with a CNFE) > Ignore failing legacy messaging transformer tests > ------------------------------------------------- > > Key: WFLY-4848 > URL: https://issues.jboss.org/browse/WFLY-4848 > Project: WildFly > Issue Type: Bug > Components: JMS > Reporter: James Perkins > Assignee: James Perkins > > When running {{legacy/messages}} subsystem tests with {{-Djboss.test.transformers.eap}} fail. Two fail with a {{ClassNotFoundException}} and two fail assertions. See http://brontes.lab.eng.brq.redhat.com/viewLog.html?buildId=58617&buildTyp... for details. > For now I'll {{@Ignore}} the tests. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4849) Messaging transformer tests are failing with a CNFE

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-4849?page=com.atlassian.jira.plugin.... ] James Perkins updated WFLY-4849: -------------------------------- Git Pull Request: (was: https://github.com/wildfly/wildfly/pull/7683) > Messaging transformer tests are failing with a CNFE > --------------------------------------------------- > > Key: WFLY-4849 > URL: https://issues.jboss.org/browse/WFLY-4849 > Project: WildFly > Issue Type: Bug > Components: JMS > Reporter: James Perkins > Assignee: Jeff Mesnil > > When running {{legacy/messages}} subsystem tests with {{-Djboss.test.transformers.eap}} fail. Two fail with a {{ClassNotFoundException}} and two fail assertions. See http://brontes.lab.eng.brq.redhat.com/viewLog.html?buildId=58617&buildTyp... for details. > For now I'll {{@Ignore}} the tests. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4849) Messaging transformer tests are failing with a CNFE

by James Perkins (JIRA)

James Perkins created WFLY-4849: ----------------------------------- Summary: Messaging transformer tests are failing with a CNFE Key: WFLY-4849 URL: https://issues.jboss.org/browse/WFLY-4849 Project: WildFly Issue Type: Bug Components: JMS Reporter: James Perkins Assignee: Jeff Mesnil When running {{legacy/messages}} subsystem tests with {{-Djboss.test.transformers.eap}} fail. Two fail with a {{ClassNotFoundException}} and two fail assertions. See http://brontes.lab.eng.brq.redhat.com/viewLog.html?buildId=58617&buildTyp... for details. For now I'll {{@Ignore}} the tests. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4848) Messaging transformer tests are failing with a CNFE

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-4848?page=com.atlassian.jira.plugin.... ] James Perkins reassigned WFLY-4848: ----------------------------------- Assignee: James Perkins (was: Jeff Mesnil) > Messaging transformer tests are failing with a CNFE > --------------------------------------------------- > > Key: WFLY-4848 > URL: https://issues.jboss.org/browse/WFLY-4848 > Project: WildFly > Issue Type: Bug > Components: JMS > Reporter: James Perkins > Assignee: James Perkins > > When running {{legacy/messages}} subsystem tests with {{-Djboss.test.transformers.eap}} fail. Two fail with a {{ClassNotFoundException}} and two fail assertions. See http://brontes.lab.eng.brq.redhat.com/viewLog.html?buildId=58617&buildTyp... for details. > For now I'll {{@Ignore}} the tests. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4848) Messaging transformer tests are failing with a CNFE

by James Perkins (JIRA)

James Perkins created WFLY-4848: ----------------------------------- Summary: Messaging transformer tests are failing with a CNFE Key: WFLY-4848 URL: https://issues.jboss.org/browse/WFLY-4848 Project: WildFly Issue Type: Bug Components: JMS Reporter: James Perkins Assignee: Jeff Mesnil When running {{legacy/messages}} subsystem tests with {{-Djboss.test.transformers.eap}} fail. Two fail with a {{ClassNotFoundException}} and two fail assertions. See http://brontes.lab.eng.brq.redhat.com/viewLog.html?buildId=58617&buildTyp... for details. For now I'll {{@Ignore}} the tests. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4581) Provide a migration management operation for JacORB to OpenJDKOrb

by Tomasz Adamski (JIRA)

[ https://issues.jboss.org/browse/WFLY-4581?page=com.atlassian.jira.plugin.... ] Tomasz Adamski updated WFLY-4581: --------------------------------- Fix Version/s: 10.0.0.Alpha5 > Provide a migration management operation for JacORB to OpenJDKOrb > ------------------------------------------------------------------ > > Key: WFLY-4581 > URL: https://issues.jboss.org/browse/WFLY-4581 > Project: WildFly > Issue Type: Feature Request > Components: IIOP > Affects Versions: 9.0.0.CR1 > Reporter: Tomasz Adamski > Assignee: Tomasz Adamski > Fix For: 10.0.0.Alpha5 > > > Provide a management operation that performs a one-time conversion from the JacORB subsystem into the JDK Orb subsystem. This allows users using the CLI to perform a migration, as well as tools such as WindUp to also execute the change. > Alternatively emulation of JacORB, using JDK Orb underneath, if viable, could be performed. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-832) Logical setters do not work with non-natively traitable beans

by Davide Sottara (JIRA)

Davide Sottara created DROOLS-832: ------------------------------------- Summary: Logical setters do not work with non-natively traitable beans Key: DROOLS-832 URL: https://issues.jboss.org/browse/DROOLS-832 Project: Drools Issue Type: Bug Components: core engine Affects Versions: 6.3.0.Beta1, 6.2.0.Final, 6.1.0.Final, 6.0.0.Final, 5.6.0.Final, 5.5.0.Final Reporter: Davide Sottara Assignee: Mario Fusco Fix For: 6.3.0.Beta2 By default, "logical" traitable beans maintain the consistency of a field adding logic to the setters. When using non-natively traitable beans, the additional logic is not invoked -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-831) KIE Execution Server is not able to find the Maven repository

by Roger Martínez (JIRA)

[ https://issues.jboss.org/browse/DROOLS-831?page=com.atlassian.jira.plugin... ] Roger Martínez edited comment on DROOLS-831 at 6/30/15 3:52 PM: ---------------------------------------------------------------- Problem and workaround: ***************************** The problem is that the KIE server Docker container does not have the information of the internal Maven repository for the Workbench container. In a non-docker installation, you should create your settings.xml file for the execution server specifying the workbench internal maven repository, so meanwhile, as a workaround, customer can access the KIE server container's shell (by using nsenter command) and write the settings.xml file in the container's filesystem. NOTE: The settings.xml file created manually following this workaround approach will be removed if you remove that specific KIE server container from you docker host. If will remain as well if you stop and restart it. was (Author: roger600): Problem and workaround: ***************************** The problem is that the KIE server Docker container does not have the information of the internal Maven repository for the Workbench container. In a non-docker installation, you should create your settings.xml file for the execution server specifying the workbench internal maven repository, so meanwhile, as a workaround, customer can access the KIE server container's shell (by using nsenter command) and write the settings.xml file in the container's filesystem. > KIE Execution Server is not able to find the Maven repository > ------------------------------------------------------------- > > Key: DROOLS-831 > URL: https://issues.jboss.org/browse/DROOLS-831 > Project: Drools > Issue Type: Bug > Components: docker images > Affects Versions: 6.2.0.Final > Environment: ALL > Reporter: Roger Martínez > Assignee: Roger Martínez > > In a non-Docker installation of the KIE execution server, the user must configure the Maven settings file to specify where the Maven repository for the artifacts is located. > As Docker images are immutable, this configuration must be specified at runtime using environment variables when the container starts. > This feature is not implemented on latest image tag and it's mandatory for being able to use the external Maven repository. > This bug is reported from community feedback: > "I'm trying out the docker images for the workbench-showcase and the execution-showcase. Fresh install. I'm using -p 8080:8080 for the wb and 8081:8080 for the exec. WB runs fine and I can build and deploy the mortgage project. Exec runs fine and I can access using REST. I can register the exec server fine. Mortgage container creates fine. Starting the container produces this error on the exec docker: > 987 ERROR [org.kie.server.services.rest.KieServerRestImpl] (default task-5) Error creating container 'Test1' for module 'mortgages:mortgages:0.0.1': java.lang.RuntimeException: Cannot find KieModule: mortgages:mortgages:0.0.1 > Should this work out of the box?" -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-831) KIE Execution Server is not able to find the Maven repository

by Roger Martínez (JIRA)

[ https://issues.jboss.org/browse/DROOLS-831?page=com.atlassian.jira.plugin... ] Roger Martínez commented on DROOLS-831: --------------------------------------- Problem and workaround: ***************************** The problem is that the KIE server Docker container does not have the information of the internal Maven repository for the Workbench container. In a non-docker installation, you should create your settings.xml file for the execution server specifying the workbench internal maven repository, so meanwhile, as a workaround, customer can access the KIE server container's shell (by using nsenter command) and write the settings.xml file in the container's filesystem. > KIE Execution Server is not able to find the Maven repository > ------------------------------------------------------------- > > Key: DROOLS-831 > URL: https://issues.jboss.org/browse/DROOLS-831 > Project: Drools > Issue Type: Bug > Components: docker images > Affects Versions: 6.2.0.Final > Environment: ALL > Reporter: Roger Martínez > Assignee: Roger Martínez > > In a non-Docker installation of the KIE execution server, the user must configure the Maven settings file to specify where the Maven repository for the artifacts is located. > As Docker images are immutable, this configuration must be specified at runtime using environment variables when the container starts. > This feature is not implemented on latest image tag and it's mandatory for being able to use the external Maven repository. > This bug is reported from community feedback: > "I'm trying out the docker images for the workbench-showcase and the execution-showcase. Fresh install. I'm using -p 8080:8080 for the wb and 8081:8080 for the exec. WB runs fine and I can build and deploy the mortgage project. Exec runs fine and I can access using REST. I can register the exec server fine. Mortgage container creates fine. Starting the container produces this error on the exec docker: > 987 ERROR [org.kie.server.services.rest.KieServerRestImpl] (default task-5) Error creating container 'Test1' for module 'mortgages:mortgages:0.0.1': java.lang.RuntimeException: Cannot find KieModule: mortgages:mortgages:0.0.1 > Should this work out of the box?" -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 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 June 2015