December 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-4560) Upgrade Narayana to version 5.1.1.Final

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4560?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-4560. ---------------------------- > Upgrade Narayana to version 5.1.1.Final > --------------------------------------- > > Key: WFLY-4560 > URL: https://issues.jboss.org/browse/WFLY-4560 > Project: WildFly > Issue Type: Component Upgrade > Components: Transactions > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 10.0.0.Alpha1 > > > Latest release of Narayana is available now. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5341) Example subsystem config is missing security manager subsystem

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-5341?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-5341. ---------------------------- > Example subsystem config is missing security manager subsystem > -------------------------------------------------------------- > > Key: WFLY-5341 > URL: https://issues.jboss.org/browse/WFLY-5341 > Project: WildFly > Issue Type: Bug > Components: Build System > Reporter: Stuart Douglas > Assignee: Stuart Douglas > Fix For: 10.0.0.CR1 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5264) Upgrade JBeret to 1.2.0.Final

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-5264?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-5264. ---------------------------- > Upgrade JBeret to 1.2.0.Final > ----------------------------- > > Key: WFLY-5264 > URL: https://issues.jboss.org/browse/WFLY-5264 > Project: WildFly > Issue Type: Component Upgrade > Components: Batch > Reporter: James Perkins > Assignee: James Perkins > Priority: Blocker > Fix For: 10.0.0.CR1 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3918) Cannot disable ConsoleRedirectService

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-3918?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-3918. ---------------------------- > Cannot disable ConsoleRedirectService > ------------------------------------- > > Key: WFLY-3918 > URL: https://issues.jboss.org/browse/WFLY-3918 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 8.1.0.Final > Reporter: Graham Johnson > Assignee: Tomaz Cerar > Fix For: 10.0.0.Alpha6 > > > Wildfly Undertow (via org.wildfly.extension.undertow.HostAdd and org.wildfly.extension.undertow.ConsoleRedirectService) redirects all /console/... URL requests (on port 8080/8443) to /console on port 9990. > This prevents developing or porting applications that themselves need to serve /console/... URLs. > There needs to be a way to disable (in the undertow subsystem configuration) the adding of ConsoleRedirectService by HostAdd. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5191) IronJacamar 1.2.6.Final

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-5191?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-5191. ---------------------------- > IronJacamar 1.2.6.Final > ----------------------- > > Key: WFLY-5191 > URL: https://issues.jboss.org/browse/WFLY-5191 > Project: WildFly > Issue Type: Component Upgrade > Reporter: Jesper Pedersen > Assignee: Jesper Pedersen > Priority: Critical > Fix For: 10.0.0.CR1 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5054) RemotingProfileRemove needs to extend AbstractRemoveStepHandler not ServiceRemoveStepHandler

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-5054?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-5054. ---------------------------- > RemotingProfileRemove needs to extend AbstractRemoveStepHandler not ServiceRemoveStepHandler > -------------------------------------------------------------------------------------------- > > Key: WFLY-5054 > URL: https://issues.jboss.org/browse/WFLY-5054 > Project: WildFly > Issue Type: Bug > Components: EJB > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Labels: affects_elytron > Fix For: 10.0.0.Beta1 > > > For some reason the class extends ServiceRemoveStepHandler but then replaces all of the functionality from that class. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5340) Unable to specify module when specifying custom JACC policy class.

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-5340?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-5340. ---------------------------- > Unable to specify module when specifying custom JACC policy class. > ------------------------------------------------------------------ > > Key: WFLY-5340 > URL: https://issues.jboss.org/browse/WFLY-5340 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 10.0.0.Beta2 > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 10.0.0.CR1 > > > It is currently possible to specify the 'javax.security.jacc.policy.provider' system property, however it is not possible to specify a module. > From the JACC specification: - > _For each JRE of a J2EE 1.4 or later version Java EE application server, if the > system property > “javax.security.jacc.policy.provider > ” is defined, > the application server must construct an > instance of the class identified by the > system property, confirm that the > resulting object is an instance of > java.security.Policy, > and set, by calling the > java.security.Policy.setPolicy > method, the resulting object as the > corresponding Policy object u > sed by the JRE. _ > The specification only specifies that the system property identifies the class, it does not specify how. > In it's simplest form we should assume this is just a class name, in a more complex form we should allow the module to be specified. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2833) data-source:enalbe and datasource:write-attribute(name=enabled, value=true) should have same result

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-2833?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-2833. ---------------------------- > data-source:enalbe and datasource:write-attribute(name=enabled, value=true) should have same result > --------------------------------------------------------------------------------------------------- > > Key: WFLY-2833 > URL: https://issues.jboss.org/browse/WFLY-2833 > Project: WildFly > Issue Type: Task > Components: JCA > Affects Versions: 10.0.0.Alpha4 > Reporter: Stefano Maestri > Assignee: Stefano Maestri > Fix For: 10.0.0.Beta1 > > > Currently enabled attribute always require a reload, while it should provide same functionalyity of :enable (and symmetric :disable operation) enabling/disabling datasource runtime. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5347) Upgrade HAL to 2.8.10.Final

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-5347?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-5347. ---------------------------- > Upgrade HAL to 2.8.10.Final > --------------------------- > > Key: WFLY-5347 > URL: https://issues.jboss.org/browse/WFLY-5347 > Project: WildFly > Issue Type: Component Upgrade > Components: Web Console > Reporter: Harald Pehl > Assignee: Harald Pehl > Fix For: 10.0.0.CR1 > > > New homepage and bugfixes -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3334) Event with qualifier @Initialized not raised if no webapp is deployed

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-3334?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-3334. ---------------------------- > Event with qualifier @Initialized not raised if no webapp is deployed > --------------------------------------------------------------------- > > Key: WFLY-3334 > URL: https://issues.jboss.org/browse/WFLY-3334 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld > Affects Versions: 8.1.0.CR1 > Environment: Wildfly 8.0.0.Final, OpenJDK 1.7.0_45 > Reporter: Daniel Lechner > Assignee: Jozef Hartinger > Fix For: 10.0.0.Alpha5 > > > As stated in the CDI-specification (section 6.7.3. Application context lifecycle) > {quote} > An event with qualifier @Initialized(ApplicationScoped.class) is fired when the application context is initialized and an event with qualifier @Destroyed(ApplicationScoped.class) is fired when the application is destroyed. > {quote} > But in my environment this is only true, if the deployed application (packaged in an EAR) contains a webapplication (as WAR inside the EAR). If there is no webapplication, the event is not raised and observer-methods are not called at all. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 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 December 2017