April 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-4507) Fix Compiler Warnings in Mail Subsystem

by Philippe Marschall (JIRA)

Philippe Marschall created WFLY-4507: ---------------------------------------- Summary: Fix Compiler Warnings in Mail Subsystem Key: WFLY-4507 URL: https://issues.jboss.org/browse/WFLY-4507 Project: WildFly Issue Type: Patch Components: Mail Reporter: Philippe Marschall Assignee: Tomaz Cerar The mail subsystem contains several compiler warnings. Some of them (mostly related to generics) are quite easy to fix. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4506) Fix Compiler Warnings in JDR Subsystem

by Philippe Marschall (JIRA)

Philippe Marschall created WFLY-4506: ---------------------------------------- Summary: Fix Compiler Warnings in JDR Subsystem Key: WFLY-4506 URL: https://issues.jboss.org/browse/WFLY-4506 Project: WildFly Issue Type: Patch Components: JDR Reporter: Philippe Marschall Assignee: Jesse Jaggars The jdr subsystem contains three compiler warnings. Two of them (related to generics) are quite easy to fix. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4505) Fix Compiler Warnings in JAX-RS Subsystem

by Philippe Marschall (JIRA)

Philippe Marschall created WFLY-4505: ---------------------------------------- Summary: Fix Compiler Warnings in JAX-RS Subsystem Key: WFLY-4505 URL: https://issues.jboss.org/browse/WFLY-4505 Project: WildFly Issue Type: Patch Components: REST Reporter: Philippe Marschall Assignee: Stuart Douglas The jaxrs subsystem contains several compiler warnings. Some of them (mostly related to generics and unused variables) are quite easy to fix. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4504) Fix JGroups susbsystem remove

by Kabir Khan (JIRA)

Kabir Khan created WFLY-4504: -------------------------------- Summary: Fix JGroups susbsystem remove Key: WFLY-4504 URL: https://issues.jboss.org/browse/WFLY-4504 Project: WildFly Issue Type: Feature Request Components: Clustering Affects Versions: 9.0.0.Beta2 Reporter: Kabir Khan Assignee: Paul Ferraro Fix For: 9.0.0.CR1 Trying to remove the jgroups subsystem does not work: {code} [domain@localhost:9999 /] /profile=ha/subsystem=jgroups:remove { "outcome" => "failed", "failure-description" => {"domain-failure-description" => "WFLYCTL0216: Management resource '[ (\"profile\" => \"ha\"), (\"subsystem\" => \"jgroups\") ]' not found"}, "rolled-back" => true } {code} This appears to be because the subsystem remove handler adds steps to remove the child resources, and then removes the subsystem resource. So when the child removal steps are executed the parent/subsystem address is no longer there -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4504) Fix JGroups susbsystem remove

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4504?page=com.atlassian.jira.plugin.... ] Kabir Khan reassigned WFLY-4504: -------------------------------- Assignee: Kabir Khan (was: Paul Ferraro) > Fix JGroups susbsystem remove > ----------------------------- > > Key: WFLY-4504 > URL: https://issues.jboss.org/browse/WFLY-4504 > Project: WildFly > Issue Type: Feature Request > Components: Clustering > Affects Versions: 9.0.0.Beta2 > Reporter: Kabir Khan > Assignee: Kabir Khan > Fix For: 9.0.0.CR1 > > > Trying to remove the jgroups subsystem does not work: > {code} > [domain@localhost:9999 /] /profile=ha/subsystem=jgroups:remove > { > "outcome" => "failed", > "failure-description" => {"domain-failure-description" => "WFLYCTL0216: Management resource '[ > (\"profile\" => \"ha\"), > (\"subsystem\" => \"jgroups\") > ]' not found"}, > "rolled-back" => true > } > {code} > This appears to be because the subsystem remove handler adds steps to remove the child resources, and then removes the subsystem resource. So when the child removal steps are executed the parent/subsystem address is no longer there -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4503) Upgrade jberet-core to 1.1.0.Final

by Cheng Fang (JIRA)

Cheng Fang created WFLY-4503: -------------------------------- Summary: Upgrade jberet-core to 1.1.0.Final Key: WFLY-4503 URL: https://issues.jboss.org/browse/WFLY-4503 Project: WildFly Issue Type: Component Upgrade Components: Batch Affects Versions: 9.0.0.Beta2 Reporter: Cheng Fang Assignee: James Perkins Priority: Critical Fix For: 9.0.0.CR1 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2456) Bad permissions on properties files when using add-user.bat for results in "JBAS015234: No mgmt-groups.properties files found"

by R Gaisford (JIRA)

[ https://issues.jboss.org/browse/WFLY-2456?page=com.atlassian.jira.plugin.... ] R Gaisford commented on WFLY-2456: ---------------------------------- I'm a first time contributor/developer, I'm interested in looking into this issue. > Bad permissions on properties files when using add-user.bat for results in "JBAS015234: No mgmt-groups.properties files found" > ------------------------------------------------------------------------------------------------------------------------------ > > Key: WFLY-2456 > URL: https://issues.jboss.org/browse/WFLY-2456 > Project: WildFly > Issue Type: Bug > Components: Scripts > Affects Versions: 8.0.0.Beta1 > Environment: Windows 7, 32-bit, jdk1.7.0_45 > Reporter: John Lusk > Fix For: Awaiting Volunteers > > > Just getting started w/Wildfly after a long absence from Java. Fresh download, trying to hit admin console, got instructed to use add-user to add an admin user. > c:\usr\local\wildfly-8.0.0.Beta1\bin>.\add-user.bat > What type of user do you wish to add? > a) Management User (mgmt-users.properties) > b) Application User (application-users.properties) > (a): a > * Error * > JBAS015234: No mgmt-groups.properties files found. > Press any key to continue . . . > c:\usr\local\wildfly-8.0.0.Beta1\bin>echo %JBOSS_HOME% > C:\usr\local\wildfly-8.0.0.Beta1 > c:\usr\local\wildfly-8.0.0.Beta1\bin>echo %JAVA_HOME% > C:\java\jdk1.7.0_45 > c:\usr\local\wildfly-8.0.0.Beta1\bin>echo %M2_HOME% > C:\usr\local\Maven\3.1.1 > c:\usr\local\wildfly-8.0.0.Beta1\bin>mvn -version > Apache Maven 3.1.1 (0728685237757ffbf44136acec0402957f723d9a; 2013-09-17 11:22:2 > 2-0400) > Maven home: C:\usr\local\Maven\3.1.1 > Java version: 1.7.0_45, vendor: Oracle Corporation > Java home: C:\java\jdk1.7.0_45\jre > Default locale: en_US, platform encoding: Cp1252 > OS name: "windows 7", version: "6.1", arch: "x86", family: "windows" > c:\usr\local\wildfly-8.0.0.Beta1\bin> -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-85) Remove non socket-binding attributes from management interfaces

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-85?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated WFCORE-85: ----------------------------------- Git Pull Request: https://github.com/wildfly/wildfly-core/pull/553 (was: https://github.com/wildfly/wildfly-core/pull/552) > Remove non socket-binding attributes from management interfaces > --------------------------------------------------------------- > > Key: WFCORE-85 > URL: https://issues.jboss.org/browse/WFCORE-85 > Project: WildFly Core > Issue Type: Task > Components: Domain Management > Reporter: Tomaz Cerar > Assignee: Tomaz Cerar > > Remove HttpManagementResourceDefinition#http-port, https-port, interface, secure-interface > as this ware replaced by socket-binding and secure-socket-binding around 7.0 time frame. > Given that it only adds complexity and no real added value they should be removed as disscussed. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-511) "Reload" support for embedded server

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-511?page=com.atlassian.jira.plugin... ] Brian Stansberry reassigned WFCORE-511: --------------------------------------- Assignee: Brian Stansberry Fix Version/s: 1.0.0.Beta1 Resolution: Done > "Reload" support for embedded server > ------------------------------------ > > Key: WFCORE-511 > URL: https://issues.jboss.org/browse/WFCORE-511 > Project: WildFly Core > Issue Type: Feature Request > Components: Server > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 1.0.0.Beta1 > > > The current embedded server stuff doesn't handle a server reload. It creates a ModelControllerClient and then holds it forever. But the ModelController backed by that MCC will be invalid after a reload. > Key thing is to register a listener with the ControlledProcessStateService, and in callbacks deal with the reload and establish a new MCC. Nice to have is to make the MCC returned by StandaloneServer.getModelControllerClient() a facade that delegates to whatever the current "live" MCC is. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ELY-176) HTTP AuthenticationMechanism Factory and Provider registration.

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELY-176: ------------------------------------ Summary: HTTP AuthenticationMechanism Factory and Provider registration. Key: ELY-176 URL: https://issues.jboss.org/browse/ELY-176 Project: WildFly Elytron Issue Type: Sub-task Components: HTTP Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.0.0.Alpha1 We are for now going to need to be Undertow specific unless we come up with a solution for a generic API/SPI to be implemented by HTTP mechanisms that also gives access to the request / response. This task is to define a factory SPI and to make all known HTTP mechanisms available using this SPI. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 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 April 2015