Implementation of a more complex ACL scheme for domain management
-----------------------------------------------------------------
Key: AS7-2487
URL: https://issues.jboss.org/browse/AS7-2487
Project: Application Server 7
Issue Type: Feature Request
Components: Domain Management, Security
Reporter: Darran Lofthouse
Assignee: Darran Lofthouse
Fix For: 7.2.0.Alpha1
--
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
JBoss Admin Console Does not allow to modify attributes like Driver
-------------------------------------------------------------------
Key: AS7-2543
URL: https://issues.jboss.org/browse/AS7-2543
Project: Application Server 7
Issue Type: Bug
Components: Console
Reporter: Vimal Kansal
Assignee: Heiko Braun
Once a datasource has been defined, I can not change the driver associated with it on console. Edit button allows editing of only JNDI name and the Connection properties. I can't change the driver.
--
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
Thomas Diesler created AS7-3694:
-----------------------------------
Summary: Allow management client to associate metadata with DeploymentUnit
Key: AS7-3694
URL: https://issues.jboss.org/browse/AS7-3694
Project: Application Server 7
Issue Type: Feature Request
Components: OSGi, Server
Reporter: Thomas Diesler
Assignee: Thomas Diesler
Fix For: 7.2.0.Alpha1
Currently there is no way to pass some metadata through the deployment API such that they could show up with the DU.
As a client I'd like to say autostart=false and in my DUP I'd like to pick that up and not start a deployment (i.e. a bundle) automatically
Generally it should be possible for the client to set some properties for the deployment in a generic way such that they get associated with the DeploymentUnit
--
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
Matej Lazar created AS7-3472:
--------------------------------
Summary: replacing domain controller
Key: AS7-3472
URL: https://issues.jboss.org/browse/AS7-3472
Project: Application Server 7
Issue Type: Feature Request
Components: Domain Management
Affects Versions: 7.1.0.CR1b
Reporter: Matej Lazar
Assignee: Brian Stansberry
Replacing domain controller using operations:
/host=node1:remove-local-domain-controller
/host=node1:write-remote-domain-controller(host=172.16.254.128, port=9999)
--
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
Thomas Diesler created AS7-3693:
-----------------------------------
Summary: Console does not support install/start semantic for bundles
Key: AS7-3693
URL: https://issues.jboss.org/browse/AS7-3693
Project: Application Server 7
Issue Type: Bug
Components: Console, Domain Management, OSGi
Reporter: Thomas Diesler
Assignee: David Bosschaert
Fix For: 7.1.1.Final
Currently, when deploy a bundle through the console it is started automatically. For a set of bundles it means that you must install them in order otherwise they might not resolve.
Digging up the related issues ...
--
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
prepared statement is getting closed prematurely
------------------------------------------------
Key: AS7-1461
URL: https://issues.jboss.org/browse/AS7-1461
Project: Application Server 7
Issue Type: Feature Request
Components: JPA / Hibernate
Reporter: Scott Marlow
Assignee: Scott Marlow
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
No way to grep/more or find a line in the CLI
---------------------------------------------
Key: AS7-2642
URL: https://issues.jboss.org/browse/AS7-2642
Project: Application Server 7
Issue Type: Feature Request
Components: CLI
Reporter: Jim Tyrrell
Assignee: Alexey Loubyansky
In the CLI I should be able to page through the pages of information that are presenting using | more or equivalent. By the same token I should be able to grep to find the one line that I am looking for, when I know what it is I am looking for.
--
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
EJB3 SFSB performace problem: parallel calls are sequenced
----------------------------------------------------------
Key: JBAS-9416
URL: https://issues.jboss.org/browse/JBAS-9416
Project: Legacy JBoss Application Server 6
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 6.0.0.Final
Reporter: Radim Hanus
When a client looks up more SFSB of given type in dedicated threads and subsequently calls business methods then such calls are always sequenced.
Works fine in jboss-5.1.0
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
tomcatAuthentication attribute on the AJP connector
---------------------------------------------------
Key: AS7-1581
URL: https://issues.jboss.org/browse/AS7-1581
Project: Application Server 7
Issue Type: Feature Request
Components: Server
Affects Versions: 7.0.0.Final
Environment: Windows Server 2003 32 bit, IIS 6, tomcat connector 1.2.28 used as an extension
Reporter: Brett Prucha
Assignee: Jason Greene
Priority: Minor
In JBoss 5.1.0 I could set the tomcatAuthentication attribute of the AJP connector to false to allow IIS to handle the authentication and pass that along to JBoss. I'm wanting to upgrade to JBoss 7 but unable to set this attribute in version 7.0.0 final to make this work. This attribute is descibed in the tomcat documentation at http://tomcat.apache.org/tomcat-7.0-doc/config/ajp.html
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
Passivation of a @Stateful session bean with an @Inject'ed @Stateless session bean fails with not-serializable error.
---------------------------------------------------------------------------------------------------------------------
Key: JBAS-9245
URL: https://issues.jboss.org/browse/JBAS-9245
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: EJB
Affects Versions: 6.0.0.Final
Reporter: Felix Ullrich
Assignee: Carlo de Wolf
I've the same problem described in this issue https://issues.jboss.org/browse/JBAS-8384
Could you please resolve it (maybe in 6.1.0) and dont just close it. Thank you
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira