July 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (AS7-1401) Domain Managent - Support for client choosing auth mechanism

by Darran Lofthouse (JIRA)

Domain Managent - Support for client choosing auth mechanism ------------------------------------------------------------ Key: AS7-1401 URL: https://issues.jboss.org/browse/AS7-1401 Project: Application Server 7 Issue Type: Task Components: Domain Management, Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 7.1.0.Beta1 Consideration is needed first as there are potential risks - however we should look at what it will take to allow clients to choose from list of auth mechansisms. AS7-1372 is to look at adding Kerberos support, however this can mean all clients need to also support it so we may need to allow some clients to fallback to a username/password based mechanism. The authorization scheme still needs further consideration however it is anticipated that the authentication mechansism will also be taken into account, this could mean that for clients that have chosen username / password auth their capabilities are restricted. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

4
4
0 / 0

[JBoss JIRA] Created: (AS7-1095) Complete Host Controller shutdown / restart operations

by Kabir Khan (JIRA)

Complete Host Controller shutdown / restart operations ------------------------------------------------------ Key: AS7-1095 URL: https://issues.jboss.org/browse/AS7-1095 Project: Application Server 7 Issue Type: Task Components: Domain Management Reporter: Kabir Khan Assignee: Kabir Khan AS7-517 did a complete shutdown of the host controller, do the rest from the original issue here. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

5
9
0 / 0

[JBoss JIRA] Created: (AS7-713) Persist named deployment groups for reuse by clients

by Max Rydahl Andersen (JIRA)

Persist named deployment groups for reuse by clients ---------------------------------------------------- Key: AS7-713 URL: https://issues.jboss.org/browse/AS7-713 Project: Application Server 7 Issue Type: Feature Request Reporter: Max Rydahl Andersen Assignee: Jason Greene It seems to me that we will have multiple clients using the management api to deploy to domain and they all today need to somehow define at every deployment the deployment plan to use if not just the hardwired default. To avoid having to redefine that everytime it means clients such as IDE's, management console, command line tools will all have to somehow be able to persist this information in their own local setup and these will probably all be a little bit different and thus not shareable. Thus I suggest that it should be possible to define named deployment settings that all the clients can query and provide as named arguments in the managed deployments instead of it being up to every client to define it. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

8
13
0 / 0

[JBoss JIRA] Created: (AS7-1333) Expose web container runtime stats through the web console

by Heiko Braun (JIRA)

Expose web container runtime stats through the web console ---------------------------------------------------------- Key: AS7-1333 URL: https://issues.jboss.org/browse/AS7-1333 Project: Application Server 7 Issue Type: Feature Request Components: Console Reporter: Heiko Braun Assignee: Heiko Braun Fix For: 7.1.0.CR1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

2
2
0 / 0

[JBoss JIRA] Created: (AS7-1334) Expose JMS runtime stats through console

by Heiko Braun (JIRA)

Expose JMS runtime stats through console ---------------------------------------- Key: AS7-1334 URL: https://issues.jboss.org/browse/AS7-1334 Project: Application Server 7 Issue Type: Feature Request Components: Console Reporter: Heiko Braun Assignee: Heiko Braun Fix For: 7.1.0.CR1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-8901) dependency injection fails when deploying large graphs of inter-dependent EJBs

by Radai Rosenblatt (JIRA)

dependency injection fails when deploying large graphs of inter-dependent EJBs ------------------------------------------------------------------------------ Key: JBAS-8901 URL: https://issues.jboss.org/browse/JBAS-8901 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: EJB3 Affects Versions: 6.0.0.Final Environment: windows xp 32bit, jdk 6u23 Reporter: Radai Rosenblatt Assignee: Carlo de Wolf i've attached a maven project that generates a random ear containing 100 EJBs that are inter-denendent. the graph generated is directed (no loops). graph roots are @Singleton @Startup beans that have a @PostConstruct method. in this method, they access all of their injected @EJBs, which then do the same recursively. the ears generated deploy fine for small cases (5 beans), but when trying to deploy a 100-bean ear several injections fail. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

5
12
0 / 0

[JBoss JIRA] Created: (JBAS-9265) Apply consistent policy with closing input streams associated with ops

by Brian Stansberry (JIRA)

Apply consistent policy with closing input streams associated with ops ---------------------------------------------------------------------- Key: JBAS-9265 URL: https://issues.jboss.org/browse/JBAS-9265 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Domain Management Affects Versions: 7.0.0.Beta2 Reporter: Brian Stansberry Fix For: 7.0.0.Beta3 We're currently haphazard about how streams associated with operations are handled. IMO the most intuitive contract is whoever opens the stream closes it. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

7
8
0 / 0

[JBoss JIRA] Created: (JBAS-6657) managementView.load() fails to merge ServerInfo, ThreadPool, GlobalRequestProcessor, and Host ManagedObjects

by Ian Springer (JIRA)

managementView.load() fails to merge ServerInfo, ThreadPool, GlobalRequestProcessor, and Host ManagedObjects ------------------------------------------------------------------------------------------------------------ Key: JBAS-6657 URL: https://jira.jboss.org/jira/browse/JBAS-6657 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: ProfileService Reporter: Ian Springer Assignee: Scott M Stark Fix For: JBossAS-5.1.0.CR1 These are all MOs that are needed by the Embedded Console. Here's the log output: 10:47:18,464 DEBUG [ProfileServiceFactory] About to load profile via Management View... 10:47:23,964 WARN [AbstractManagedObjectPopulator] Cannot create String name from non-Simple property: ManagedProperty{JNDIName,JNDIName,metaType=SimpleMetaType:java.lang.String}, value=null 10:47:23,980 WARN [AbstractManagedObjectPopulator] Cannot create String name from non-Simple property: ManagedProperty{JNDIName,JNDIName,metaType=SimpleMetaType:java.lang.String}, value=null 10:47:57,870 WARN [ManagementViewImpl] Failed to merged the following runtime ManagedObjects: {jboss.system:type=ServerInfo/jboss.system:type=ServerInfo=ManagedObject{jboss.system:type=ServerInfo}, jboss.web:name=http-127.0.0.1-8080,type=ThreadPool/=ManagedObject{jboss.web:name=http-127.0.0.1-8080,type=ThreadPool}, jboss.web:name=http-127.0.0.1-8080,type=GlobalRequestProcessor/=ManagedObject{jboss.web:name=http-127.0.0.1-8080,type=GlobalRequestProcessor}, jboss.web:host=127.0.0.1,type=Host/=ManagedObject{jboss.web:host=127.0.0.1,type=Host}} 10:48:00,917 DEBUG [ProfileServiceFactory] Loaded profile via Management View in 42453 milliseconds. -- 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

13 years, 1 month

4
3
0 / 0

[JBoss JIRA] Created: (JBAS-8679) Add xml comment support to the domain model

by Jason Greene (JIRA)

Add xml comment support to the domain model ------------------------------------------- Key: JBAS-8679 URL: https://jira.jboss.org/browse/JBAS-8679 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Reporter: Jason Greene Fix For: 7.0.0.Beta1 For usability reasons, we should attach an xml comment to the nearest AbstractModelElement, so that they can be recreated when the model is altered. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

4
5
0 / 0

[JBoss JIRA] Created: (JBAS-8140) Standard JTS-based configuration

by Brian Stansberry (JIRA)

Standard JTS-based configuration -------------------------------- Key: JBAS-8140 URL: https://jira.jboss.org/browse/JBAS-8140 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Fix For: Unscheduled This JIRA is based on feedback we received after the Andiamo BOF at JBoss World 2010: >> Would like to have a configuration with JBossTM JTS implementation >> already installed and optimized for servers that need distributed >> transactions. Proper transaction management is an advanced topic for >> JBoss admins and having Redhat's expertise already configured on a >> server is very reassuring. -- 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, 1 month

5
8
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 2011