June 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-6814) Add outbound-socket-binding capability reference support for TCPPING.initial_hosts

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-6814?page=com.atlassian.jira.plugin.... ] Paul Ferraro closed WFLY-6814. ------------------------------ Resolution: Duplicate Issue Duplicate of WFLY-8655 > Add outbound-socket-binding capability reference support for TCPPING.initial_hosts > ---------------------------------------------------------------------------------- > > Key: WFLY-6814 > URL: https://issues.jboss.org/browse/WFLY-6814 > Project: WildFly > Issue Type: Feature Request > Components: Clustering > Affects Versions: 10.0.0.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JASSIST-267) ProxyFactory will not invoke MethodHandler on methods having same name declared in non-public parent classes

by Ning Zhang (JIRA)

Ning Zhang created JASSIST-267: ---------------------------------- Summary: ProxyFactory will not invoke MethodHandler on methods having same name declared in non-public parent classes Key: JASSIST-267 URL: https://issues.jboss.org/browse/JASSIST-267 Project: Javassist Issue Type: Bug Affects Versions: 3.21.0-GA, 3.22.0-CR1 Environment: Linux/Windows 7, Java 1.7 and 1.8 Reporter: Ning Zhang Assignee: Shigeru Chiba Priority: Critical Attachments: IssueMethodsHaveSameNameInParent.java As in the attachment, if there are multiple methods in non-public parent class,then the MethodHandler will not take effect. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-8903) Upgrade WildFly Transaction Client to 1.0.0.Beta24

by David Lloyd (JIRA)

David Lloyd created WFLY-8903: --------------------------------- Summary: Upgrade WildFly Transaction Client to 1.0.0.Beta24 Key: WFLY-8903 URL: https://issues.jboss.org/browse/WFLY-8903 Project: WildFly Issue Type: Component Upgrade Reporter: David Lloyd Assignee: David Lloyd Fix For: 11.0.0.Beta1 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-8782) Reenable RemoteIdentityTestCase in AS TS with elytron profile

by Josef Cacek (JIRA)

[ https://issues.jboss.org/browse/WFLY-8782?page=com.atlassian.jira.plugin.... ] Josef Cacek updated WFLY-8782: ------------------------------ Git Pull Request: https://github.com/wildfly/wildfly/pull/10069, https://github.com/wildfly/wildfly/pull/10075, https://github.com/wildfly/wildfly/pull/10161 (was: https://github.com/wildfly/wildfly/pull/10069, https://github.com/wildfly/wildfly/pull/10075) > Reenable RemoteIdentityTestCase in AS TS with elytron profile > ------------------------------------------------------------- > > Key: WFLY-8782 > URL: https://issues.jboss.org/browse/WFLY-8782 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Reporter: Josef Cacek > Assignee: Josef Cacek > Fix For: 11.0.0.Beta1 > > > The JBEAP-9744 is fixed, let's reenable regression tests. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-1606) Error: "write size larger than buffer can fit" when running test scenario in workbench

by Russell Morrisey (JIRA)

Russell Morrisey created DROOLS-1606: ---------------------------------------- Summary: Error: "write size larger than buffer can fit" when running test scenario in workbench Key: DROOLS-1606 URL: https://issues.jboss.org/browse/DROOLS-1606 Project: Drools Issue Type: Bug Components: kie server, tools Affects Versions: 6.5.0.Final Environment: KIE Drools Workbench - Distribution Wars-Version: 6.5.0.Final Apache Tomcat 9.0 (CLI startup), Windows 7 x64 H2 database Reporter: Russell Morrisey Assignee: Edson Tirelli Attachments: KIE WB write size error.png, KIE test scenario.png When I run a test scenario in the KIE Workbench, the test scenario completes normally, but after it's completed, I get a pop-up error dialog: _Unable to complete your request. The following exception occurred: write size larger than buffer can fit._ This looks like it may(?) be related to: https://issues.jboss.org/browse/RHBPMS-1475 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-160) Client authentication configuration by task

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/ELY-160?page=com.atlassian.jira.plugin.sy... ] David Lloyd resolved ELY-160. ----------------------------- Fix Version/s: (was: 1.1.0.CR1) Resolution: Rejected > Client authentication configuration by task > ------------------------------------------- > > Key: ELY-160 > URL: https://issues.jboss.org/browse/ELY-160 > Project: WildFly Elytron > Issue Type: Task > Components: API / SPI > Reporter: David Lloyd > Assignee: David Lloyd > > The authentication client needs support for multiple tasks, such as: > * {{connection}} - the authentication configuration applies to the connection itself > * {{request}} - the authentication configuration applies to activities interacting with services provided by the named peer > * {{*}} - the authentication configuration applies to all matching tasks > In this way, one can specify a separate configuration for initial connections versus normal requests on that connection. > Furthermore, a new authentication configuration type should then be added which allows a task configuration to be inherited to another task. For example: > * {{useConfiguration("<referenced-task>"}} - could specify that my current authentication configuration for the matched task should use the configuration assigned to the referenced task, for example "connection", which would in turn mean that the connection credentials should be used (whatever they may be) for the given task/match criteria. > This allows a simple default configuration which allows connection credentials to be used whenever they are available. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-2042) Improve query operation for nested child resources

by Michal Petrov (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2042?page=com.atlassian.jira.plugi... ] Michal Petrov commented on WFCORE-2042: --------------------------------------- (I "stole" the name from SQL, I don't think it's confusing and it doesn't have to be called that) I feel like changing how "where" works makes the operation behave significantly differently for different queries. As it is now {code} ADDRESS:query(select=[a], where={b=c}) {code} performs read-resource on ADDRESS and if the condition is met removes all attributes from the result except for "a". So first "where" filters out the resource as a whole and then "select" filters its attributes (and they work independently of each other). Changing "where" to look into nested attributes would create a dependency between the two because select would also have to filter out the children that don't meet the "where" condition (in cases where the attribute is a list). I'm proposing simply shifting the scope of the operation from the parent resource to its attribute (that otherwise isn't addressable). > Improve query operation for nested child resources > -------------------------------------------------- > > Key: WFCORE-2042 > URL: https://issues.jboss.org/browse/WFCORE-2042 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: Lin Gao > > This is another similar RFE as WFCORE-2041. > It would be good if the 'query()' operation can filter the resources by specifying value of attributes which are +inside of nested child resources(not only by the first level of child resource)+, so that, for example, the following command can work well as expected: > {code:} > [standalone@localhost:9990 /] /subsystem=security:query(select=[security-domain], where={security-domain.authentication.login-modules.code=RealmDirect}) > { > "outcome" => "success", > "result" => undefined > } > // here the expected output are the security-domain resources which have the loging-module RealmDirect defined. > {code} > The {{security-domain.authentication.login-modules.code}} in 'where' parameter is proposed attribute name in enhanced syntax, other options maybe possible. > The different requirements between this WFCORE-2042 and WFCORE-2041 are: > * WFCORE-2041 focus on complex attributes in one management resource > * WFCORE-2042 focus on nested management resources with or without complex attributes -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-2911) Upgrade WildFly Elytron to 1.1.0.Beta51

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2911?page=com.atlassian.jira.plugi... ] Darran Lofthouse updated WFCORE-2911: ------------------------------------- Fix Version/s: 3.0.0.Beta25 > Upgrade WildFly Elytron to 1.1.0.Beta51 > --------------------------------------- > > Key: WFCORE-2911 > URL: https://issues.jboss.org/browse/WFCORE-2911 > Project: WildFly Core > Issue Type: Component Upgrade > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 3.0.0.Beta25 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-2911) Upgrade WildFly Elytron to 1.1.0.Beta51

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2911?page=com.atlassian.jira.plugi... ] Darran Lofthouse updated WFCORE-2911: ------------------------------------- Component/s: Security > Upgrade WildFly Elytron to 1.1.0.Beta51 > --------------------------------------- > > Key: WFCORE-2911 > URL: https://issues.jboss.org/browse/WFCORE-2911 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 3.0.0.Beta25 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1031) Make the CredentialStore class final

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1031?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1031: ---------------------------------- Fix Version/s: 1.1.0.Beta52 (was: 1.1.0.Beta51) > Make the CredentialStore class final > ------------------------------------ > > Key: ELY-1031 > URL: https://issues.jboss.org/browse/ELY-1031 > Project: WildFly Elytron > Issue Type: Enhancement > Components: Credential Store > Reporter: Darran Lofthouse > Assignee: Peter Skopek > Priority: Critical > Fix For: 1.1.0.Beta52 > > > Unless there is a reason this has not already be done the class should probably be made final to be sure extension is not possible. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

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