February 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-1430) DMN Model nodes to reference origin XML location, also to improve Validation

by Matteo Mortari (JIRA)

Matteo Mortari created DROOLS-1430: -------------------------------------- Summary: DMN Model nodes to reference origin XML location, also to improve Validation Key: DROOLS-1430 URL: https://issues.jboss.org/browse/DROOLS-1430 Project: Drools Issue Type: Enhancement Reporter: Matteo Mortari Assignee: Matteo Mortari For each DMN Model node provide the XML origin. This shall in turn provide more helpful information during DMN Validation. This also requires for the validation rules to always reference the original source model object -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8063) When a looked up service is modified it should use the OperationContext.getServiceRegistry(true)

by James Perkins (JIRA)

James Perkins created WFLY-8063: ----------------------------------- Summary: When a looked up service is modified it should use the OperationContext.getServiceRegistry(true) Key: WFLY-8063 URL: https://issues.jboss.org/browse/WFLY-8063 Project: WildFly Issue Type: Bug Components: Security Reporter: James Perkins Assignee: James Perkins In cases where a service is looked up in the {{OperationContext.getServiceRegistry()}} and the service is modified the registry should be looked up with {{true}} for the modifiable parameter. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7796) Java EE 7 API: unable to validate expressions with method invocations

by Dmitrii Tikhomirov (JIRA)

[ https://issues.jboss.org/browse/WFLY-7796?page=com.atlassian.jira.plugin.... ] Dmitrii Tikhomirov commented on WFLY-7796: ------------------------------------------ proposed solution: https://github.com/treblereel/jboss-jsf-api_spec/commit/19738f4eadf2987b1... > Java EE 7 API: unable to validate expressions with method invocations > --------------------------------------------------------------------- > > Key: WFLY-7796 > URL: https://issues.jboss.org/browse/WFLY-7796 > Project: WildFly > Issue Type: Bug > Components: JSF > Affects Versions: 10.1.0.Final > Reporter: Markus Pollak > Assignee: Dmitrii Tikhomirov > > Hello, > I’ve found a bug in the javaee-api-7.0.jar: > *Problem:* > javax.faces.validator.ValueExpressionAnalyzer$InterceptingResolver should also override (and delegate) the method "invoke" from ELResolver otherwise the BeanValidator wouldn’t support expressions with method invocations (e.g. #{exampleBean.anyMethod(anyParam).value}. Currently it doesn’t override the method so the default implementation is taken which returns null and leads to problems… > Best Regards, > Markus Pollak -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7796) Java EE 7 API: Bug in javaee-api-7.0.jar

by Dmitrii Tikhomirov (JIRA)

[ https://issues.jboss.org/browse/WFLY-7796?page=com.atlassian.jira.plugin.... ] Dmitrii Tikhomirov reassigned WFLY-7796: ---------------------------------------- Assignee: Dmitrii Tikhomirov (was: Farah Juma) > Java EE 7 API: Bug in javaee-api-7.0.jar > ---------------------------------------- > > Key: WFLY-7796 > URL: https://issues.jboss.org/browse/WFLY-7796 > Project: WildFly > Issue Type: Bug > Components: JSF > Affects Versions: 10.1.0.Final > Reporter: Markus Pollak > Assignee: Dmitrii Tikhomirov > > Hello, > I’ve found a bug in the javaee-api-7.0.jar: > *Problem:* > javax.faces.validator.ValueExpressionAnalyzer$InterceptingResolver should also override (and delegate) the method "invoke" from ELResolver otherwise the BeanValidator wouldn’t support expressions with method invocations (e.g. #{exampleBean.anyMethod(anyParam).value}. Currently it doesn’t override the method so the default implementation is taken which returns null and leads to problems… > Best Regards, > Markus Pollak -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7796) Java EE 7 API: unable to validate expressions with method invocations

by Dmitrii Tikhomirov (JIRA)

[ https://issues.jboss.org/browse/WFLY-7796?page=com.atlassian.jira.plugin.... ] Dmitrii Tikhomirov updated WFLY-7796: ------------------------------------- Summary: Java EE 7 API: unable to validate expressions with method invocations (was: Java EE 7 API: Bug in javaee-api-7.0.jar) > Java EE 7 API: unable to validate expressions with method invocations > --------------------------------------------------------------------- > > Key: WFLY-7796 > URL: https://issues.jboss.org/browse/WFLY-7796 > Project: WildFly > Issue Type: Bug > Components: JSF > Affects Versions: 10.1.0.Final > Reporter: Markus Pollak > Assignee: Dmitrii Tikhomirov > > Hello, > I’ve found a bug in the javaee-api-7.0.jar: > *Problem:* > javax.faces.validator.ValueExpressionAnalyzer$InterceptingResolver should also override (and delegate) the method "invoke" from ELResolver otherwise the BeanValidator wouldn’t support expressions with method invocations (e.g. #{exampleBean.anyMethod(anyParam).value}. Currently it doesn’t override the method so the default implementation is taken which returns null and leads to problems… > Best Regards, > Markus Pollak -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8062) Some OSH's in the Elytron subsystem don't validate the server type before registering steps

by James Perkins (JIRA)

James Perkins created WFLY-8062: ----------------------------------- Summary: Some OSH's in the Elytron subsystem don't validate the server type before registering steps Key: WFLY-8062 URL: https://issues.jboss.org/browse/WFLY-8062 Project: WildFly Issue Type: Bug Components: Security Reporter: James Perkins Assignee: James Perkins Priority: Blocker Fix For: 11.0.0.Alpha1 In the Elytron subsystem there are implementations of {{org.jboss.as.controller.OperationStepHandler}} that do not check the state of the {{OperationContext}} before registering runtime steps. This is an issue for domain servers as the steps will be registered on the host-controller even if the operations is being executed on a profile. For example: {code:java} @Override public void execute(OperationContext context, ModelNode operation) throws OperationFailedException { context.addStep(operation, (parentContext, parentOperation) -> { ModifiableRealmIdentity realmIdentity = getRealmIdentity(parentContext); List<ModelNode> modelNodes = parentOperation.asList(); Property passwordProperty = modelNodes.get(2).asProperty(); PathAddress currentAddress = parentContext.getCurrentAddress(); String principalName = currentAddress.getLastElement().getValue(); try { realmIdentity.setCredentials(Collections.singleton(new PasswordCredential(createPassword(parentContext, principalName, passwordProperty)))); } catch (NoSuchAlgorithmException | InvalidKeySpecException | RealmUnavailableException e) { throw ROOT_LOGGER.couldNotCreatePassword(e); } parentContext.completeStep(NOOP_RESULT_HANDLER); }, OperationContext.Stage.RUNTIME); } {code} Should check the {{context.isDefaultRequiresRuntime()}}: {code:java} @Override public void execute(OperationContext context, ModelNode operation) throws OperationFailedException { if (context.isDefaultRequiresRuntime()) { context.addStep(operation, (parentContext, parentOperation) -> { ModifiableRealmIdentity realmIdentity = getRealmIdentity(parentContext); List<ModelNode> modelNodes = parentOperation.asList(); Property passwordProperty = modelNodes.get(2).asProperty(); PathAddress currentAddress = parentContext.getCurrentAddress(); String principalName = currentAddress.getLastElement().getValue(); try { realmIdentity.setCredentials(Collections.singleton(new PasswordCredential(createPassword(parentContext, principalName, passwordProperty)))); } catch (NoSuchAlgorithmException | InvalidKeySpecException | RealmUnavailableException e) { throw ROOT_LOGGER.couldNotCreatePassword(e); } parentContext.completeStep(NOOP_RESULT_HANDLER); }, OperationContext.Stage.RUNTIME); } } {code} The handlers should be analyzed to ensure they check the state before registering runtime steps. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8061) Support role mapping from jboss deployment descriptors in undertow subsystem

by Pedro Igor (JIRA)

Pedro Igor created WFLY-8061: -------------------------------- Summary: Support role mapping from jboss deployment descriptors in undertow subsystem Key: WFLY-8061 URL: https://issues.jboss.org/browse/WFLY-8061 Project: WildFly Issue Type: Enhancement Components: Security, Web (Undertow) Reporter: Pedro Igor Assignee: Darran Lofthouse Currently, role mapping from jboss-web.xml and jboss-app.xml are not taken into consideration when mapping roles for an identity in Elytron. This already being done by ejb subsystem, but we lack in web/undertow subsystem. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8060) Restore distributed SFSB cache key marshalling optimization

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-8060?page=com.atlassian.jira.plugin.... ] Paul Ferraro updated WFLY-8060: ------------------------------- Affects Version/s: No Release > Restore distributed SFSB cache key marshalling optimization > ----------------------------------------------------------- > > Key: WFLY-8060 > URL: https://issues.jboss.org/browse/WFLY-8060 > Project: WildFly > Issue Type: Bug > Components: Clustering, EJB > Affects Versions: No Release > Reporter: Paul Ferraro > Assignee: Paul Ferraro > > As part of EAP7-552, EJBs use a new SessionID implementation for which we don't currently have an externalizer. This causes Infinispan to unnecessarily marshal and send class descriptors for each cache operation. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8060) Restore distributed SFSB cache key marshalling optimization

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-8060?page=com.atlassian.jira.plugin.... ] Paul Ferraro moved JBEAP-8739 to WFLY-8060: ------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-8060 (was: JBEAP-8739) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Clustering EJB (was: Clustering) (was: EJB) > Restore distributed SFSB cache key marshalling optimization > ----------------------------------------------------------- > > Key: WFLY-8060 > URL: https://issues.jboss.org/browse/WFLY-8060 > Project: WildFly > Issue Type: Bug > Components: Clustering, EJB > Reporter: Paul Ferraro > Assignee: Paul Ferraro > > As part of EAP7-552, EJBs use a new SessionID implementation for which we don't currently have an externalizer. This causes Infinispan to unnecessarily marshal and send class descriptors for each cache operation. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-31) CFME Tests: Adjust Datasource automation tests to 4.5 release.

by Hayk Hovsepyan (JIRA)

[ https://issues.jboss.org/browse/HAWKULARQE-31?page=com.atlassian.jira.plu... ] Hayk Hovsepyan commented on HAWKULARQE-31: ------------------------------------------ Blocked by https://bugzilla.redhat.com/show_bug.cgi?id=1420431 > CFME Tests: Adjust Datasource automation tests to 4.5 release. > -------------------------------------------------------------- > > Key: HAWKULARQE-31 > URL: https://issues.jboss.org/browse/HAWKULARQE-31 > Project: Hawkular QE > Issue Type: Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 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 2017