October 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-11243) Update WildFlyCustomJtaPlatform#locateTransactionSynchronizationRegistry to use a direct reference to the TransactionSynchronizationRegistry

by Scott Marlow (Jira)

Scott Marlow created WFLY-11243: ----------------------------------- Summary: Update WildFlyCustomJtaPlatform#locateTransactionSynchronizationRegistry to use a direct reference to the TransactionSynchronizationRegistry Key: WFLY-11243 URL: https://issues.jboss.org/browse/WFLY-11243 Project: WildFly Issue Type: Feature Request Components: JPA / Hibernate Reporter: Scott Marlow Assignee: Scott Marlow -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3796) Incorrect Elytron permission class-name or module should throw exception

by Ilia Vassilev (Jira)

[ https://issues.jboss.org/browse/WFCORE-3796?page=com.atlassian.jira.plugi... ] Ilia Vassilev reassigned WFCORE-3796: ------------------------------------- Assignee: Ilia Vassilev > Incorrect Elytron permission class-name or module should throw exception > ------------------------------------------------------------------------ > > Key: WFCORE-3796 > URL: https://issues.jboss.org/browse/WFCORE-3796 > Project: WildFly Core > Issue Type: Bug > Components: Security > Affects Versions: 5.0.0.Alpha4 > Reporter: Ondrej Lukas > Assignee: Ilia Vassilev > Priority: Major > > When non-existent class-name or module (e.g. when there is a typo) is added to any Elytron permission mapper (constant-permission-mapper or simple-permission-mapper) then exception should be thrown. Otherwise it can result to situation when due to a typo some permission is granted to any identity instead of denying it - when permission in used on 'deny' side. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-466) Include registry.access.stage.redhat.com on B16

by Guilherme Baufaker Rêgo (Jira)

[ https://issues.jboss.org/browse/SWSQE-466?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo commented on SWSQE-466: ----------------------------------------------- Done! > Include registry.access.stage.redhat.com on B16 > ----------------------------------------------- > > Key: SWSQE-466 > URL: https://issues.jboss.org/browse/SWSQE-466 > Project: Kiali QE > Issue Type: Task > Reporter: Guilherme Baufaker Rêgo > Assignee: Guilherme Baufaker Rêgo > Priority: Major > > [~tmoreira] needs registry.access.stage.redhat.com to be included. > I will also include on the bladecenter inventories. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-466) Include registry.access.stage.redhat.com on B16

by Tiago Moreira Vieira (Jira)

[ https://issues.jboss.org/browse/SWSQE-466?page=com.atlassian.jira.plugin.... ] Tiago Moreira Vieira commented on SWSQE-466: -------------------------------------------- Please include istioci-registry.usersys.redhat.com (insecure). This is where the nightly builds are pushed. Once we get the message bus working, this is where you get the builds. > Include registry.access.stage.redhat.com on B16 > ----------------------------------------------- > > Key: SWSQE-466 > URL: https://issues.jboss.org/browse/SWSQE-466 > Project: Kiali QE > Issue Type: Task > Reporter: Guilherme Baufaker Rêgo > Assignee: Guilherme Baufaker Rêgo > Priority: Major > > [~tmoreira] needs registry.access.stage.redhat.com to be included. > I will also include on the bladecenter inventories. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3151) [DMN Designer] Decision Table: Improve contrast of Input- and OutputClause columns

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-3151?page=com.atlassian.jira.plugi... ] Michael Anstis commented on DROOLS-3151: ---------------------------------------- [~stetson.robinson] and the new (as yet undocumented) Test Scenario editor (Simulation Scenario editor?). The only area probably impacted is the Guided Decision Table editor. > [DMN Designer] Decision Table: Improve contrast of Input- and OutputClause columns > ---------------------------------------------------------------------------------- > > Key: DROOLS-3151 > URL: https://issues.jboss.org/browse/DROOLS-3151 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Affects Versions: 7.13.0.Final > Reporter: Edson Tirelli > Assignee: Michael Anstis > Priority: Major > Labels: VisualDesign, drools-tools > Attachments: GDT.png, dtable-column-colours.png > > > [~tirelli] requested greater visual contrast between {{InputClause}} and {{OutputClause}} columns. > {quote} > this is way too subtle, to be honest... can we get colours that are a bit more distinguishable? > {quote} > See the attached screenshot. > Additional note for clarity, goal is to: clearly differentiate between different blocks of columns (decision table: input column, output column plus possibly a third "general" type.) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-466) Include registry.access.stage.redhat.com on B16

by Guilherme Baufaker Rêgo (Jira)

Guilherme Baufaker Rêgo created SWSQE-466: --------------------------------------------- Summary: Include registry.access.stage.redhat.com on B16 Key: SWSQE-466 URL: https://issues.jboss.org/browse/SWSQE-466 Project: Kiali QE Issue Type: Task Reporter: Guilherme Baufaker Rêgo Assignee: Guilherme Baufaker Rêgo [~tmoreira] needs registry.access.stage.redhat.com to be included. I will also include on the bladecenter inventories. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-466) Include registry.access.stage.redhat.com on B16

by Guilherme Baufaker Rêgo (Jira)

[ https://issues.jboss.org/browse/SWSQE-466?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo updated SWSQE-466: ------------------------------------------ Sprint: Kiali Sprint #13 > Include registry.access.stage.redhat.com on B16 > ----------------------------------------------- > > Key: SWSQE-466 > URL: https://issues.jboss.org/browse/SWSQE-466 > Project: Kiali QE > Issue Type: Task > Reporter: Guilherme Baufaker Rêgo > Assignee: Guilherme Baufaker Rêgo > Priority: Major > > [~tmoreira] needs registry.access.stage.redhat.com to be included. > I will also include on the bladecenter inventories. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3151) [DMN Designer] Decision Table: Improve contrast of Input- and OutputClause columns

by Stetson Robinson (Jira)

[ https://issues.jboss.org/browse/DROOLS-3151?page=com.atlassian.jira.plugi... ] Stetson Robinson commented on DROOLS-3151: ------------------------------------------ Thanks [~manstis], [~bdellasc]. So from Brian's specs, looks like what will be updated are the colors for guided decision tables and DMN decision tables, correct? Just confirming I understand. > [DMN Designer] Decision Table: Improve contrast of Input- and OutputClause columns > ---------------------------------------------------------------------------------- > > Key: DROOLS-3151 > URL: https://issues.jboss.org/browse/DROOLS-3151 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Affects Versions: 7.13.0.Final > Reporter: Edson Tirelli > Assignee: Michael Anstis > Priority: Major > Labels: VisualDesign, drools-tools > Attachments: GDT.png, dtable-column-colours.png > > > [~tirelli] requested greater visual contrast between {{InputClause}} and {{OutputClause}} columns. > {quote} > this is way too subtle, to be honest... can we get colours that are a bit more distinguishable? > {quote} > See the attached screenshot. > Additional note for clarity, goal is to: clearly differentiate between different blocks of columns (decision table: input column, output column plus possibly a third "general" type.) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11233) allow EntityManager caching in the JPA container

by Scott Marlow (Jira)

[ https://issues.jboss.org/browse/WFLY-11233?page=com.atlassian.jira.plugin... ] Scott Marlow commented on WFLY-11233: ------------------------------------- Would be nice to also evaluate if JPA ThreadLocalStack could benefit from initializing with: ArrayDeque(1), as suggested by Jesper. > allow EntityManager caching in the JPA container > ------------------------------------------------ > > Key: WFLY-11233 > URL: https://issues.jboss.org/browse/WFLY-11233 > Project: WildFly > Issue Type: Enhancement > Components: JPA / Hibernate > Reporter: Scott Marlow > Assignee: Scott Marlow > Priority: Major > > It could be interesting to see if caching EntityManager instances (per EntityManagerFactory) could improve performance for applications, that could benefit from that. > The JPA 2.2 specification mentions the below, pay particular attention to the text "whether entity manager instances are sometimes reused" in section 7.8.2, also look at mention of [88]: > {quote} > 7.8 Requirements on the Container > 7.8.1 Application-managed Persistence Contexts > When application-managed persistence contexts are used, the container must instantiate the entity manager factory and expose it to the application via JNDI. The container might use internal APIs to create the entity manager factory, or it might use the PersistenceProvider.createContainerEntityManagerFactory method. However, the container is required to support third-party persistence providers, and in this case the container must use the PersistenceProvider.createContainerEntityManagerFactory method to create the entity manager factory and the EntityManagerFactory.close method to destroy the entity manager factory prior to shutdown (if it has not been previously closed by the application). > 7.8.2 Container Managed Persistence Contexts > The container is responsible for managing the lifecycle of container-managed persistence contexts, for injecting EntityManager references into web components and session bean and message-driven bean components, and for making EntityManager references available to direct lookups in JNDI. When operating with a third-party persistence provider, the container uses the contracts defined in section 7.9 to create and destroy container-managed persistence contexts. It is undefined whether a new entity manager instance is created for every persistence context, or whether entity manager instances are sometimes reused. Exactly how the container maintains the association between persistence context and JTA transaction is not defined. If a persistence context is already associated with a JTA transaction, the container uses that persistence context for subsequent invocations within the scope of that transaction, according to the semantics for persistence context propagation defined in section 7.6.4. > 7.9 Runtime Contracts between the Container and Persistence Provider > This section describes contracts between the container and the persistence provider for the pluggability of third-party persistence providers. Containers are required to support these pluggability contracts. [87] > 7.9.1 Container Responsibilities > For the management of a transaction-scoped persistence context, if there is no EntityManager already associated with the JTA transaction: > * The container creates a new entity manager by calling EntityManagerFactory.createEntityManager when the first invocation of an entity manager with PersistenceContextType.TRANSACTION occurs within the scope of a business method executing in the JTA transaction. > * After the JTA transaction has completed (either by transaction commit or rollback), the container closes the entity manager by calling EntityManager.close. [88] Note that the JTA transaction may rollback in a background thread (e.g., as a result of transaction timeout), in which case the container should arrange for the entity manager to be closed but the EntityManager.close method should not be concurrently invoked while the application is in an EntityManager invocation. > The container must throw the TransactionRequiredException if a transaction-scoped persistence context is used and the EntityManager persist, remove, merge, or refresh method is invoked when no transaction is active. > For stateful session beans with extended persistence contexts: > * The container creates an entity manager by calling EntityManagerFactory.createEntityManager when a stateful session bean is created that declares a dependency on an entity manager with PersistenceContextType.EXTENDED. (See section 7.6.3). > * The container closes the entity manager by calling EntityManager.close after the stateful session bean and all other stateful session beans that have inherited the same persistence context as the entity manager have been removed. > * When a business method of the stateful session bean is invoked, if the stateful session bean uses container managed transaction demarcation, and the entity manager is not already associated with the current JTA transaction, the container associates the entity manager with the current JTA transaction and, if the persistence context is of type SynchronizationType.SYNCHRONIZED, the container calls EntityManager.joinTransaction. If there is a different persistence context already associated with the JTA transaction, the container throws the EJBException. > * When a business method of the stateful session bean is invoked, if the stateful session bean uses bean managed transaction demarcation and a UserTransaction is begun within the method, the container associates the persistence context with the JTA transaction and, if the persistence context is of type SynchronizationType.SYNCHRONIZED, the container calls EntityManager.joinTransaction. > The container must throw the IllegalStateException if the application calls EntityManager.close on a container-managed entity manager. > [87] It is not required that these contracts be used when a third-party persistence provider is not used: the container might use these same APIs or its might use its own internal APIs. > [88] The container may choose to pool EntityManagers: it instead of creating and closing in each case, it may acquire one from its pool and call clear() on it. > {quote} > One challenge with introducing an entity manager (per EntityManagerFactory) cache, is knowing when to close EntityManagers after certain errors have occurred on the EntityManager: > * In [https://github.com/wildfly/wildfly/blob/master/jpa/subsystem/src/main/jav...], we can try to retrieve an entity manager from the cache (cache reference can be passed into the TransactionScopedEntityManager proxy constructor), if cache is empty, then create a new entity manager to return. > * In https://github.com/wildfly/wildfly/blob/master/jpa/subsystem/src/main/jav..., if caching is enabled, we should call EntityManager.clear(), instead of EntityManager.close(), however, if an exception is thrown (on call to em.clear()), the entity manager shouldn't be put in the cache, instead we can try to close it and log/ignore any further exception thrown by the call to em.close(). > * If an entity manager is in a bad state, we shouldn't place it back in the cache. This may really be the same as the previous bullet but I wanted to mention it as a separate bullet, since we may need to add more error checking for the persistence throwing exceptions in [https://github.com/wildfly/wildfly/blob/master/jpa/subsystem/src/main/jav...] or/and other places. > * In [https://github.com/wildfly/wildfly/blob/master/jpa/subsystem/src/main/jav...], if caching is enabled, we should call EntityManager.clear() instead of EntityManager.close(), however, if an exception is thrown (on call to em.clear()), the entity manager shouldn't be put in the cache, instead we can try to close it and log/ignore any any further exception thrown by the call to em.close(). > * Lastly, we should update [https://github.com/wildfly/wildfly/blob/master/jpa/subsystem/src/main/jav...], to deal with releasing the entity manager cache before calling entityManagerFactory.close(). Since, [https://docs.oracle.com/javaee/7/api/javax/persistence/EntityManagerFacto...] says that the entity managers will be closed automatically, we probably can just clear the cache of EntityManagers, instead of actually calling EntityManager.close() on each one in the cache. > * Also ensure that SynchronizationType is respected, so we don't mix SynchronizationType.UNSYNCHRONIZED + SynchronizationType.SYNCHRONIZED types. Perhaps we need a cache slot for each SynchronizationType. > EntityManager cache settings can be: > * No cache (default) > * ThreadLocal cache (only cached at the application thread level) > * Per EntityManagerFactory cache (cache is shared between multiple threads, so make it thread safe), this would need to be proven to be leak free (especially with CDI beans). Cache size would be configurable. > If EM leaks are a problem in the above, an alternative might be to only cache within JTA transactions, since we would then have control of the closing of the EntityManager. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11242) Provide builtin ParamConverter* classes for multi valued params

by Ron Sigal (Jira)

[ https://issues.jboss.org/browse/WFLY-11242?page=com.atlassian.jira.plugin... ] Ron Sigal moved JBEAP-15723 to WFLY-11242: ------------------------------------------ Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-11242 (was: JBEAP-15723) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Fix Version/s: 15.0.0.Alpha1 (was: 7.3.0.GA) > Provide builtin ParamConverter* classes for multi valued params > --------------------------------------------------------------- > > Key: WFLY-11242 > URL: https://issues.jboss.org/browse/WFLY-11242 > Project: WildFly > Issue Type: Feature Request > Reporter: Marek Kopecký > Assignee: Ron Sigal > Priority: Major > Fix For: 15.0.0.Alpha1 > > > This is follow up for RESTEASY-1746 and RESTEASY-1566. In these feature jiras, users needs to prepare custom ParamConverter* classes in deployment. > This feature should provide builtin ParamConverter* universal classes. > Some PoC is in [this commit|https://github.com/marekkopecky/Resteasy/commit/08e0eb6de206085593...] > Suitable annotations for end-point can parametrize converter behaviour. [~ron_sigal]'s proposal: > {noformat}Maybe annotations in > > public <T> ParamConverter<T> getConverter(Class<T> rawType, Type genericType, Annotation[] annotations; > could be used to generalize. E.g., > public Response conversion1(@QueryParam @Separator("&") List<MultiValueParamBuiltinMyObject1> q); > Even more general could be something like > public Response conversion1(@QueryParam @MultiSyntax(<regular expression/>) List<MultiValueParamBuiltinMyObject1> q) {{noformat} -- This message was sent by Atlassian Jira (v7.12.1#712002)

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