January 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-9024) Consolidated AS 7 Javadocs

by David Lloyd (JIRA)

Consolidated AS 7 Javadocs -------------------------- Key: JBAS-9024 URL: https://issues.jboss.org/browse/JBAS-9024 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Reporter: David Lloyd Assignee: John Casey Fix For: 7.0.0.CR1 Parent issue for tracking tasks required to accomplish a consolidated javadoc bundle for AS 7. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

5
5
0 / 0

[JBoss JIRA] Created: (JBAS-9029) Identify modules with inadequate/missing JavaDoc

by David Lloyd (JIRA)

Identify modules with inadequate/missing JavaDoc ------------------------------------------------ Key: JBAS-9029 URL: https://issues.jboss.org/browse/JBAS-9029 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: David Lloyd Fix For: 7.0.0.CR1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

4
9
0 / 0

[JBoss JIRA] (AS7-2756) Implement username / password strength checks

by Darran Lofthouse (Created) (JIRA)

Implement username / password strength checks --------------------------------------------- Key: AS7-2756 URL: https://issues.jboss.org/browse/AS7-2756 Project: Application Server 7 Issue Type: Feature Request Components: Domain Management Reporter: Darran Lofthouse Assignee: Brian Stansberry Fix For: Open To Community The AS 7.1 distribution now contains a utility for adding new users to the property files, this utility contains some very basic checks of the username and password e.g. bad choices of username and disallowing passwords which match the username. This Jira is to implement a more advanced check to enforce complexity. I believe we should have something along the lines of a util that will take a username and password and will respond ACCEPT, REJECT, or WARN where WARN has a message to display to the user and the user an opportunity to ignore the warning or return to re-entry of the details. At some point in the future this could become a management operations so the implementation shouldn't be too constrained to the current command line tool. As a management op we may also want to take into account the user making the request, i.e. a user changing their own password has tighter restrictions than the overall administrator. As the add user script is currently stand alone this may be a nice task for someone to undertake who would like to get more familiar with submitting an AS change without needing to get too involved with the internals of the application server at this stage. -- 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

13 years, 7 months

6
10
0 / 0

[JBoss JIRA] Created: (JBAS-8325) graceful shutdown

by Emanuel Muckenhuber (JIRA)

graceful shutdown ----------------- Key: JBAS-8325 URL: https://jira.jboss.org/browse/JBAS-8325 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Domain Management Reporter: Emanuel Muckenhuber Fix For: 7.0.0.M1 We need to define a clear contract between these networking services and the services that use them in order to be able to perform a graceful shutdown of remote connectors. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

6
11
0 / 0

[JBoss JIRA] Created: (JBAS-9086) Add Notification support to the domain management API

by Brian Stansberry (JIRA)

Add Notification support to the domain management API ----------------------------------------------------- Key: JBAS-9086 URL: https://issues.jboss.org/browse/JBAS-9086 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Fix For: 7.0.0.CR1 Management resource should be able to emit notifications; clients can register listeners. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

6
10
0 / 0

[JBoss JIRA] (AS7-2468) Support for profile and socket binding group includes

by Brian Stansberry (Created) (JIRA)

Support for profile and socket binding group includes ----------------------------------------------------- Key: AS7-2468 URL: https://issues.jboss.org/browse/AS7-2468 Project: Application Server 7 Issue Type: Feature Request Components: Domain Management Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 7.2.0.Alpha1 Restore the ability to have a profile include another profile and for a socket-binding-group to include another socket-binding-group. -- 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

13 years, 7 months

2
1
0 / 0

[JBoss JIRA] (AS7-2705) .deployed sticks around

by Jesper Pedersen (Created) (JIRA)

.deployed sticks around ----------------------- Key: AS7-2705 URL: https://issues.jboss.org/browse/AS7-2705 Project: Application Server 7 Issue Type: Bug Components: Domain Management Affects Versions: 7.1.0.Alpha1 Reporter: Jesper Pedersen Assignee: Brian Stansberry Steps: 1) cp successful.rar /path/to/jbossas7/standalone/deployments 2) touch /path/to/jbossas7/standalone/deployments/successful.rar.dodeploy .rar deploys with issues => .deployed 3) Ctrl+C The .deployed file is still there -- 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

13 years, 7 months

2
2
0 / 0

[JBoss JIRA] (AS7-3016) Lazy enlistment of JMS Session does not work - UserTransaction implementation does not support it

by Jiri Pechanec (Created) (JIRA)

Lazy enlistment of JMS Session does not work - UserTransaction implementation does not support it ------------------------------------------------------------------------------------------------- Key: AS7-3016 URL: https://issues.jboss.org/browse/AS7-3016 Project: Application Server 7 Issue Type: Bug Components: Transactions Affects Versions: 7.1.0.Beta1b Reporter: Jiri Pechanec Assignee: Jonathan Halliday Priority: Critical This test case was identified in TCK6. There is a MDB with CMT configured - com/sun/ts/tests/jms/ee/mdb/xa The testsuite sends a message to MDB MDB 1) creates a QueueSession 2) Start UT 3) Send a message 4) Rollback UT 5) Start UT 6) Send a message 7) commit UT Unfortunately the semantics is broken as QueueSession is not enlisted into transactions. The enlistment is done when UserTransaction emits a notification org/jboss/tm/usertx/UserTransactionRegistry. The enlistment is done by JCA component which receives the notification and enlists all active XAResources. Unfortunately the notification is emitted by org/jboss/tm/usertx/client/ServerVMClientUserTransaction. Unfortunately org/jboss/as/txn/service/ArjunaTransactionManagerService hard-codes com.arjuna.ats.internal.jta.transaction.arjunacore.UserTransactionImple which does not have this capability. It is necessary to support this scenario as it is tested in TCKs. -- 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

13 years, 7 months

11
11
0 / 0

[JBoss JIRA] (JBEE-97) See if the jstl dependency on xalan can be refactored out

by Paul Gier (Created) (JIRA)

See if the jstl dependency on xalan can be refactored out --------------------------------------------------------- Key: JBEE-97 URL: https://issues.jboss.org/browse/JBEE-97 Project: JBoss JavaEE Spec APIs Issue Type: Enhancement Components: jboss-jstl-api Affects Versions: JavaEE 6 Spec APIs 3.0.0.Beta1 Reporter: Paul Gier Assignee: Paul Gier Fix For: JavaEE 6 Spec APIs 3.0.0 The JSTL api has a dependency on the xalan fork which is only available in the JBoss repository. If this can be refactored out, then the complete set of dependencies will be available in central. -- 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

13 years, 7 months

3
4
0 / 0

[JBoss JIRA] Created: (AS7-1268) Can't update subhandler on async handler

by Stan Silvert (JIRA)

Can't update subhandler on async handler ---------------------------------------- Key: AS7-1268 URL: https://issues.jboss.org/browse/AS7-1268 Project: Application Server 7 Issue Type: Bug Components: Logging Affects Versions: 7.1.0.Alpha1 Reporter: Stan Silvert Assignee: David Lloyd David, sorry if I'm assigning to the wrong person. I guess this could be a CLI bug. [standalone@localhost:9999 /] cd subsystem=logging/async-handler=ASYNC [standalone@localhost:9999 async-handler=ASYNC] :read-resource(recursive=true) { "outcome" => "success", "result" => { "level" => "INFO", "overflow-action" => "BLOCK", "queue-length" => 1024, "subhandlers" => ["FILE"] } } [standalone@localhost:9999 async-handler=ASYNC] :update-properties(subhandlers=["CONSOLE"]) {"outcome" => "success"} [standalone@localhost:9999 async-handler=ASYNC] :read-resource(recursive=true) { "outcome" => "success", "result" => { "level" => "INFO", "overflow-action" => "BLOCK", "queue-length" => 1024, "subhandlers" => ["FILE"] } } -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

3
3
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 January 2012