August 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-12300) Convert to Jakarta EE 8 specification APIs

by Cheng Fang (Jira)

[ https://issues.jboss.org/browse/WFLY-12300?page=com.atlassian.jira.plugin... ] Cheng Fang commented on WFLY-12300: ----------------------------------- I added a javadoc plugin section that kinda combines both javadoc settings from jboss-parent and upstream spec project, and it worked ok. I found it necessary to check: * generated javadoc title, footer, header and copyright declaration * MANIFEST.MF in javadoc.jar, source.jar, and api.jar So they don't contain reference to old names and Java, or defaults that are not suitable for forked spec projects. > Convert to Jakarta EE 8 specification APIs > ------------------------------------------ > > Key: WFLY-12300 > URL: https://issues.jboss.org/browse/WFLY-12300 > Project: WildFly > Issue Type: Task > Components: Server > Reporter: Brian Stansberry > Assignee: Scott Marlow > Priority: Critical > Fix For: 18.0.0.Final > > > This is a top-level task for moving WildFly to specification API artifacts associated with Jakarta EE 8. > The Jakarta EE 8 spec APIs are meant to be fully compatible with their Java EE 8 analogues, so this is not expected to result in runtime behavioral differences. > I don't anticipate code changes specific to this top level task. Instead changes will be associated with other issues linked to this one. > The overall goal is to use API jars that either directly come from the Jakarta EE projects, or that use code closely based on those projects; i.e. that are forks derived from the Jakarta EE code that incorporate jboss.org specific changes and whose maintainers monitor the Jakarta EE projects and bring over needed changes and contribute any relevant jboss.org changes back. > For each JBoss specification API fork that existed in EAP 7.2, a designated owner for that API jar has been determined. The task for each owner consists of: > # Create/update a jboss.org Jakarta fork. > # Track work on that fork via issues in the https://issues.jboss.org/projects/JBEE JIRA project. If there is a high-level issue for that fork, the component owner *should* link it to this issue via a 'relates to' link. > # For the fork, the component owner *must* create a WFLY or WFCORE JIRA to track the change of the WildFly code to use the Jarkarta EE based artifact. That can either be a subtask of this task, or a separate issue linked to this once such that that issue is 'incorporated by' this one. That JIRA should have priority 'Critical' and should have its Fix Version set to 18.0.0.Final or 10.0.0.Final for WFCORE. > Generally, WildFly and WildFly Core do not accept non-Final artifacts into their master branch. For projects that we are forking from the Jakarta EE projects, we are making an exception to this rule: > _Once a Jakarta API project has made a staging release and submitted the specification for formal approval, it is acceptable for the jboss.org fork of that project to produce a CR release based on the code in that staged release and ask that it be incorporated into master._ > _In fact, doing this is strongly encouraged as it allows us to further verify the fork._ > Once the staged release is approved, the component owner *must* as soon as possible (e.g. the next working day) produce a .Final artifact from the fork and submit a component upgrade PR. > For artifacts that will not involve a fork (e.g. JPA), the component owner should plan to file a PR moving to the Jakarta artifact (e.g. jakarta.persistence:jakarta.persistence-api) as soon as the official version after Jakarta is available in maven central (after Jakarta EE 8 final release). > Following are the relevant APIs, organized by the maven GA of the artifact produced by the Jakarta project, along with the 'owner' of that component: > ||API||Owner|| > |jakarta.annotation:jakarta.annotation-api|Yeray Borges| > |jakarta.batch:jakarta.batch-api|Cheng Fang| > |jakarta.ejb:jakarta.ejb-api|Cheng Fang/Tomasz Adamski| > |jakarta.el:jakarta.el-api|Scott Marlow| > |jakarta.enterprise.concurrent:jakarta.enterprise.concurrent-api|Eduardo Martins| > |jakarta.faces:jakarta.faces-api|Farah Juma| > |jakarta.interceptor:jakarta.interceptor-api|Yeray Borges| > |jakarta.jms:jakarta.jms-api|Emmanuel Hugonnet| > |jakarta.management.j2ee:jakarta.management.j2ee-api|Jeff Mesnil| > |jakarta.resource:jakarta.resource-api|Stefano Maestri| > |jakarta.security.auth.message:jakarta.security.auth.message-api|Darran Lofthouse / Farah Juma| > |jakarta.security.jacc:jakarta.security.jacc-api|Darran Lofthouse / Farah Juma| > |jakarta.servlet:jakarta.servlet-api|Flavia Rainone| > |jakarta.servlet.jsp:jakarta.servlet.jsp-api|Flavia Rainone| > |jakarta.transaction:jakarta.transaction-api|Tom Jenkinson| > |jakarta.websocket:jakarta.websocket-all|Flavia Rainone| > |jakarta.ws.rs:jakarta.ws.rs-api|Ron Sigal| > |jakarta.xml.bind:jakarta.xml.bind-api|Jim Ma| > |jakarta.xml.rpc:jakarta.xml.rpc-api|Jim Ma| > |jakarta.xml.soap:jakarta.xml.soap-api|Jim Ma| > |jakarta.xml.ws:jakarta.xml.ws-api|Jim Ma| > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4422) BasicXARecovery calculates the name of the XA recovery properties file incorrectly if a number of connections is included

by Simon Dallaway (Jira)

[ https://issues.jboss.org/browse/DROOLS-4422?page=com.atlassian.jira.plugi... ] Simon Dallaway updated DROOLS-4422: ----------------------------------- Priority: Trivial (was: Minor) > BasicXARecovery calculates the name of the XA recovery properties file incorrectly if a number of connections is included > ------------------------------------------------------------------------------------------------------------------------- > > Key: DROOLS-4422 > URL: https://issues.jboss.org/browse/DROOLS-4422 > Project: Drools > Issue Type: Bug > Affects Versions: 7.24.0.Final > Reporter: Simon Dallaway > Assignee: Mario Fusco > Priority: Trivial > > The procedure initialise of BasicXARecovery incorrectly calculates the name of the XA recovery properties file if a number of connections is included > The current code is > fileName = parameter.substring(0, breakPosition - 1); > The correct code should be > fileName = parameter.substring(0, breakPosition); -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4422) BasicXARecovery calculates the name of the XA recovery properties file incorrectly if a number of connections is included

by Simon Dallaway (Jira)

Simon Dallaway created DROOLS-4422: -------------------------------------- Summary: BasicXARecovery calculates the name of the XA recovery properties file incorrectly if a number of connections is included Key: DROOLS-4422 URL: https://issues.jboss.org/browse/DROOLS-4422 Project: Drools Issue Type: Bug Affects Versions: 7.24.0.Final Reporter: Simon Dallaway Assignee: Mario Fusco The procedure initialise of BasicXARecovery incorrectly calculates the name of the XA recovery properties file if a number of connections is included The current code is fileName = parameter.substring(0, breakPosition - 1); The correct code should be fileName = parameter.substring(0, breakPosition); -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4399) KIE Server kie-server-7.24.0.Final-webc fails with ClassNotFoundException

by Simon Dallaway (Jira)

[ https://issues.jboss.org/browse/DROOLS-4399?page=com.atlassian.jira.plugi... ] Simon Dallaway edited comment on DROOLS-4399 at 8/8/19 8:59 PM: ---------------------------------------------------------------- Hi Maciej, Sorry, I haven't had as much time to look at this today as I'd have liked but I believe I have it running now (I haven't actually run any rules or workflows but I'm not getting any errors). I've uploaded a README.md file with the way I've got it going. Feel free to use it if it's correct - I think you need to provide a bit more guidance for providing the right versions so I'm suggesting adding a github link or something that would help. Regards, Simon was (Author: simon.dallaway): Hi Maciej, Sorry, I haven't had as much time to look at this today as I'd have liked but I believe I have it running now. I've uploaded a README.md file with the way I've got it going. Feel free to use it if it's correct. Regards, Simon > KIE Server kie-server-7.24.0.Final-webc fails with ClassNotFoundException > ------------------------------------------------------------------------- > > Key: DROOLS-4399 > URL: https://issues.jboss.org/browse/DROOLS-4399 > Project: Drools > Issue Type: Bug > Components: kie server > Affects Versions: 7.24.0.Final > Environment: Windows 8.1 x64 > Tomcat 9.0.16 > Reporter: Simon Dallaway > Assignee: Maciej Swiderski > Priority: Major > Attachments: README.md, catalina.2019-08-05.log, catalina.2019-08-06.log, catalina.2019-08-08.log, catalina.2019-08-08.log, context.xml, libDir.txt, server.xml, setenv.bat, tomcat-users.xml, xa-recovery-properties.xml > > > Attempting to deploy KIE Server on Tomcat 9 fails with a ClassNotFoundException org.jboss.narayana.tomcat.jta.NarayanaJtaServletContextListener when trying to setup application listener -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4399) KIE Server kie-server-7.24.0.Final-webc fails with ClassNotFoundException

by Simon Dallaway (Jira)

[ https://issues.jboss.org/browse/DROOLS-4399?page=com.atlassian.jira.plugi... ] Simon Dallaway commented on DROOLS-4399: ---------------------------------------- Hi Maciej, Sorry, I haven't had as much time to look at this today as I'd have liked but I believe I have it running now. I've uploaded a README.md file with the way I've got it going. Feel free to use it if it's correct. Regards, Simon > KIE Server kie-server-7.24.0.Final-webc fails with ClassNotFoundException > ------------------------------------------------------------------------- > > Key: DROOLS-4399 > URL: https://issues.jboss.org/browse/DROOLS-4399 > Project: Drools > Issue Type: Bug > Components: kie server > Affects Versions: 7.24.0.Final > Environment: Windows 8.1 x64 > Tomcat 9.0.16 > Reporter: Simon Dallaway > Assignee: Maciej Swiderski > Priority: Major > Attachments: README.md, catalina.2019-08-05.log, catalina.2019-08-06.log, catalina.2019-08-08.log, catalina.2019-08-08.log, context.xml, libDir.txt, server.xml, setenv.bat, tomcat-users.xml, xa-recovery-properties.xml > > > Attempting to deploy KIE Server on Tomcat 9 fails with a ClassNotFoundException org.jboss.narayana.tomcat.jta.NarayanaJtaServletContextListener when trying to setup application listener -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12365) WildFlyCustomJtaPlatform does not cache TSR for manually bootstrapped hibernate apps

by Stuart Douglas (Jira)

[ https://issues.jboss.org/browse/WFLY-12365?page=com.atlassian.jira.plugin... ] Stuart Douglas reassigned WFLY-12365: ------------------------------------- Assignee: Stuart Douglas (was: Brian Stansberry) > WildFlyCustomJtaPlatform does not cache TSR for manually bootstrapped hibernate apps > ------------------------------------------------------------------------------------ > > Key: WFLY-12365 > URL: https://issues.jboss.org/browse/WFLY-12365 > Project: WildFly > Issue Type: Bug > Reporter: Stuart Douglas > Assignee: Stuart Douglas > Priority: Major > > This results in the TSR being looked up from JNDI every time which has a performance impact -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12365) WildFlyCustomJtaPlatform does not cache TSR for manually bootstrapped hibernate apps

by Stuart Douglas (Jira)

[ https://issues.jboss.org/browse/WFLY-12365?page=com.atlassian.jira.plugin... ] Stuart Douglas updated WFLY-12365: ---------------------------------- Component/s: JPA / Hibernate > WildFlyCustomJtaPlatform does not cache TSR for manually bootstrapped hibernate apps > ------------------------------------------------------------------------------------ > > Key: WFLY-12365 > URL: https://issues.jboss.org/browse/WFLY-12365 > Project: WildFly > Issue Type: Bug > Components: JPA / Hibernate > Reporter: Stuart Douglas > Assignee: Stuart Douglas > Priority: Major > > This results in the TSR being looked up from JNDI every time which has a performance impact -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4399) KIE Server kie-server-7.24.0.Final-webc fails with ClassNotFoundException

by Simon Dallaway (Jira)

[ https://issues.jboss.org/browse/DROOLS-4399?page=com.atlassian.jira.plugi... ] Simon Dallaway updated DROOLS-4399: ----------------------------------- Attachment: README.md > KIE Server kie-server-7.24.0.Final-webc fails with ClassNotFoundException > ------------------------------------------------------------------------- > > Key: DROOLS-4399 > URL: https://issues.jboss.org/browse/DROOLS-4399 > Project: Drools > Issue Type: Bug > Components: kie server > Affects Versions: 7.24.0.Final > Environment: Windows 8.1 x64 > Tomcat 9.0.16 > Reporter: Simon Dallaway > Assignee: Maciej Swiderski > Priority: Major > Attachments: README.md, catalina.2019-08-05.log, catalina.2019-08-06.log, catalina.2019-08-08.log, catalina.2019-08-08.log, context.xml, libDir.txt, server.xml, setenv.bat, tomcat-users.xml, xa-recovery-properties.xml > > > Attempting to deploy KIE Server on Tomcat 9 fails with a ClassNotFoundException org.jboss.narayana.tomcat.jta.NarayanaJtaServletContextListener when trying to setup application listener -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4399) KIE Server kie-server-7.24.0.Final-webc fails with ClassNotFoundException

by Simon Dallaway (Jira)

[ https://issues.jboss.org/browse/DROOLS-4399?page=com.atlassian.jira.plugi... ] Simon Dallaway edited comment on DROOLS-4399 at 8/8/19 8:15 PM: ---------------------------------------------------------------- Hi Maciej, I have modified my setenv.bat to have -Dorg.kie.server.id=tomcat-kieserver -Dorg.kie.server.location=http://localhost:8081/kie-server/services/rest/server Note that initially I was just deploying it as kie-server-7.24.0.Final-webc.war but it looks as though it wants to be renamed as kie-server Accessing http://localhost:8081/kie-server/services/rest/server now works but returns <messages><content>Error when initializing server extension of type jBPM KIE Server extension due to Unable to create EntityManagerFactory due to [PersistenceUnit: org.jbpm.domain] Unable to build Hibernate SessionFactory</content><severity>ERROR</severity><timestamp>2019-08-08T15:10:45.816+12:00</timestamp></messages> I read that as meaning that JBPM is not available without the database configured. Of course I want to be able to use that as well as Drools :-) I've attached the Catalina log file for reference (ignore the earlier one for 8/8 - I had a problem of my own making related to the naming of the context). Regards, Simon was (Author: simon.dallaway): Hi Maciej, I'm now wondering where I found the documentation for setting up the org.kie.server.persistence.ds etc. properties. Anyway, I have modified my setenv.bat to have -Dorg.kie.server.id=tomcat-kieserver -Dorg.kie.server.location=http://localhost:8081/kie-server/services/rest/server Note that initially I was just deploying it as kie-server-7.24.0.Final-webc.war but it looks as though it wants to be renamed as kie-server Accessing http://localhost:8081/kie-server/services/rest/server now works but returns <messages><content>Error when initializing server extension of type jBPM KIE Server extension due to Unable to create EntityManagerFactory due to [PersistenceUnit: org.jbpm.domain] Unable to build Hibernate SessionFactory</content><severity>ERROR</severity><timestamp>2019-08-08T15:10:45.816+12:00</timestamp></messages> I read that as meaning that JBPM is not available without the database configured. Of course I want to be able to use that as well as Drools :-) I've attached the Catalina log file for reference (ignore the earlier one for 8/8 - I had a problem of my own making related to the naming of the context). Regards, Simon > KIE Server kie-server-7.24.0.Final-webc fails with ClassNotFoundException > ------------------------------------------------------------------------- > > Key: DROOLS-4399 > URL: https://issues.jboss.org/browse/DROOLS-4399 > Project: Drools > Issue Type: Bug > Components: kie server > Affects Versions: 7.24.0.Final > Environment: Windows 8.1 x64 > Tomcat 9.0.16 > Reporter: Simon Dallaway > Assignee: Maciej Swiderski > Priority: Major > Attachments: catalina.2019-08-05.log, catalina.2019-08-06.log, catalina.2019-08-08.log, catalina.2019-08-08.log, context.xml, libDir.txt, server.xml, setenv.bat, tomcat-users.xml, xa-recovery-properties.xml > > > Attempting to deploy KIE Server on Tomcat 9 fails with a ClassNotFoundException org.jboss.narayana.tomcat.jta.NarayanaJtaServletContextListener when trying to setup application listener -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12365) WildFlyCustomJtaPlatform does not cache TSR for manually bootstrapped hibernate apps

by Stuart Douglas (Jira)

Stuart Douglas created WFLY-12365: ------------------------------------- Summary: WildFlyCustomJtaPlatform does not cache TSR for manually bootstrapped hibernate apps Key: WFLY-12365 URL: https://issues.jboss.org/browse/WFLY-12365 Project: WildFly Issue Type: Bug Reporter: Stuart Douglas Assignee: Brian Stansberry This results in the TSR being looked up from JNDI every time which has a performance impact -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 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 August 2019