September 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-7133) Automatically define resource adapter for deployed RARs

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

[ https://issues.jboss.org/browse/WFLY-7133?page=com.atlassian.jira.plugin.... ] Guillermo González de Agüero commented on WFLY-7133: ---------------------------------------------------- [~jthoennes] Yes, but you have to manually define it in the subsystem in order to see it. And for that you have to manually configure it. And if it comes with an ironjacamar.xml, it doesn't make sense to manually reconfigure it, potentially with different and wrong settings. But I guess what I requested is not technically viable at all. If the adapter would be created at deployment time, it would also need to be deleted when undeploying. Doesn't seem very robust. I created the ticket before checking how the JDBC drivers par work. After that I realized that the new operation I mention could do the trick. I've created WFLY-7209 for that. > Automatically define resource adapter for deployed RARs > ------------------------------------------------------- > > Key: WFLY-7133 > URL: https://issues.jboss.org/browse/WFLY-7133 > Project: WildFly > Issue Type: Feature Request > Components: JCA > Affects Versions: 10.1.0.Final > Reporter: Guillermo González de Agüero > Assignee: Jesper Pedersen > > Deploying a RAR file enables the resource adapter for the server, but in order to configure it, you must manually add it to the Resource Adapters subsystem. This is error prone (you can put in invalid "archive name" for the resource adapter and it doesn't complaint) and little user friendly. > From a user perspective and from what can be read from the documentation (https://docs.jboss.org/author/display/WFLY10/Resource+adapters), it seems like the resource adapter is not enabled unless you explicitly define it. > It would be very simpler if RA deployments would be detected and registered as it's done for deployed JDBC drivers. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

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

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

Guillermo González de Agüero created WFLY-7209: -------------------------------------------------- Summary: 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: Jesper Pedersen Fix For: 10.1.0.Final 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() -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4763) Include org.jboss.invocation in group ids that are synced to Maven central

by jaikiran pai (JIRA)

[ https://issues.jboss.org/browse/WFLY-4763?page=com.atlassian.jira.plugin.... ] jaikiran pai resolved WFLY-4763. -------------------------------- Resolution: Done I now see this artifact in Maven central https://repo1.maven.org/maven2/org/jboss/invocation/jboss-invocation/, marking this as resolved. > Include org.jboss.invocation in group ids that are synced to Maven central > -------------------------------------------------------------------------- > > Key: WFLY-4763 > URL: https://issues.jboss.org/browse/WFLY-4763 > Project: WildFly > Issue Type: Enhancement > Components: Build System > Reporter: jaikiran pai > Assignee: Paul Gier > > The jboss-invocation module under the org.jboss.invocation group (https://github.com/jbossas/jboss-invocation/ - project home) isn't available in Maven central unlike most of the other org.jboss projects. > jboss-invocation is part of WildFly dependencies. Please include the org.jboss.invocation group id in the groups that are synced to Maven central. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7120) NPE in SessionManagerStatsHandler

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-7120?page=com.atlassian.jira.plugin.... ] Brian Stansberry reassigned WFLY-7120: -------------------------------------- Assignee: Tomaz Cerar (was: Brian Stansberry) Tomaz, could you look into this and make sure JBEAP-6026 gets in the right state or a new one is opened if there's further change? > NPE in SessionManagerStatsHandler > --------------------------------- > > Key: WFLY-7120 > URL: https://issues.jboss.org/browse/WFLY-7120 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 10.1.0.Final > Reporter: Brian Stansberry > Assignee: Tomaz Cerar > Fix For: 11.0.0.Alpha1 > > > [~matlach] reports an NPE when SessionManagerStatsHandler tries to use the ServiceController for a no-longer present deployment. See https://github.com/wildfly/wildfly/pull/9189 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

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

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-7202?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-7202: ----------------------------------------------- Tom Ross <tom.ross(a)redhat.com> changed the Status of [bug 1378723|https://bugzilla.redhat.com/show_bug.cgi?id=1378723] from NEW to ASSIGNED > generic-jms-ra's JmsMCFProperties.getSessionDefaultType returns incorrect value for session type > ------------------------------------------------------------------------------------------------ > > Key: WFLY-7202 > URL: https://issues.jboss.org/browse/WFLY-7202 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 10.1.0.Final > Reporter: Tom Ross > 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)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1821) Failures in ModuleOpsCompletionTestCase

by Brian Stansberry (JIRA)

Brian Stansberry created WFCORE-1821: ---------------------------------------- Summary: Failures in ModuleOpsCompletionTestCase Key: WFCORE-1821 URL: https://issues.jboss.org/browse/WFCORE-1821 Project: WildFly Core Issue Type: Bug Components: Test Suite Reporter: Brian Stansberry Assignee: ehsavoie Hugonnet Failed tests: ModuleOpsCompletionTestCase.testModuleAddCompletionSuggestions:56->testSuggestion:146->testSuggestion:153 expected:<[org, ibm, io, javax, org, sun]> but was:<[ibm, io, javax, org, sun]> There's already a PR that's probably meant to fix this but it isn't passing CI. I'm going to @Ignore this test. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1820) Use MRR-driven capability registration for the management interface capabilities

by Brian Stansberry (JIRA)

Brian Stansberry created WFCORE-1820: ---------------------------------------- Summary: Use MRR-driven capability registration for the management interface capabilities Key: WFCORE-1820 URL: https://issues.jboss.org/browse/WFCORE-1820 Project: WildFly Core Issue Type: Enhancement Components: Domain Management Reporter: Brian Stansberry Assignee: Brian Stansberry Priority: Minor Currently the registration of runtime capabilities for the management interfaces is being done in the add handlers instead of by the MRR. This is fragile as it's non-standard and makes it more difficult to add other capabilities, since registering via the handler turns off registration via the MRR. WFCORE-1819 is needed to fix this. This is arguably a bug but I'll call it an enhancement for now. It's just making the code better. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1819) Allow collections kept by SimpleResourceDefinition.Parameters to be appended

by Brian Stansberry (JIRA)

Brian Stansberry created WFCORE-1819: ---------------------------------------- Summary: Allow collections kept by SimpleResourceDefinition.Parameters to be appended Key: WFCORE-1819 URL: https://issues.jboss.org/browse/WFCORE-1819 Project: WildFly Core Issue Type: Enhancement Components: Domain Management Reporter: Brian Stansberry Assignee: Brian Stansberry The Parameters object is meant to be built with a builder and then passed into SimpleResourceDefinition constructors. It is useful for scenarios where RD's are based on subclassing to let the superclass *add* items to the passed in set of access constraints, capabilities and incorporating capabilities instead of forcing the subclass constructor itself to manually read existing values, create new collections with added values, and then re-set the overall collection. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ELY-642) Investigate Elytron and gssproxy interoperability

by Bilge Ozpeynirci (JIRA)

Bilge Ozpeynirci created ELY-642: ------------------------------------ Summary: Investigate Elytron and gssproxy interoperability Key: ELY-642 URL: https://issues.jboss.org/browse/ELY-642 Project: WildFly Elytron Issue Type: Task Components: SASL Reporter: Bilge Ozpeynirci Assignee: Peter Skopek Fix For: 2.0.0.Alpha1 Investigate Elytron and gssproxy interoperability. https://fedorahosted.org/gss-proxy/ -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1817) upgrade Xerces to 2.11.0.SP5

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1817?page=com.atlassian.jira.plugi... ] Scott Marlow closed WFCORE-1817. -------------------------------- > upgrade Xerces to 2.11.0.SP5 > ---------------------------- > > Key: WFCORE-1817 > URL: https://issues.jboss.org/browse/WFCORE-1817 > Project: WildFly Core > Issue Type: Task > Reporter: Scott Marlow > Assignee: Scott Marlow > Fix For: 3.0.0.Alpha9, 2.2.1.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 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 September 2016