January 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-12901) Create new QuickStart demonstrating MicroProfile JWT

by James Perkins (Jira)

[ https://issues.redhat.com/browse/WFLY-12901?page=com.atlassian.jira.plugi... ] James Perkins updated WFLY-12901: --------------------------------- Fix Version/s: 19.0.0.Beta2 (was: 19.0.0.Beta1) > Create new QuickStart demonstrating MicroProfile JWT > ---------------------------------------------------- > > Key: WFLY-12901 > URL: https://issues.redhat.com/browse/WFLY-12901 > Project: WildFly > Issue Type: Task > Components: MP JWT, Quickstarts, Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Fix For: 19.0.0.Beta2 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12866) Add MP Metrics test for Webservice

by James Perkins (Jira)

[ https://issues.redhat.com/browse/WFLY-12866?page=com.atlassian.jira.plugi... ] James Perkins updated WFLY-12866: --------------------------------- Fix Version/s: 19.0.0.Beta2 (was: 19.0.0.Beta1) > Add MP Metrics test for Webservice > ----------------------------------- > > Key: WFLY-12866 > URL: https://issues.redhat.com/browse/WFLY-12866 > Project: WildFly > Issue Type: Task > Components: Web Services > Affects Versions: 18.0.1.Final > Reporter: Jim Ma > Assignee: Jim Ma > Priority: Minor > Fix For: 19.0.0.Beta2 > > > Add a Microprofile-metrics test to demonstrate this works for webservice endpoint -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12765) Webservice deployment fails

by James Perkins (Jira)

[ https://issues.redhat.com/browse/WFLY-12765?page=com.atlassian.jira.plugi... ] James Perkins updated WFLY-12765: --------------------------------- Fix Version/s: 19.0.0.Beta2 (was: 19.0.0.Beta1) > Webservice deployment fails > --------------------------- > > Key: WFLY-12765 > URL: https://issues.redhat.com/browse/WFLY-12765 > Project: WildFly > Issue Type: Bug > Components: Web Services > Affects Versions: 18.0.0.Final > Reporter: Jim Ma > Assignee: Jim Ma > Priority: Major > Fix For: 19.0.0.Beta2 > > > Enabling elytron in undertow subsystem, EAP fails to deploy a webservice war and show the following error messages: > 17:44:48,834 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) WFLYCTL0013: Operation ("add") failed - address: ([("deployment" => "wsat-simple.war")]) - failure description: { > "WFLYCTL0412: Required services that are not installed:" => ["jboss.security.security-domain.other"], > "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.ws.endpoint.\"wsat-simple.war\".\"org.jboss.as.quickstarts.wsa > t.simple.RestaurantServiceATImpl\" is missing [jboss.security.security-domain.other]"] > } > 17:44:48,836 ERROR [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0021: Deploy of deployment "wsat-simple.war" was rolled back with the following failure message: > { > "WFLYCTL0412: Required services that are not installed:" => ["jboss.security.security-domain.other"], > "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.ws.endpoint.\"wsat-simple.war\".\"org.jboss.as.quickstarts.wsat.simple.RestaurantServiceATImpl\" is missing [jboss.security.security-domain.other]"] > } > 17:44:48,867 ERROR [org.jboss.ws.common.deployment] (MSC service thread 1-7) JBWS022102: Cannot stop endpoint in state UNDEFINED: jboss.ws:context=,endpoint=org.jboss.as.quickstarts.wsat.simple.RestaurantServiceATImpl -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

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

by James Perkins (Jira)

[ https://issues.redhat.com/browse/WFLY-12709?page=com.atlassian.jira.plugi... ] James Perkins updated WFLY-12709: --------------------------------- Fix Version/s: 19.0.0.Beta2 (was: 19.0.0.Beta1) > 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 > Fix For: 19.0.0.Beta2 > > > 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)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12674) wildfly.jpa.skipquerydetach set to true, will now skip clearing of query results

by James Perkins (Jira)

[ https://issues.redhat.com/browse/WFLY-12674?page=com.atlassian.jira.plugi... ] James Perkins updated WFLY-12674: --------------------------------- Fix Version/s: 19.0.0.Beta2 (was: 19.0.0.Beta1) > wildfly.jpa.skipquerydetach set to true, will now skip clearing of query results > -------------------------------------------------------------------------------- > > Key: WFLY-12674 > URL: https://issues.redhat.com/browse/WFLY-12674 > Project: WildFly > Issue Type: Bug > Components: JPA / Hibernate > Reporter: Scott Marlow > Assignee: Scott Marlow > Priority: Major > Fix For: 19.0.0.Beta2 > > > Introduce wildfly.jpa.skipquerydetach that defaults to false (to wrap query objects with detacher that clears query results when obtained) but could be set to true, for JBoss AS 5/6 compatibility. This could of been part of [WFLY-3674] but was overlooked. > An example of setting wildfly.jpa.skipquerydetach to true, so that the various query detacher will not be used (e.g. underlying query is returned instead of instance of QueryNonTxInvocationDetacher/TypedQueryNonTxInvocationDetacher/StoredProcedureQueryNonTxInvocationDetacher wrapper): > {code} > <property name="wildfly.jpa.skipquerydetach" value="true" /> > {code} > The below reference notes are more for background information but provide the explanation of why the AS5/6 way of detaching loaded entities changed later, to ensure the returned results from Query objects, are detached, instead of the current persistence context at the time of creating the query object, as per feedback below from JPA lead Linda DeMichiel. > [From related JPA expert group discussion|https://download.oracle.com/javaee-archive/jpa-spec.java.net/u...]: > {code} > >>>>> Perhaps a clearer proposal could be: > >>>>> > >>>>> " > >>>>> If the entity manager is invoked outside the scope of a transaction, > >>>>> any entities loaded from the database will > >>>>> immediately become detached at the end of the container level method > >>>>> invocation call (e.g. when the session bean method > >>>>> ends). > >>>>> " > >>>> > >>>> Ah, thanks. That is not the intended semantics. Rather it is that the > >>>> persistence context is created to service the method call that is made > >>>> on the entity manager only. It doesn't have the duration of a business > >>>> method invocation. > >>> > >>> Is it really? > >>> > >> > >> Yes. See also section 3.8.7, which is quite explicit with regard to > >> queries. > >> BTW, these decisions date back to JPA 1.0 (aka EJB 3.0). > > > > My updated proposal for the 7.6.2 wording is: > > > > " > > If the entity manager is invoked outside the scope of a transaction, any entities loaded from the database will > > immediately become detached at the end of the entity manager method call. > > " > OK, sure + "... or query invocation" > {code} > Note that we (JPA expert group) missed Linda's response of "... or query invocation" in the JPA spec update, as the JPA 2.2 spec today states: > {quote} > 7.6.2 Container-managed Transaction-scoped Persistence Context > The application can obtain a container-managed entity manager with transaction-scoped persistence context by injection or direct lookup in the JNDI namespace. The persistence context type for the entity manager is defaulted or defined as PersistenceContextType.TRANSACTION. > A new persistence context begins when the container-managed entity manager is invoked [84] in the scope of an active JTA transaction, and there is no current persistence context already associated with the JTA transaction. The persistence context is created and then associated with the JTA transaction. This association of the persistence context with the JTA transaction is independent of the synchronization type of the persistence context and whether the persistence context has been joined to the transaction. > {quote} > [Some related AS5/6 JPA container code.|https://anonsvn.jboss.org/repos/jbossas/projects/jpa/trunk/impl/src...] which simply cleared the persistence context as we were creating a new Query, for example see: > {code} > public Query createQuery(String ejbqlString) > { > EntityManager em = getEntityManager(); > detachEntitiesIfNoTx(em); > return em.createQuery(ejbqlString); > } > {code} > Also of reference, is from issue description [WFLY-3674]: > {quote} > For compatibility with earlier JBoss application server versions (5.0/6.0), add an extension that allows the persistence context to last until the referencing persistence context is closed. > For example, in a session method that has no active JTA transaction, entities returned, will not cleared from the persistence context, until the session method completes. This extension is only introduced to allow compatibility with older application server versions. > {quote} > [WFLY-12674] is about doing the same for Queries (if wildfly.jpa.skipquerydetach is set to true). -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12993) Upgrade Smallrye JWT to 2.0.12

by James Perkins (Jira)

[ https://issues.redhat.com/browse/WFLY-12993?page=com.atlassian.jira.plugi... ] James Perkins updated WFLY-12993: --------------------------------- Fix Version/s: 19.0.0.Beta2 (was: 19.0.0.Beta1) > Upgrade Smallrye JWT to 2.0.12 > ------------------------------ > > Key: WFLY-12993 > URL: https://issues.redhat.com/browse/WFLY-12993 > Project: WildFly > Issue Type: Component Upgrade > Components: MP JWT > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Fix For: 19.0.0.Beta2 > > > This is an upgrade to a private module used to provide JWT capabilities within WildFly. > https://github.com/smallrye/smallrye-jwt/compare/2.0.11...2.0.12 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12990) Upgrade WildFly-Naming-Client from 1.0.11.final to 1.0.12.Final

by James Perkins (Jira)

[ https://issues.redhat.com/browse/WFLY-12990?page=com.atlassian.jira.plugi... ] James Perkins updated WFLY-12990: --------------------------------- Fix Version/s: 19.0.0.Beta2 (was: 19.0.0.Beta1) > Upgrade WildFly-Naming-Client from 1.0.11.final to 1.0.12.Final > --------------------------------------------------------------- > > Key: WFLY-12990 > URL: https://issues.redhat.com/browse/WFLY-12990 > Project: WildFly > Issue Type: Component Upgrade > Components: Naming > Reporter: Richard Opalka > Assignee: Richard Opalka > Priority: Major > Fix For: 19.0.0.Beta2 > > > This component upgrade fixes https://issues.redhat.com/browse/WFNC-56 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12988) Upgrade smallrye-fault-tolerance to 2.1.5

by James Perkins (Jira)

[ https://issues.redhat.com/browse/WFLY-12988?page=com.atlassian.jira.plugi... ] James Perkins updated WFLY-12988: --------------------------------- Fix Version/s: 19.0.0.Beta2 (was: 19.0.0.Beta1) > Upgrade smallrye-fault-tolerance to 2.1.5 > ----------------------------------------- > > Key: WFLY-12988 > URL: https://issues.redhat.com/browse/WFLY-12988 > Project: WildFly > Issue Type: Component Upgrade > Components: MP Fault Tolerance > Affects Versions: No Release > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Critical > Fix For: 19.0.0.Beta2 > > > https://github.com/smallrye/smallrye-fault-tolerance/compare/2.1.4...2.1.5 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12574) Documentation for SSH authentication for Git persistence

by James Perkins (Jira)

[ https://issues.redhat.com/browse/WFLY-12574?page=com.atlassian.jira.plugi... ] James Perkins updated WFLY-12574: --------------------------------- Fix Version/s: (was: 11.0.0.Beta1) > Documentation for SSH authentication for Git persistence > -------------------------------------------------------- > > Key: WFLY-12574 > URL: https://issues.redhat.com/browse/WFLY-12574 > Project: WildFly > Issue Type: Feature Request > Components: Management, Security > Reporter: Ashley Abdel-Sayed > Assignee: Ashley Abdel-Sayed > Priority: Major > > Currently Elytron only supports authentication for HTTP(s) URLS so there is no way to connect to a SSH git server to pull/push configuration history -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12950) [EAT] Multiversion Asynchronous EJB test

by James Perkins (Jira)

[ https://issues.redhat.com/browse/WFLY-12950?page=com.atlassian.jira.plugi... ] James Perkins commented on WFLY-12950: -------------------------------------- Is there a reason for a WFLY JIRA here? It seems odd as I'm not sure what release this would be associated with. > [EAT] Multiversion Asynchronous EJB test > ---------------------------------------- > > Key: WFLY-12950 > URL: https://issues.redhat.com/browse/WFLY-12950 > Project: WildFly > Issue Type: Task > Components: Test Suite > Reporter: Panagiotis Sotiropoulos > Assignee: Panagiotis Sotiropoulos > Priority: Major > > Multiversion Test for issue "Calling Asynchronous EJB will use the propagated caller transaction which is not according to the specification" -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 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 January 2020