February 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-1805) It should be possible to pass objects via invocation context from the server side EJB to the client and read with a via client side interceptor

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-1805?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated WFLY-1805: ------------------------------------------ Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1422216 Bugzilla Update: Perform > It should be possible to pass objects via invocation context from the server side EJB to the client and read with a via client side interceptor > ----------------------------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-1805 > URL: https://issues.jboss.org/browse/WFLY-1805 > Project: WildFly > Issue Type: Bug > Components: EJB > Reporter: Wolf-Dieter Fink > Assignee: David Lloyd > Labels: ejb > > With former JBoss versions it was possible to pass context beside the method invocation from the client to the server and back. This was done via (AOP) interceptors. > Since AS7 and WildFly the only possibility is to pass such context from the client to the server. > It should also possible to pass serializeable objects from the server side to the client if the invocation returns and have a client side interceptor to read that informations. > This was used to return i.e. tracking or additional usefull informations. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7980) Upgrade mod_cluster to 1.3.6.CR2

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-7980?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-7980: --------------------------------- Description: https://issues.jboss.org/projects/MODCLUSTER/versions/12333488 > Upgrade mod_cluster to 1.3.6.CR2 > -------------------------------- > > Key: WFLY-7980 > URL: https://issues.jboss.org/browse/WFLY-7980 > Project: WildFly > Issue Type: Component Upgrade > Components: mod_cluster > Affects Versions: 10.1.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > > https://issues.jboss.org/projects/MODCLUSTER/versions/12333488 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8130) Upgrade WildFly Transaction Client to 1.0.0.Beta14

by Darran Lofthouse (JIRA)

Darran Lofthouse created WFLY-8130: -------------------------------------- Summary: Upgrade WildFly Transaction Client to 1.0.0.Beta14 Key: WFLY-8130 URL: https://issues.jboss.org/browse/WFLY-8130 Project: WildFly Issue Type: Component Upgrade Components: Transactions Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 11.0.0.Alpha1 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2300) ReadResourceNameOperationStepHandler does not check if the resource exists before returning the resource name

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2300?page=com.atlassian.jira.plugi... ] James Perkins moved JBEAP-8868 to WFCORE-2300: ---------------------------------------------- Project: WildFly Core (was: JBoss Enterprise Application Platform) Key: WFCORE-2300 (was: JBEAP-8868) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Domain Management (was: Domain Management) (was: User Experience) Affects Version/s: (was: 7.1.0.DR7) > ReadResourceNameOperationStepHandler does not check if the resource exists before returning the resource name > ------------------------------------------------------------------------------------------------------------- > > Key: WFCORE-2300 > URL: https://issues.jboss.org/browse/WFCORE-2300 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: James Perkins > Assignee: James Perkins > Priority: Minor > > Trying to read the {{category}} attribute on a nonexistent logger results in success: > {code} > [standalone@localhost:9990 /] /subsystem=logging/logger=aaaaaa:read-attribute(name=category) > { > "outcome" => "success", > "result" => "aaaaaa" > } > {code} > Any other attributes can't be read and the operation correctly fails, e.g.: > {code} > [standalone@localhost:9990 /] /subsystem=logging/logger=aaaaaab:read-attribute(name=level > { > "outcome" => "failed", > "failure-description" => "WFLYCTL0216: Management resource '[ > (\"subsystem\" => \"logging\"), > (\"logger\" => \"aaaaaab\") > ]' not found", > "rolled-back" => true > } > {code} > This behavior is confusing, the operation should fail for any attribute on a nonexistent logger. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1444) KieSession to implement java.lang.AutoCloseable

by tech meshter (JIRA)

tech meshter created DROOLS-1444: ------------------------------------ Summary: KieSession to implement java.lang.AutoCloseable Key: DROOLS-1444 URL: https://issues.jboss.org/browse/DROOLS-1444 Project: Drools Issue Type: Enhancement Components: core engine Affects Versions: 6.5.0.Final Reporter: tech meshter Assignee: Mario Fusco Priority: Minor Given the new Java 7 and 8 syntax features, it would be useful that KieSession (and maybe some other APIs that involve "disposability") to implement java.lang.AutoCloseable. The implementation can call directly the "dispose" method (unless I miss something) and over time dispose might become deprecated. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2076) Wrong options for auto-completion in realms of Elytron security-domain in CLI

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2076?page=com.atlassian.jira.plugi... ] Brian Stansberry resolved WFCORE-2076. -------------------------------------- Assignee: Tomaz Cerar (was: Brian Stansberry) Resolution: Done I'm going to guess this is fixed because of something Tomaz did. :) > Wrong options for auto-completion in realms of Elytron security-domain in CLI > ----------------------------------------------------------------------------- > > Key: WFCORE-2076 > URL: https://issues.jboss.org/browse/WFCORE-2076 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management, Server > Affects Versions: 3.0.0.Alpha12 > Reporter: Ondrej Lukas > Assignee: Tomaz Cerar > Labels: user_experience > Fix For: 3.0.0.Beta1 > > > Auto-completion for realm in realms of security-domain provides wrong options. In case when ldap-realm with name ldapName is defined in configuration then also option {{rity-realm.ldapName}} occurs in auto-completion options. I am not able to reproduce this issue with properties-realm. Take a look at Steps to Reproduce for more details. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1489) Expose (un)registerNotificationHandler() on OperationContext

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1489?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1489: ------------------------------------- Fix Version/s: 4.0.0.Alpha1 (was: 3.0.0.Beta3) I'm moving this to 4. If there's a clear need for it in 3, please let me know. > Expose (un)registerNotificationHandler() on OperationContext > ------------------------------------------------------------ > > Key: WFCORE-1489 > URL: https://issues.jboss.org/browse/WFCORE-1489 > Project: WildFly Core > Issue Type: Enhancement > Components: Domain Management > Reporter: Kabir Khan > Assignee: Jeff Mesnil > Fix For: 4.0.0.Alpha1 > > > Currently the only way to (un)register notifications is via the NotificationHandlerRegistration exposed by ModelController.getNotificationRegistry(). It would be nice to not have to install a service whose only purpose is to get hold of the ModelController from OSH's. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-377) The management API should provide a command to restart only all servers that are in state 'reload-required'

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-377?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-377: ------------------------------------ Fix Version/s: 4.0.0.Beta1 (was: 3.0.0.Beta3) > The management API should provide a command to restart only all servers that are in state 'reload-required' > ----------------------------------------------------------------------------------------------------------- > > Key: WFCORE-377 > URL: https://issues.jboss.org/browse/WFCORE-377 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: Wolf-Dieter Fink > Labels: cli, domain, management > Fix For: 4.0.0.Beta1 > > > After configuration changes via CLI batch it might be that different processes needs to be restarted. > It is possible to iterate over all servers and check it. > But I think it would be easier to have a command that restart all controllers and servers conditional to the 'relod required' state > - at domain level > - at host level > - at server level > command example : > :restart(ifRequired=true) > :reload(ifRequired=true) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-185) Api returns internal server error instead of not found for non-existing path

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-185?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-185: ------------------------------------ Fix Version/s: 4.0.0.Beta1 (was: 3.0.0.Beta3) > Api returns internal server error instead of not found for non-existing path > ---------------------------------------------------------------------------- > > Key: WFCORE-185 > URL: https://issues.jboss.org/browse/WFCORE-185 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Heiko Rupp > Assignee: Brian Stansberry > Labels: rhq > Fix For: 4.0.0.Beta1 > > > When I try to e.g. /subsystem=foo:read-resource the api returns a 500 internal server error. > In http-land, the return code for "not found" is normally 404. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7158) Working with multiple keys in key store

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/WFLY-7158?page=com.atlassian.jira.plugin.... ] Jan Kalina commented on WFLY-7158: ---------------------------------- As the KeyManagerFactory consume KeyStore, there is no reason/possibility to use CredentialReference here. Will add *alias-filter* to the key-manager instead. > Working with multiple keys in key store > --------------------------------------- > > Key: WFLY-7158 > URL: https://issues.jboss.org/browse/WFLY-7158 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Martin Choma > Assignee: Jan Kalina > Priority: Critical > Fix For: 11.0.0.Alpha1 > > > In case when 2 keys are present in keystore, then alias-filter (filtering into single key) on key-store resource has to be specified, otherwise key-manager can't be created. If user want to use keystore with multiple keys, user has to configure multiple key-store elements with specified alias-filter (filtering into single key). > That is pretty inconvinient. Probably introducing *alias attribute on key-manager* would be more intuitive solution to this situation. > {code} > /subsystem=elytron/key-managers=server:add(key-store=server,algorithm="SunX509",password=key-password) > {code} -- 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