February 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-9743) WildScribe: use strike-through for deprecated model attribute/operation/children names

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-9743?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-9743: --------------------------------- Issue Type: Feature Request (was: Component Upgrade) > WildScribe: use strike-through for deprecated model attribute/operation/children names > -------------------------------------------------------------------------------------- > > Key: WFLY-9743 > URL: https://issues.jboss.org/browse/WFLY-9743 > Project: WildFly > Issue Type: Feature Request > Components: Documentation > Reporter: Radoslav Husar > Fix For: 12.0.0.CR1 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9743) WildScribe: use strike-through for deprecated model attribute/operation/children names

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-9743?page=com.atlassian.jira.plugin.... ] Radoslav Husar resolved WFLY-9743. ---------------------------------- Assignee: Radoslav Husar Resolution: Done Oops, fixed. > WildScribe: use strike-through for deprecated model attribute/operation/children names > -------------------------------------------------------------------------------------- > > Key: WFLY-9743 > URL: https://issues.jboss.org/browse/WFLY-9743 > Project: WildFly > Issue Type: Feature Request > Components: Documentation > Reporter: Radoslav Husar > Assignee: Radoslav Husar > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9743) WildScribe: use strike-through for deprecated model attribute/operation/children names

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-9743?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-9743: --------------------------------- Fix Version/s: 12.0.0.CR1 > WildScribe: use strike-through for deprecated model attribute/operation/children names > -------------------------------------------------------------------------------------- > > Key: WFLY-9743 > URL: https://issues.jboss.org/browse/WFLY-9743 > Project: WildFly > Issue Type: Feature Request > Components: Documentation > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 12.0.0.CR1 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9878) EclipseLink Entity Scanning broken in Wildfly 11

by Alessandro Moscatelli (JIRA)

[ https://issues.jboss.org/browse/WFLY-9878?page=com.atlassian.jira.plugin.... ] Alessandro Moscatelli updated WFLY-9878: ---------------------------------------- Description: Following : https://docs.jboss.org/author/display/WFLY/JPA+Reference+Guide#JPAReferen... When you try to persist ANY entity (located in ejb, or jar or anywhere you want) if such entity is not listed in persistence.xml you'll get a : Caused by: javax.ejb.EJBException: java.lang.IllegalArgumentException: Object: org.visiontech.optoplus.entity.Provider[ id=null ] is not a known Entity type If I list such entity in persistence.xml the error is gone and the entity is persisted. Inside standalone.xml I used : <system-properties> ... <property name="eclipselink.archive.factory" value="org.jipijapa.eclipselink.JBossArchiveFactoryImpl"/> </system-properties> Is this a problem related to the last version (11 Final) of jipijapa.eclipselink ? I found several topic stating that what I done worked with Wildfly 10 and older version of jipijapa. I tried several combination of older jipijapa and eclipselink versions without success. I have about 130 entities in my probject, I'd REALLY love not to enlist them all. My persistence.xml : <persistence-unit name="optoplus"> <provider>org.eclipse.persistence.jpa.PersistenceProvider</provider> <jta-data-source>java:/jdbc/db_optoplus</jta-data-source> <exclude-unlisted-classes>false</exclude-unlisted-classes> </persistence-unit> was: Following : https://docs.jboss.org/author/display/WFLY/JPA+Reference+Guide#JPAReferen... When you try to persist ANY entity (located in ejb, or jar or anywhere you want) if such entity is not listed in persistence.xml you'll get a : Caused by: javax.ejb.EJBException: java.lang.IllegalArgumentException: Object: org.visiontech.optoplus.entity.Provider[ id=null ] is not a known Entity type If I list such entity in persistence.xml the error is gone and the entity is persisted. Inside standalone.xml I used : <system-properties> ... <property name="eclipselink.archive.factory" value="org.jipijapa.eclipselink.JBossArchiveFactoryImpl"/> </system-properties> Is this a problem related to the last version (11 Final) of jipijapa.eclipselink ? I found several topic stating that what I done worked with Wildfly 10 and older version of jipijapa. I tried several combination of older jipijapa and eclipselink versions without success. I have about 130 entities in my probject, I'd REALLY love not to enlist them all. > EclipseLink Entity Scanning broken in Wildfly 11 > ------------------------------------------------ > > Key: WFLY-9878 > URL: https://issues.jboss.org/browse/WFLY-9878 > Project: WildFly > Issue Type: Bug > Components: JPA / Hibernate > Affects Versions: 11.0.0.Final > Environment: Enterprise Maven Project > Wildfly 11 > Eclipse Link 2.7.1 (2.6.3 and 2.64 were also tested) > Reporter: Alessandro Moscatelli > Assignee: Scott Marlow > Fix For: 12.0.0.Final > > > Following : > https://docs.jboss.org/author/display/WFLY/JPA+Reference+Guide#JPAReferen... > When you try to persist ANY entity (located in ejb, or jar or anywhere you want) if such entity is not listed in persistence.xml you'll get a : > Caused by: javax.ejb.EJBException: java.lang.IllegalArgumentException: Object: org.visiontech.optoplus.entity.Provider[ id=null ] is not a known Entity type > If I list such entity in persistence.xml the error is gone and the entity is persisted. > Inside standalone.xml I used : > <system-properties> > ... > <property name="eclipselink.archive.factory" value="org.jipijapa.eclipselink.JBossArchiveFactoryImpl"/> > </system-properties> > Is this a problem related to the last version (11 Final) of jipijapa.eclipselink ? > I found several topic stating that what I done worked with Wildfly 10 and older version of jipijapa. > I tried several combination of older jipijapa and eclipselink versions without success. > I have about 130 entities in my probject, I'd REALLY love not to enlist them all. > My persistence.xml : > <persistence-unit name="optoplus"> > <provider>org.eclipse.persistence.jpa.PersistenceProvider</provider> > <jta-data-source>java:/jdbc/db_optoplus</jta-data-source> > <exclude-unlisted-classes>false</exclude-unlisted-classes> > </persistence-unit> -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9743) WildScribe: use strike-through for deprecated model attribute/operation/children names

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-9743?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-9743: --------------------------------- Issue Type: Task (was: Feature Request) > WildScribe: use strike-through for deprecated model attribute/operation/children names > -------------------------------------------------------------------------------------- > > Key: WFLY-9743 > URL: https://issues.jboss.org/browse/WFLY-9743 > Project: WildFly > Issue Type: Task > Components: Documentation > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 12.0.0.CR1 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2299) Relation editor

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2299?page=com.atlassian.jira.plugi... ] Michael Anstis reopened DROOLS-2299: ------------------------------------ > Relation editor > --------------- > > Key: DROOLS-2299 > URL: https://issues.jboss.org/browse/DROOLS-2299 > Project: Drools > Issue Type: Sub-task > Components: DMN Editor > Reporter: Michael Anstis > Assignee: Michael Anstis > > Refactoring for "Relation" editor -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9878) EclipseLink Entity Scanning broken in Wildfly 11

by Alessandro Moscatelli (JIRA)

Alessandro Moscatelli created WFLY-9878: ------------------------------------------- Summary: EclipseLink Entity Scanning broken in Wildfly 11 Key: WFLY-9878 URL: https://issues.jboss.org/browse/WFLY-9878 Project: WildFly Issue Type: Bug Components: JPA / Hibernate Affects Versions: 11.0.0.Final Environment: Enterprise Maven Project Wildfly 11 Eclipse Link 2.7.1 (2.6.3 and 2.64 were also tested) Reporter: Alessandro Moscatelli Assignee: Scott Marlow Fix For: 12.0.0.Final Following : https://docs.jboss.org/author/display/WFLY/JPA+Reference+Guide#JPAReferen... When you try to persist ANY entity (located in ejb, or jar or anywhere you want) if such entity is not listed in persistence.xml you'll get a : Caused by: javax.ejb.EJBException: java.lang.IllegalArgumentException: Object: org.visiontech.optoplus.entity.Provider[ id=null ] is not a known Entity type If I list such entity in persistence.xml the error is gone and the entity is persisted. Inside standalone.xml I used : <system-properties> ... <property name="eclipselink.archive.factory" value="org.jipijapa.eclipselink.JBossArchiveFactoryImpl"/> </system-properties> Is this a problem related to the last version (11 Final) of jipijapa.eclipselink ? I found several topic stating that what I done worked with Wildfly 10 and older version of jipijapa. I tried several combination of older jipijapa and eclipselink versions without success. I have about 130 entities in my probject, I'd REALLY love not to enlist them all. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9743) WildScribe: use strike-through for deprecated model attribute/operation/children names

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-9743?page=com.atlassian.jira.plugin.... ] Brian Stansberry commented on WFLY-9743: ---------------------------------------- Component Upgrade? > WildScribe: use strike-through for deprecated model attribute/operation/children names > -------------------------------------------------------------------------------------- > > Key: WFLY-9743 > URL: https://issues.jboss.org/browse/WFLY-9743 > Project: WildFly > Issue Type: Component Upgrade > Components: Documentation > Reporter: Radoslav Husar > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2109) [XLS Decision Table] New Asset Dialogue misses descriptions

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2109?page=com.atlassian.jira.plugi... ] Jozef Marko commented on DROOLS-2109: ------------------------------------- As shown in the screenshots form 2018-02-21, there is needed additional refactoring for these assets. > [XLS Decision Table] New Asset Dialogue misses descriptions > ----------------------------------------------------------- > > Key: DROOLS-2109 > URL: https://issues.jboss.org/browse/DROOLS-2109 > Project: Drools > Issue Type: Bug > Components: XLS Decision Table Editor > Affects Versions: 7.5.0.Final > Reporter: Jozef Marko > Assignee: Jozef Marko > Priority: Optional > Attachments: Screenshot from 2017-11-03 10-20-21.png, Screenshot from 2018-02-21 17-30-29.png, Screenshot from 2018-02-21 17-30-38.png, Screenshot from 2018-02-21 17-30-51.png, Screenshot from 2018-02-21 17-31-12.png, Screenshot from 2018-02-21 17-31-56.png, Screenshot from 2018-02-21 17-32-25.png, Screenshot from 2018-02-21 17-33-00.png, Screenshot from 2018-02-21 17-33-57.png, Screenshot from 2018-02-21 17-34-22.png > > > The attached dialogue shows missing descriptions for table format and file selector. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2109) [XLS Decision Table] New Asset Dialogue misses descriptions

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2109?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-2109: -------------------------------- Attachment: Screenshot from 2018-02-21 17-34-22.png Screenshot from 2018-02-21 17-33-57.png Screenshot from 2018-02-21 17-33-00.png Screenshot from 2018-02-21 17-32-25.png Screenshot from 2018-02-21 17-31-56.png Screenshot from 2018-02-21 17-31-12.png Screenshot from 2018-02-21 17-30-51.png Screenshot from 2018-02-21 17-30-38.png Screenshot from 2018-02-21 17-30-29.png > [XLS Decision Table] New Asset Dialogue misses descriptions > ----------------------------------------------------------- > > Key: DROOLS-2109 > URL: https://issues.jboss.org/browse/DROOLS-2109 > Project: Drools > Issue Type: Bug > Components: XLS Decision Table Editor > Affects Versions: 7.5.0.Final > Reporter: Jozef Marko > Assignee: Jozef Marko > Priority: Optional > Attachments: Screenshot from 2017-11-03 10-20-21.png, Screenshot from 2018-02-21 17-30-29.png, Screenshot from 2018-02-21 17-30-38.png, Screenshot from 2018-02-21 17-30-51.png, Screenshot from 2018-02-21 17-31-12.png, Screenshot from 2018-02-21 17-31-56.png, Screenshot from 2018-02-21 17-32-25.png, Screenshot from 2018-02-21 17-33-00.png, Screenshot from 2018-02-21 17-33-57.png, Screenshot from 2018-02-21 17-34-22.png > > > The attached dialogue shows missing descriptions for table format and file selector. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 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 February 2018