November 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-4335) Verify whether -Djava.net.preferIPv4Stack=true should be disabled on Linux/jdk6+

by Dimitris Andreadis (JIRA)

Verify whether -Djava.net.preferIPv4Stack=true should be disabled on Linux/jdk6+ -------------------------------------------------------------------------------- Key: JBAS-4335 URL: http://jira.jboss.com/jira/browse/JBAS-4335 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: System service Reporter: Dimitris Andreadis Assigned To: Dimitris Andreadis Fix For: JBossAS-5.0.1.CR1 -- 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 years, 8 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-4197) Allow more control over hot deployment triggers

by Scott M Stark (JIRA)

Allow more control over hot deployment triggers ----------------------------------------------- Key: JBAS-4197 URL: http://jira.jboss.com/jira/browse/JBAS-4197 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Deployment services Reporter: Scott M Stark Assigned To: Dimitris Andreadis Fix For: JBossAS-5.0.0.Beta3 We need finer grained control over how hot deployment events are triggered. Two examples are: 1. Enable/disable the current hot deployment scanning based on time stamp for individual deployments 2. Allow a trigger hot deployment on next request mode. -- 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 years, 8 months

3
3
0 / 0

[JBoss JIRA] Created: (JBAS-5128) JaasSecurityManagerService/AuthorizationManagerService need to retire

by Anil Saldhana (JIRA)

JaasSecurityManagerService/AuthorizationManagerService need to retire --------------------------------------------------------------------- Key: JBAS-5128 URL: http://jira.jboss.com/jira/browse/JBAS-5128 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: EJB3, Security Affects Versions: JBossAS-5.0.0.Beta3 Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: JBossAS-5.0.0.CR1 Since we injecting Security Managers into the deployers via beans, there is no need for these JMX MBean Services. -- 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 years, 8 months

3
8
0 / 0

[JBoss JIRA] Created: (JBAS-5672) Further jbossweb deployer/runtime refactoring

by Scott M Stark (JIRA)

Further jbossweb deployer/runtime refactoring --------------------------------------------- Key: JBAS-5672 URL: http://jira.jboss.com/jira/browse/JBAS-5672 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Deployers, ProfileService, Web (Tomcat) service Affects Versions: JBossAS-5.0.0.CR1 Reporter: Scott M Stark Assigned To: Scott M Stark Fix For: JBossAS-5.0.0.CR2 A task for further cleanup of the jbossweb deployer/services to integrate with MC, deployers, management, etc. -- 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 years, 8 months

4
6
0 / 0

[JBoss JIRA] Created: (JBAS-3633) Tidyup logging when transaction is no longer active

by Adrian Brock (JIRA)

Tidyup logging when transaction is no longer active --------------------------------------------------- Key: JBAS-3633 URL: http://jira.jboss.com/jira/browse/JBAS-3633 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: JB5-Transaction Manager Affects Versions: JBossAS-4.0.5.CR1 Reporter: Adrian Brock Priority: Minor Since JBossTM rollsback transactions at transaction timeout, we need to tidyup the transaction demarcation code (commit/rollback/setRollbackOnly, etc) such that the logging is more information and not so noisy. We still need to communicate that the transaction rolled back even if it is not the transaction demarcation point that does the rollback. Currrently, you get errors/warnings about not being able to setRollbackOnly or rollback, because the transaction is already ended. -- 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 years, 8 months

4
4
0 / 0

[JBoss JIRA] Created: (JBAS-5309) Revisit Security Injection

by Adrian Brock (JIRA)

Revisit Security Injection -------------------------- Key: JBAS-5309 URL: http://jira.jboss.com/jira/browse/JBAS-5309 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Security Reporter: Adrian Brock Assigned To: Anil Saldhana Fix For: JBossAS-5.0.0.CR1 The way security injection and dependency is working is a mess. 1) Some bits are passed as attachments 2) The Tomcat deployment mechanism needs redoing anyway 3) There's no way to override some things per deployment 4) The service dependencies of the security implementation don't look well defined 5) There's no real way to depend upon a specific login module, you have to depend on the XMLLoginConfig -- 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 years, 8 months

4
7
0 / 0

[JBoss JIRA] Created: (JBAS-6071) Move legacy invoker configurations to docs/examples/legacy-remoting

by Scott M Stark (JIRA)

Move legacy invoker configurations to docs/examples/legacy-remoting ------------------------------------------------------------------- Key: JBAS-6071 URL: https://jira.jboss.org/jira/browse/JBAS-6071 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Build System, Docs/Administration and Configuration Guide, Docs/Installation and Getting Started Guide, Remoting Affects Versions: JBossAS-5.0.0.CR2 Reporter: Scott M Stark Assignee: Paul Gier Fix For: JBossAS-5.0.0.GA We need to retire the old jmx invoker based configuration into docs/examples/legacy-remoting -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

3
6
0 / 0

[JBoss JIRA] Created: (JBAS-6073) Migrate password based attributes in beans to additionally accept PBE or SubjectFactory setup

by Anil Saldhana (JIRA)

Migrate password based attributes in beans to additionally accept PBE or SubjectFactory setup --------------------------------------------------------------------------------------------- Key: JBAS-6073 URL: https://jira.jboss.org/jira/browse/JBAS-6073 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Security Affects Versions: JBossAS-5.0.0.CR2 Reporter: Anil Saldhana Assignee: Anil Saldhana Fix For: JBossAS-5.0.1.CR1 We need to identify configurations where password is required and provide capabilities to do PBE (security-domain) or the SubjectFactory injection. The SubjectFactory instance should be able to accept a password. The SF instance can be injected to multiple beans. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

2
4
0 / 0

[JBoss JIRA] Created: (JBAS-6072) Retire http-invoker.sar

by Scott M Stark (JIRA)

Retire http-invoker.sar ----------------------- Key: JBAS-6072 URL: https://jira.jboss.org/jira/browse/JBAS-6072 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Remoting Reporter: Scott M Stark Assignee: Scott M Stark Fix For: JBossAS-5.0.0.GA Move the legacy http over jmx invoker service to docs/examples/legacy-remoting -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

3
6
0 / 0

[JBoss JIRA] Created: (JBAS-6123) Create legacy invoker test config

by Scott M Stark (JIRA)

Create legacy invoker test config --------------------------------- Key: JBAS-6123 URL: https://jira.jboss.org/jira/browse/JBAS-6123 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Scott M Stark Assignee: Scott M Stark -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

3
6
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2008