Bug 1204628 - [6.4.0 RN] Clarify confusing release notes text for fixed issue BZ#1107869
Summary: [6.4.0 RN] Clarify confusing release notes text for fixed issue BZ#1107869
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Documentation
Version: 6.4.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: CR2
: EAP 6.4.0
Assignee: Scott Mumford
QA Contact: Pavel Jelinek
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-03-23 08:42 UTC by Pavel Jelinek
Modified: 2015-04-17 05:37 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Build Name: 23033, 6.4.0 Release Notes-6.4-1 Build Date: 17-03-2015 12:23:47 Topic ID: 42588-746727 [Latest]
Last Closed: 2015-04-17 05:37:54 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1107869 0 unspecified CLOSED Web Console errors out and ends the jbossas process completely 2023-09-14 02:09:48 UTC

Internal Links: 1107869

Description Pavel Jelinek 2015-03-23 08:42:06 UTC
Title: Fixed Issues

Describe the issue:
"In previous JBoss EAP 6 versions, when JTS was enabled in the Transactions section of the web management console, it was necessary to also set the attribute transactins to the value on in the JacORB subystem.
This was not the intended behavior, which is for transactions to be enabled when JTS is enabled.
The behavior has been corrected in this release by adding a validation check to the console." 
is confusing since the behaviour actually wasn't changed just the validation was added.

Suggestions for improvement:
Change the text to 
"When JTS is enabled in the `Transactions` section of the web management console, it is necessary to also set the attribute `transactions` to the value `on` in the JacORB subsystem.
In previous JBoss EAP 6 versions user was not notified about this dependency by management console.
The behavior has been corrected in this release by adding a validation check to the console."

Comment 3 Radim Hatlapatka 2015-04-13 09:17:07 UTC
Verified with EAP 6.4.0.CR2 and RN revision 6.4.0-12


Note You need to log in before you can comment on or make changes to this bug.