November 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-11268) Eliminate ServiceBuilder's addDependencies() usages

by Richard Opalka (Jira)

Richard Opalka created WFLY-11268: ------------------------------------- Summary: Eliminate ServiceBuilder's addDependencies() usages Key: WFLY-11268 URL: https://issues.jboss.org/browse/WFLY-11268 Project: WildFly Issue Type: Sub-task Reporter: Richard Opalka Assignee: Richard Opalka Fix For: 15.0.0.Alpha1 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11259) Wildfly 11.0.0.Final org.dom4j.DocumentFactory cannot be cast to org.dom4j.DocumentFactory

by Adam Bialas (Jira)

[ https://issues.jboss.org/browse/WFLY-11259?page=com.atlassian.jira.plugin... ] Adam Bialas updated WFLY-11259: ------------------------------- Description: I have an ear file which I want to deploy to the Wildfly 11.0.0.Final. In this ear file in the lib folder I have dom4j-2.0.1.jar. One of the sub deployments (war) uses JPA (no dependencies to hibernate, just to javax.javaee-api as compile only). This sub deployment contains of course the persistence.xml file. I see in the logs that when the application server starts and loads this file the following exception is thrown: org.dom4j.DocumentFactory cannot be cast to org.dom4j.DocumentFactory and the application fails to deploy. I checked many posts and forums on the net and as far as I understand I must exclude the dom4j provided by the application server so the jar located in the lib folder of ear can be used. I created jboss-deployment-structure: <?xml version="1.0" encoding="UTF-8"?> <jboss-deployment-structure> <deployment> <exclusions> <module name="org.dom4j"/> </exclusions> </deployment> </jboss-deployment-structure> Even though I get the same exception so I suppose both jars are loaded and cause problems. I checked how class loading works on Wildfly 11.0.0 in comparison to JBoss EAP 7.1. In both cases this class is first loaded from provided 1.6.1 jar. JBoss does not load the newer version. However, Wildfly does and here is the problem. was: I have an ear file which I want to deploy to the Wildfly 11.0.0.Final. In this ear file in the lib folder I have dom4j-2.0.1.jar. One of the sub deployments (war) uses JPA (no dependencies to hibernate, just to javax.javaee-api as compile only). This sub deployment contains of course the persistence.xml file. I see in the logs that when the application server starts and loads this file the following exception is thrown: org.dom4j.DocumentFactory cannot be cast to org.dom4j.DocumentFactory and the application fails to deploy. I checked many posts and forums on the net and as far as I understand I must exclude the dom4j provided by the application server so the jar located in the lib folder of ear can be used. I created jboss-deployment-structure: <?xml version="1.0" encoding="UTF-8"?> <jboss-deployment-structure> <deployment> <exclusions> <module name="org.dom4j"/> </exclusions> </deployment> </jboss-deployment-structure> Even though I get the same exception so I suppose both jars are loaded and cause problems. > Wildfly 11.0.0.Final org.dom4j.DocumentFactory cannot be cast to org.dom4j.DocumentFactory > ------------------------------------------------------------------------------------------ > > Key: WFLY-11259 > URL: https://issues.jboss.org/browse/WFLY-11259 > Project: WildFly > Issue Type: Bug > Affects Versions: 11.0.0.Final > Reporter: Adam Bialas > Assignee: Jason Greene > Priority: Major > > I have an ear file which I want to deploy to the Wildfly 11.0.0.Final. In this ear file in the lib folder I have dom4j-2.0.1.jar. One of the sub deployments (war) uses JPA (no dependencies to hibernate, just to javax.javaee-api as compile only). This sub deployment contains of course the persistence.xml file. I see in the logs that when the application server starts and loads this file the following exception is thrown: > org.dom4j.DocumentFactory cannot be cast to org.dom4j.DocumentFactory > and the application fails to deploy. > I checked many posts and forums on the net and as far as I understand I must exclude the dom4j provided by the application server so the jar located in the lib folder of ear can be used. > I created jboss-deployment-structure: > <?xml version="1.0" encoding="UTF-8"?> > <jboss-deployment-structure> > <deployment> > <exclusions> > <module name="org.dom4j"/> > </exclusions> > </deployment> > </jboss-deployment-structure> > Even though I get the same exception so I suppose both jars are loaded and cause problems. > I checked how class loading works on Wildfly 11.0.0 in comparison to JBoss EAP 7.1. In both cases this class is first loaded from provided 1.6.1 jar. JBoss does not load the newer version. However, Wildfly does and here is the problem. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-424) Create Maistra Message Bus Consumer Job

by Matt Mahoney (Jira)

[ https://issues.jboss.org/browse/SWSQE-424?page=com.atlassian.jira.plugin.... ] Matt Mahoney commented on SWSQE-424: ------------------------------------ Example producer job: http://pastebin.test.redhat.com/665492 > Create Maistra Message Bus Consumer Job > --------------------------------------- > > Key: SWSQE-424 > URL: https://issues.jboss.org/browse/SWSQE-424 > Project: Kiali QE > Issue Type: Dev Task > Reporter: Matt Mahoney > Assignee: Matt Mahoney > Priority: Major > > This job will: > - Consume the Message Bus Maistra build notice > - Run the Maistra job (deploy Maistra, bookinfo, kiali) > - Traffic to bookinfo > - Run E2E tests -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4179) Refactor MBeanRegistrationService from WildFly-Core to WildFly

by Richard Opalka (Jira)

[ https://issues.jboss.org/browse/WFCORE-4179?page=com.atlassian.jira.plugi... ] Richard Opalka updated WFCORE-4179: ----------------------------------- Git Pull Request: https://github.com/wildfly/wildfly-core/pull/3580 (was: https://github.com/wildfly/wildfly-core/pull/3568) > Refactor MBeanRegistrationService from WildFly-Core to WildFly > -------------------------------------------------------------- > > Key: WFCORE-4179 > URL: https://issues.jboss.org/browse/WFCORE-4179 > Project: WildFly Core > Issue Type: Sub-task > Components: JMX > Reporter: Richard Opalka > Assignee: Richard Opalka > Priority: Major > Fix For: 7.0.0.Alpha5 > > > MBeanRegistrationService have been moved to WildFly so we can eliminate it from WildFly-Core JMX subsystem. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4179) Refactor MBeanRegistrationService from WildFly-Core to WildFly

by Richard Opalka (Jira)

[ https://issues.jboss.org/browse/WFCORE-4179?page=com.atlassian.jira.plugi... ] Richard Opalka updated WFCORE-4179: ----------------------------------- Description: MBeanRegistrationService have been moved to WildFly so we can eliminate it from WildFly-Core JMX subsystem. (was: In order to be able to migrate SAR WildFly subsystem to new MSC API we need to enrich MBeanRegistrationService to support new MSC API.) > Refactor MBeanRegistrationService from WildFly-Core to WildFly > -------------------------------------------------------------- > > Key: WFCORE-4179 > URL: https://issues.jboss.org/browse/WFCORE-4179 > Project: WildFly Core > Issue Type: Sub-task > Components: JMX > Reporter: Richard Opalka > Assignee: Richard Opalka > Priority: Major > Fix For: 7.0.0.Alpha5 > > > MBeanRegistrationService have been moved to WildFly so we can eliminate it from WildFly-Core JMX subsystem. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4179) Refactor MBeanRegistrationService from WildFly-Core to WildFly

by Richard Opalka (Jira)

[ https://issues.jboss.org/browse/WFCORE-4179?page=com.atlassian.jira.plugi... ] Richard Opalka updated WFCORE-4179: ----------------------------------- Summary: Refactor MBeanRegistrationService from WildFly-Core to WildFly (was: Enrich MBeanRegistrationService to support both new and deprecated MSC API) > Refactor MBeanRegistrationService from WildFly-Core to WildFly > -------------------------------------------------------------- > > Key: WFCORE-4179 > URL: https://issues.jboss.org/browse/WFCORE-4179 > Project: WildFly Core > Issue Type: Sub-task > Components: JMX > Reporter: Richard Opalka > Assignee: Richard Opalka > Priority: Major > Fix For: 7.0.0.Alpha5 > > > In order to be able to migrate SAR WildFly subsystem to new MSC API we need to enrich > MBeanRegistrationService to support new MSC API. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3220) [DMN Designer] [Edge] Unable to edit context cell

by Daniel José dos Santos (Jira)

[ https://issues.jboss.org/browse/DROOLS-3220?page=com.atlassian.jira.plugi... ] Daniel José dos Santos edited comment on DROOLS-3220 at 11/1/18 2:07 PM: ------------------------------------------------------------------------- I don't know if I get it correctly !drools-3220.gif! . I just tested with latest snapshot and I think is working (if I get it correctly). Can you confirm? was (Author: dadossan): I don't know if I get it correctly !drools-3220.gif! . I just tested with latest snapshot and I think is working (if I get it correctly). Can you confirm? > [DMN Designer] [Edge] Unable to edit context cell > ------------------------------------------------- > > Key: DROOLS-3220 > URL: https://issues.jboss.org/browse/DROOLS-3220 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.14.0.Final > Environment: Windows, Edge browser > Reporter: Jozef Marko > Assignee: Daniel José dos Santos > Priority: Blocker > Labels: drools-tools > Attachments: drools-3220.gif > > > User is unable to invoke edit mode for context cells. Other expression types seems to work fine. > Spotted during DROOLS-3214 review, however don't think it is related. > h2. Acceptance test > Invoke edit mode of regular cell > - Literal > - Dec. Table > - Function > - Relation > - Invocation > - Context > Invoke edit mode of header cell - where applicable > - Literal > - Dec. Table > - Function > - Relation > - Invocation > - Context -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3220) [DMN Designer] [Edge] Unable to edit context cell

by Daniel José dos Santos (Jira)

[ https://issues.jboss.org/browse/DROOLS-3220?page=com.atlassian.jira.plugi... ] Daniel José dos Santos updated DROOLS-3220: ------------------------------------------- Attachment: drools-3220.gif > [DMN Designer] [Edge] Unable to edit context cell > ------------------------------------------------- > > Key: DROOLS-3220 > URL: https://issues.jboss.org/browse/DROOLS-3220 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.14.0.Final > Environment: Windows, Edge browser > Reporter: Jozef Marko > Assignee: Daniel José dos Santos > Priority: Blocker > Labels: drools-tools > Attachments: drools-3220.gif > > > User is unable to invoke edit mode for context cells. Other expression types seems to work fine. > Spotted during DROOLS-3214 review, however don't think it is related. > h2. Acceptance test > Invoke edit mode of regular cell > - Literal > - Dec. Table > - Function > - Relation > - Invocation > - Context > Invoke edit mode of header cell - where applicable > - Literal > - Dec. Table > - Function > - Relation > - Invocation > - Context -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-448) Add missing Label checks for all objects

by Hayk Hovsepyan (Jira)

[ https://issues.jboss.org/browse/SWSQE-448?page=com.atlassian.jira.plugin.... ] Hayk Hovsepyan commented on SWSQE-448: -------------------------------------- https://github.com/Kiali-QE/kiali-qe-python/pull/94 > Add missing Label checks for all objects > ---------------------------------------- > > Key: SWSQE-448 > URL: https://issues.jboss.org/browse/SWSQE-448 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3220) [DMN Designer] [Edge] Unable to edit context cell

by Daniel José dos Santos (Jira)

[ https://issues.jboss.org/browse/DROOLS-3220?page=com.atlassian.jira.plugi... ] Daniel José dos Santos commented on DROOLS-3220: ------------------------------------------------ I don't know if I get it correctly !drools-3220.gif! . I just tested with latest snapshot and I think is working (if I get it correctly). Can you confirm? > [DMN Designer] [Edge] Unable to edit context cell > ------------------------------------------------- > > Key: DROOLS-3220 > URL: https://issues.jboss.org/browse/DROOLS-3220 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.14.0.Final > Environment: Windows, Edge browser > Reporter: Jozef Marko > Assignee: Daniel José dos Santos > Priority: Blocker > Labels: drools-tools > > User is unable to invoke edit mode for context cells. Other expression types seems to work fine. > Spotted during DROOLS-3214 review, however don't think it is related. > h2. Acceptance test > Invoke edit mode of regular cell > - Literal > - Dec. Table > - Function > - Relation > - Invocation > - Context > Invoke edit mode of header cell - where applicable > - Literal > - Dec. Table > - Function > - Relation > - Invocation > - Context -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 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 November 2018