[
https://issues.jboss.org/browse/AS7-3350?page=com.atlassian.jira.plugin.s...
]
David Bosschaert updated AS7-3350:
----------------------------------
Steps to Reproduce:
1. Go to EJB 3, Container Configuration
2. Hit Edit and change the Stateless Session Pool value to 'mdb-strict-max-pool'
3. Hit cancel
4. Hit Edit again
5. Now you can see that you can't change the value of the Stateless Session Pool any
more.
Workaround Description: (was: 1. Go to EJB 3, Container Configuration
2. Hit Edit and change the Stateless Session Pool value to 'mdb-strict-max-pool'
3. Hit cancel
4. Hit Edit again
5. Now you can see that you can't change the value of the Stateless Session Pool any
more.)
Combo boxes stop working after hitting cancel
---------------------------------------------
Key: AS7-3350
URL:
https://issues.jboss.org/browse/AS7-3350
Project: Application Server 7
Issue Type: Bug
Components: Console
Affects Versions: 7.1.0.CR1b
Reporter: David Bosschaert
Assignee: Heiko Braun
This is a general issue with the combo-boxes and their interaction with the editing
framework.
When you edit a subsystem that uses combo boxes (e.g. EJB 3) and then hit cancel instead
of save, the combo box becomes unresponsive when trying to edit the subsystem again.
The main problem is with combo boxes that have 2 possible values, although if there are 3
values the problem applies to the 2 values involved (the old and the new).
I have also seen the same behaviour with combo boxes in various places.
--
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