July 2015 - 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

1 week, 6 days

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

2 months

2
3
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, 3 weeks

3
10
0 / 0

[JBoss JIRA] (WFCORE-857) A read-resource on a subsystem resource of a missing deployment returns a successful completion

by James Perkins (JIRA)

James Perkins created WFCORE-857: ------------------------------------ Summary: A read-resource on a subsystem resource of a missing deployment returns a successful completion Key: WFCORE-857 URL: https://issues.jboss.org/browse/WFCORE-857 Project: WildFly Core Issue Type: Bug Components: Domain Management Reporter: James Perkins Assignee: Brian Stansberry Executing the follow operation results in the operation succeeding even though no deployment exists with the name. {code} [standalone@localhost:9990 /] /deployment=foo.war/subsystem=*:read-resource { "outcome" => "success", "result" => [] } {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4937) Implement graceful shutdown for transactions

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-4937?page=com.atlassian.jira.plugin.... ] Jason Greene commented on WFLY-4937: ------------------------------------ Ah ok yes I think that sounds like the desired behavior. > Implement graceful shutdown for transactions > -------------------------------------------- > > Key: WFLY-4937 > URL: https://issues.jboss.org/browse/WFLY-4937 > Project: WildFly > Issue Type: Feature Request > Components: Transactions > Affects Versions: 10.0.0.Alpha5 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 11.0.0.Alpha1 > > > We will handle suspend for JTA and JTS by disallowing new transactions and then block the suspend thread until the count of active transactions drops to zero. We will also suspend the recovery manager. > We will *not* do graceful shutdown for the optional XTS subsystem. For example an incoming XTS request for an existing transaction will be blocked. > Question: should we > - raise a new JIRA for this XTS case; > - document the deficiency and see if there are complaints; > - document the deficiency and fix it in a subsequent release -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ELY-14) Provide a set of realm implementations.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-14?page=com.atlassian.jira.plugin.sys... ] Darran Lofthouse updated ELY-14: -------------------------------- Fix Version/s: 1.0.0.Alpha4 (was: 1.0.0.Alpha3) > Provide a set of realm implementations. > --------------------------------------- > > Key: ELY-14 > URL: https://issues.jboss.org/browse/ELY-14 > Project: WildFly Elytron > Issue Type: Task > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.0.0.Alpha4 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ELY-154) Session based DigestCredential support

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-154?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-154: --------------------------------- Fix Version/s: 1.0.0.Alpha4 (was: 1.0.0.Alpha3) > Session based DigestCredential support > -------------------------------------- > > Key: ELY-154 > URL: https://issues.jboss.org/browse/ELY-154 > Project: WildFly Elytron > Issue Type: Sub-task > Components: Passwords > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.0.0.Alpha4 > > > DigestCredential but where additional information is included such as nonce and cnonce to create a credential applicable to a session. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ELY-153) Support DigestCredential with a specified realm name

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-153?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-153: --------------------------------- Fix Version/s: 1.0.0.Alpha4 (was: 1.0.0.Alpha3) > Support DigestCredential with a specified realm name > ---------------------------------------------------- > > Key: ELY-153 > URL: https://issues.jboss.org/browse/ELY-153 > Project: WildFly Elytron > Issue Type: Sub-task > Components: Passwords > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.0.0.Alpha4 > > > This would imply the password is retrievable and the realm associated by the authentication mechanism. > I see the following scenarios to be covered by this: - > - Realm that does not store pre-hashed and so is open to the mechanism providing the realm name. > - Realms where one or more realm names may be in use. > - One identity with multiple credentials each with a different realm. > - Different realms used for different identities but no more than one per identity. > If this is accomplished using a CallbackHandler then there are couple of Callback options: - > 1. getCredentialSupport on the realm, a RealmChoiceCallback can be used by a realm that advertises all the realm names it knows, where realm names are selected the response can take into account if all or some of the identities in that realm have a credential stored for that realm. > 2. getCredentialSupport on the realm can also support RealmCallback, in this case the mechanism specifies one realm name. > 3. These two can be repeated on the RealmIdentity, in that case however as a specific identity is being referenced the response can be much more specific. > 4. On getCredential the Callbacks can both be supported but in both cases can allow the selection of a single realm. > Another option could be an extension to RealmChoiceCallback that also indicates the level of support for each realm it contains. > Whilst exploring this, being able to identify the message digest algorithm support level should also be considered in parallel. > Also I see solving this as a simple pre-requisite for ELY-154 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ELY-151) Ability to supply additional information during credential acquisition

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-151?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-151: --------------------------------- Fix Version/s: 1.0.0.Alpha4 (was: 1.0.0.Alpha3) > Ability to supply additional information during credential acquisition > ---------------------------------------------------------------------- > > Key: ELY-151 > URL: https://issues.jboss.org/browse/ELY-151 > Project: WildFly Elytron > Issue Type: Enhancement > Components: API / SPI, Passwords > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.0.0.Alpha4 > > > I think this is the final known gap in our credential acquisition and validation API/SPI. > There are a couple of specifications that also allow for additional information to be used when obtaining a representation of a users credential, the most obvious being the session based variant of digest authentication where a nonce and cnonce are also incorporated. > A second variant with two different modes of operation would be the realm associated with the digest credential, currently we assume it is tightly associated with the storage representation of the credential but it could also be the case that the mech is requesting it for a specific realm. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ELY-147) Default Methods on the RealmIdentity interface

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-147?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-147: --------------------------------- Fix Version/s: 1.0.0.Alpha4 (was: 1.0.0.Alpha3) > Default Methods on the RealmIdentity interface > ---------------------------------------------- > > Key: ELY-147 > URL: https://issues.jboss.org/browse/ELY-147 > Project: WildFly Elytron > Issue Type: Feature Request > Components: API / SPI > Reporter: Darran Lofthouse > Fix For: 1.0.0.Alpha4 > > > Review how much of the RealmIdentity interface can have default method implementations, e.g. verification could be implemented if we can obtain the credential. > Credential conversion is also another one we could cover, a mechanism should be able to start querying from the most specific type of credential it understands, if default methods on the realm can handle the conversion it will mean the mechanism can ignore the conversion. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 4 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 July 2015