Bug 1195132 - (6.4.z) Wrong order of elements in jboss-cli.xml
Summary: (6.4.z) Wrong order of elements in jboss-cli.xml
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: CLI
Version: 6.4.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: CR1
: EAP 6.4.15
Assignee: Dominik Pospisil
QA Contact: Marek Kopecky
URL:
Whiteboard:
Depends On:
Blocks: eap6415-payload
TreeView+ depends on / blocked
 
Reported: 2015-02-23 08:02 UTC by Marek Kopecky
Modified: 2017-05-19 08:08 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2017-05-19 08:08:00 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1195138 0 unspecified CLOSED (6.4.z) Wrong order of elements in appclient.xml 2021-02-22 00:41:40 UTC
Red Hat Issue Tracker WFCORE-562 0 Major Resolved Wrong order of elements in jboss-cli.xml 2017-10-19 09:02:07 UTC

Internal Links: 1195138

Description Marek Kopecky 2015-02-23 08:02:04 UTC
Description of problem:
File bin/jboss-cli.xml has an incorrect order of elements. <history> tag should be before <resolve-parameter-values> tag. Schema of jboss-cli.xml is docs/schema/jboss-as-cli_1_3.xsd

Version-Release number of selected component (if applicable):
6.4.0.ER2

Steps to validate:
cd <eap_dir>
xmllint -noout -schema docs/schema/jboss-as-cli_1_3.xsd bin/jboss-cli.xml

 Error during validation:
bin/jboss-cli.xml:21: element history: Schemas validity error : Element '{urn:jboss:cli:1.3}history': This element is not expected. Expected is one of ( {urn:jboss:cli:1.3}connection-timeout, {urn:jboss:cli:1.3}ssl, {urn:jboss:cli:1.3}silent ).

Comment 1 Dominik Pospisil 2015-02-26 09:45:20 UTC
PR sent: https://github.com/jbossas/jboss-eap/pull/2329

Comment 2 Mike McCune 2016-03-28 22:30:10 UTC
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions

Comment 3 Michael Cada 2017-04-26 12:17:55 UTC
Verified with EAP 6.4.15.CP.CR2

Comment 4 Petr Penicka 2017-05-19 08:08:00 UTC
Released on May 18 as part of EAP 6.4.15.


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