February 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBFORUMS-109) BBCode support for standalone version

by Ryszard Kozmik (JIRA)

BBCode support for standalone version ------------------------------------- Key: JBFORUMS-109 URL: http://jira.jboss.com/jira/browse/JBFORUMS-109 Project: JBoss Forums Issue Type: Task Components: Forum Enhancements Reporter: Ryszard Kozmik Fix For: 1.0.0 Alpha BBCode parser is now working only in portal environment. We need make it work as a standalone too. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 hours, 13 minutes

4
5
0 / 0

[JBoss JIRA] Created: (JGRP-457) Optimization: make threads return immediately if NAKACK has another active thread for the same sender

by Bela Ban (JIRA)

Optimization: make threads return immediately if NAKACK has another active thread for the same sender ----------------------------------------------------------------------------------------------------- Key: JGRP-457 URL: http://jira.jboss.com/jira/browse/JGRP-457 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assigned To: Bela Ban Priority: Minor Fix For: 2.5 In NAKACK, when a thread places a message for sender S into the NakReceiverWindow NRW, it subsequently acquires a lock on NRW (lock by sender) and removes as many messages as possible and passes them up. If many threads do this at the same time, all threads but one are blocked, and - when finally unblocked - usually return. This causes context switches and possibly cache flushing, so a better way would be to have the threads check whether another thread is already removing messages using a CAS operation *before* acquiring the lock. The effect should be that no threads will wait on the lock unnecessarily, and thus fewer context switches, and more threads available to the pool. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

1 month, 2 weeks

2
3
0 / 0

[JBoss JIRA] (ELY-776) Eliminate reference to "slot" from module configurations

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-776?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse reassigned ELY-776: ------------------------------------ Assignee: Darran Lofthouse > Eliminate reference to "slot" from module configurations > -------------------------------------------------------- > > Key: ELY-776 > URL: https://issues.jboss.org/browse/ELY-776 > Project: WildFly Elytron > Issue Type: Enhancement > Components: Authentication Client > Reporter: David Lloyd > Assignee: Darran Lofthouse > Fix For: 1.1.0.Beta15 > > > The final version of our client XSD should accept a name for modules but no slot. Instead, either the new name-only APIs should be used or a ModuleIdentifier created via that class's "fromString" method. Module slots are deprecated. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

2 months, 1 week

2
1
0 / 0

[JBoss JIRA] (JBRULES-3445) DSL expander expands lines in /* */comment block

by Mario Fusco (JIRA)

Mario Fusco created JBRULES-3445: ------------------------------------ Summary: DSL expander expands lines in /* */comment block Key: JBRULES-3445 URL: https://issues.jboss.org/browse/JBRULES-3445 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Mario Fusco Assignee: Mario Fusco When you comment some code in dslr file, the expander still tries to expand it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

7 months, 1 week

3
10
0 / 0

[JBoss JIRA] (WFCORE-1958) Clean up testsuite Elytron registration

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1958?page=com.atlassian.jira.plugi... ] Brian Stansberry commented on WFCORE-1958: ------------------------------------------ https://github.com/wildfly/wildfly-core/pull/2218 reenables the last @Ignored test, since it passes for me locally. > Clean up testsuite Elytron registration > --------------------------------------- > > Key: WFCORE-1958 > URL: https://issues.jboss.org/browse/WFCORE-1958 > Project: WildFly Core > Issue Type: Task > Components: Test Suite > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Blocker > Fix For: 3.0.0.Beta7 > > > In a couple of places we have artificially registered the WildFly Elytron Security provider, we need to address this so tests can automatically have it available to them.. > Also re-enable the following test case: - > * org.jboss.as.test.integration.domain.suites.FullRbacProviderRunAsTestSuite -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8023) Autocomplete doesn't work properly in credential-reference.alias attribute.

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-8023?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated WFLY-8023: ----------------------------------- Issue Type: Enhancement (was: Bug) This is not information available to the CLI via any standard tab completion mechanism and thus is an RFE. > Autocomplete doesn't work properly in credential-reference.alias attribute. > --------------------------------------------------------------------------- > > Key: WFLY-8023 > URL: https://issues.jboss.org/browse/WFLY-8023 > Project: WildFly > Issue Type: Enhancement > Components: Security > Reporter: Hynek Švábek > Assignee: Peter Skopek > > Autocomplete doesn't work properly in credential-reference.alias attribute. > I want to use autocomplete for credential-reference.alias when I the credential-reference.store attribute is filled but it doesn't work. > *How to reproduce* > {code} > /subsystem=elytron/credential-store=cs1:add(uri="cr-store://test/cs1.jceks", credential-reference={store=cs012, alias=<TAB> > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3759) Make IP address of remote EJB client accessible to the developer from within app authentication code

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-3759?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated WFLY-3759: ----------------------------------- Component/s: EJB (was: Domain Management) > Make IP address of remote EJB client accessible to the developer from within app authentication code > ---------------------------------------------------------------------------------------------------- > > Key: WFLY-3759 > URL: https://issues.jboss.org/browse/WFLY-3759 > Project: WildFly > Issue Type: Feature Request > Components: EJB, Security > Reporter: Derek Horton > Assignee: Darran Lofthouse > > Make the IP address of remote EJB clients accessible from within a login module login module when the security-realm is configured to defer to JAAS. > This is possible when the authentication is handled by the security-realm, but it is not possible when the security-realm defers to a security-domain (JAAS). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2346) Revisit enforcement of required file system permissions.

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2346?page=com.atlassian.jira.plugi... ] Brian Stansberry moved WFLY-431 to WFCORE-2346: ----------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-2346 (was: WFLY-431) Component/s: Domain Management (was: Domain Management) > Revisit enforcement of required file system permissions. > -------------------------------------------------------- > > Key: WFCORE-2346 > URL: https://issues.jboss.org/browse/WFCORE-2346 > Project: WildFly Core > Issue Type: Task > Components: Domain Management > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Labels: management_security, > > Now that AS8 has moved to Java 7 we can re-visit the level of control we have over file system permissions, this can be from taking more control of the local authentication mechanism to ensure incorrect permissions are not inherited to verifying sensitive configuration files are not world readable. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1457) Guided rules editor function field does not perform semantic validation

by Petr Široký (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1457?page=com.atlassian.jira.plugi... ] Petr Široký reassigned DROOLS-1457: ----------------------------------- Assignee: (was: Petr Široký) > Guided rules editor function field does not perform semantic validation > ----------------------------------------------------------------------- > > Key: DROOLS-1457 > URL: https://issues.jboss.org/browse/DROOLS-1457 > Project: Drools > Issue Type: Feature Request > Reporter: Kalyan gogineni > > guided rules editor function field does not perform semantic validation. > For example: when you define rules like below > When number 1 is not null > And number 2 is not null > Then number 3 = number5/number1 > Note: Where number5 is not defined. Then when you compile or build and deploy then drools does not throw error. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1457) Guided rules editor function field does not perform semantic validation

by Petr Široký (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1457?page=com.atlassian.jira.plugi... ] Petr Široký updated DROOLS-1457: -------------------------------- Component/s: (was: build) > Guided rules editor function field does not perform semantic validation > ----------------------------------------------------------------------- > > Key: DROOLS-1457 > URL: https://issues.jboss.org/browse/DROOLS-1457 > Project: Drools > Issue Type: Feature Request > Reporter: Kalyan gogineni > Assignee: Petr Široký > > guided rules editor function field does not perform semantic validation. > For example: when you define rules like below > When number 1 is not null > And number 2 is not null > Then number 3 = number5/number1 > Note: Where number5 is not defined. Then when you compile or build and deploy then drools does not throw error. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira February 2017