October 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-7209) Operation to list installed Resource Adapters

by Guillermo González de Agüero (JIRA)

[ https://issues.jboss.org/browse/WFLY-7209?page=com.atlassian.jira.plugin.... ] Guillermo González de Agüero updated WFLY-7209: ----------------------------------------------- Description: Currently there's no way to list all the deployed Resource Adapters (modules or deployed archives). I propose to add a new operation to list installed RAs and their configuration, similar to the one available for JDBC drivers (see attached screenshots). This would allow HAL to provide a wizard of available options when configuring them. The command would be something like: /subsystem=resource-adapters:installed-resource-adapters-list() was: Currently there's no way to list all the deployed Resource Adapters (modules or deployed archives). I propose to add a new operation to list installed RAs and their configuration, similar to the one available for JDBC drivers. This would allow HAL to provide a wizard of available options when configuring them. The command would be something like: /subsystem=resource-adapters:installed-resource-adapters-list() > Operation to list installed Resource Adapters > --------------------------------------------- > > Key: WFLY-7209 > URL: https://issues.jboss.org/browse/WFLY-7209 > Project: WildFly > Issue Type: Feature Request > Components: JCA > Reporter: Guillermo González de Agüero > Assignee: Stefano Maestri > Fix For: 10.1.0.Final > > Attachments: 1-jdbc.png, 2-ra.png > > > Currently there's no way to list all the deployed Resource Adapters (modules or deployed archives). I propose to add a new operation to list installed RAs and their configuration, similar to the one available for JDBC drivers (see attached screenshots). This would allow HAL to provide a wizard of available options when configuring them. > The command would be something like: /subsystem=resource-adapters:installed-resource-adapters-list() -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7209) Operation to list installed Resource Adapters

by Guillermo González de Agüero (JIRA)

[ https://issues.jboss.org/browse/WFLY-7209?page=com.atlassian.jira.plugin.... ] Guillermo González de Agüero updated WFLY-7209: ----------------------------------------------- Attachment: 2-ra.png 1-jdbc.png > Operation to list installed Resource Adapters > --------------------------------------------- > > Key: WFLY-7209 > URL: https://issues.jboss.org/browse/WFLY-7209 > Project: WildFly > Issue Type: Feature Request > Components: JCA > Reporter: Guillermo González de Agüero > Assignee: Stefano Maestri > Fix For: 10.1.0.Final > > Attachments: 1-jdbc.png, 2-ra.png > > > Currently there's no way to list all the deployed Resource Adapters (modules or deployed archives). I propose to add a new operation to list installed RAs and their configuration, similar to the one available for JDBC drivers. This would allow HAL to provide a wizard of available options when configuring them. > The command would be something like: /subsystem=resource-adapters:installed-resource-adapters-list() -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7209) Operation to list installed Resource Adapters

by Guillermo González de Agüero (JIRA)

[ https://issues.jboss.org/browse/WFLY-7209?page=com.atlassian.jira.plugin.... ] Guillermo González de Agüero updated WFLY-7209: ----------------------------------------------- Description: Currently there's no way to list all the deployed Resource Adapters (modules or deployed archives). I propose to add a new operation to list installed RAs and their configuration, similar to the one available for JDBC drivers. This would allow HAL to provide a wizard of available options when configuring them. The command would be something like: /subsystem=resource-adapters:installed-resource-adapters-list() was: Currently there's no way to list all the installed Resource Adapters. Only configured resource adapters can be queried. However, they are automatically enabled at deployment time. I propose to add a new operation to list installed RAs and their configuration, similar to the one available for JDBC drivers. This would allow HAL to provide a wizard of available options when configuring them. The command would be something like: /subsystem=resource-adapters:installed-resource-adapters-list() > Operation to list installed Resource Adapters > --------------------------------------------- > > Key: WFLY-7209 > URL: https://issues.jboss.org/browse/WFLY-7209 > Project: WildFly > Issue Type: Feature Request > Components: JCA > Reporter: Guillermo González de Agüero > Assignee: Stefano Maestri > Fix For: 10.1.0.Final > > > Currently there's no way to list all the deployed Resource Adapters (modules or deployed archives). I propose to add a new operation to list installed RAs and their configuration, similar to the one available for JDBC drivers. This would allow HAL to provide a wizard of available options when configuring them. > The command would be something like: /subsystem=resource-adapters:installed-resource-adapters-list() -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7251) Clustering API does not expose a proper capability contract

by Paul Ferraro (JIRA)

Paul Ferraro created WFLY-7251: ---------------------------------- Summary: Clustering API does not expose a proper capability contract Key: WFLY-7251 URL: https://issues.jboss.org/browse/WFLY-7251 Project: WildFly Issue Type: Bug Components: Clustering Affects Versions: 10.0.0.Final Reporter: Paul Ferraro Assignee: Paul Ferraro -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7250) Infinispan subsystem does not expose a proper capability contract

by Paul Ferraro (JIRA)

Paul Ferraro created WFLY-7250: ---------------------------------- Summary: Infinispan subsystem does not expose a proper capability contract Key: WFLY-7250 URL: https://issues.jboss.org/browse/WFLY-7250 Project: WildFly Issue Type: Bug Components: Clustering Affects Versions: 10.0.0.Final Reporter: Paul Ferraro Assignee: Paul Ferraro -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ELY-522) Add callbacks for persisting and restoring a SecurityIdentity

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-522?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse resolved ELY-522. ---------------------------------- Fix Version/s: 1.1.0.Beta10 (was: 1.1.0.Beta11) Resolution: Done > Add callbacks for persisting and restoring a SecurityIdentity > ------------------------------------------------------------- > > Key: ELY-522 > URL: https://issues.jboss.org/browse/ELY-522 > Project: WildFly Elytron > Issue Type: Enhancement > Components: HTTP > Reporter: Darran Lofthouse > Assignee: Pedro Igor > Priority: Critical > Fix For: 1.1.0.Beta10 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7247) Wildfly 10 JSESSIONIDSSOs not being created

by Jive JIRA Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-7247?page=com.atlassian.jira.plugin.... ] Jive JIRA Integration updated WFLY-7247: ---------------------------------------- Forum Reference: https://developer.jboss.org/message/962289#962289, https://developer.jboss.org/message/963592 (was: https://developer.jboss.org/message/963592) > Wildfly 10 JSESSIONIDSSOs not being created > ------------------------------------------- > > Key: WFLY-7247 > URL: https://issues.jboss.org/browse/WFLY-7247 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 10.0.0.Final, 10.1.0.Final > Reporter: M Wardell > Assignee: Jason Greene > > Found on wildfly 10.1 and 10.0. With SSO enabled, the server can startup in a state where not all the deployments get the SSO auth mechanism. Possibly caused by a missing dependency between the UndertowDeploymentInfoService and SingleSignOnService, which could be allowing the deployments to start before the SSO auth mechanism is registered in the host service. > Issue in intermittent on startup. After most startups the JESSSIONIDSSO is reliably generated during login. After some startups the JSESSIONIDSSO is never created after login. > Details in the referenced forum thread. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7247) Wildfly 10 JSESSIONIDSSOs not being created

by jaikiran pai (JIRA)

[ https://issues.jboss.org/browse/WFLY-7247?page=com.atlassian.jira.plugin.... ] jaikiran pai updated WFLY-7247: ------------------------------- Component/s: Web (Undertow) > Wildfly 10 JSESSIONIDSSOs not being created > ------------------------------------------- > > Key: WFLY-7247 > URL: https://issues.jboss.org/browse/WFLY-7247 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 10.0.0.Final, 10.1.0.Final > Reporter: M Wardell > Assignee: Jason Greene > > Found on wildfly 10.1 and 10.0. With SSO enabled, the server can startup in a state where not all the deployments get the SSO auth mechanism. Possibly caused by a missing dependency between the UndertowDeploymentInfoService and SingleSignOnService, which could be allowing the deployments to start before the SSO auth mechanism is registered in the host service. > Issue in intermittent on startup. After most startups the JESSSIONIDSSO is reliably generated during login. After some startups the JSESSIONIDSSO is never created after login. > Details in the referenced forum thread. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7248) [GSS](7.1.0) generic-jms-ra's JmsMCFProperties.getSessionDefaultType returns incorrect value for session type

by Brad Maxwell (JIRA)

Brad Maxwell created WFLY-7248: ---------------------------------- Summary: [GSS](7.1.0) generic-jms-ra's JmsMCFProperties.getSessionDefaultType returns incorrect value for session type Key: WFLY-7248 URL: https://issues.jboss.org/browse/WFLY-7248 Project: WildFly Issue Type: Bug Components: JMS Affects Versions: 10.1.0.Final Reporter: Brad Maxwell Assignee: Tom Ross The code snippet shows that the method returns wrong type. {noformat} public String getSessionDefaultType() { if (type == JmsConnectionFactory.AGNOSTIC) return "agnostic"; else if (type == JmsConnectionFactory.QUEUE) return TOPIC_TYPE; else return QUEUE_TYPE; } {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7249) [GSS](7.0.z) generic-jms-ra's JmsMCFProperties.getSessionDefaultType returns incorrect value for session type

by Brad Maxwell (JIRA)

Brad Maxwell created WFLY-7249: ---------------------------------- Summary: [GSS](7.0.z) generic-jms-ra's JmsMCFProperties.getSessionDefaultType returns incorrect value for session type Key: WFLY-7249 URL: https://issues.jboss.org/browse/WFLY-7249 Project: WildFly Issue Type: Bug Components: JMS Affects Versions: 10.1.0.Final Reporter: Brad Maxwell Assignee: Tom Ross The code snippet shows that the method returns wrong type. {noformat} public String getSessionDefaultType() { if (type == JmsConnectionFactory.AGNOSTIC) return "agnostic"; else if (type == JmsConnectionFactory.QUEUE) return TOPIC_TYPE; else return QUEUE_TYPE; } {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2016