Bug 1151000 - Empty elements should be removed from XML after removing their last child element in PicketLink Subsystem
Summary: Empty elements should be removed from XML after removing their last child ele...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: PicketLink
Version: 6.4.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: DR6
: EAP 6.4.0
Assignee: Pedro Igor
QA Contact: Pavel Slavicek
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-10-09 11:46 UTC by Ondrej Lukas
Modified: 2019-08-19 12:44 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-08-19 12:44:10 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker EAP6-182 0 Major Ready for QA Transition PicketLink subsystems from tech preview to production support 2016-01-04 10:02:32 UTC
Red Hat Issue Tracker WFLY-3978 0 Major Resolved PicketLink Subsystem EAP 6.4 Issues 2016-03-17 08:36:17 UTC

Description Ondrej Lukas 2014-10-09 11:46:35 UTC
These issue is related to following elements of PicketLink Federation Subsystem:
<service-providers>, <trust>, <handlers>, <keys>

All of these elements have no attributes and they are added automatically when their child element is added via CLI. It is correct behavior - according to XSD (wildfly-picketlink-federation_1_1.xsd), when any of these elements exists they have to contain at least one child element. However, when their last child element is removed, they stay written empty in configuration, which is not valid XML state according to XSD (e.g. <service-providers/> left in configuration).

These empty elements should be removed, when their last child element is removed or XSD should be updated to allow minOccurs="0" for their child elements.

Comment 1 JBoss JIRA Server 2014-10-14 13:01:26 UTC
Kabir Khan <kabir.khan> updated the status of jira EAP6-182 to Resolved

Comment 2 JBoss JIRA Server 2014-10-14 13:26:52 UTC
Kabir Khan <kabir.khan> updated the status of jira EAP6-182 to Reopened

Comment 3 Pedro Igor 2014-10-17 15:32:59 UTC
https://github.com/jbossas/jboss-eap/pull/1810

Comment 4 JBoss JIRA Server 2014-10-17 18:38:40 UTC
Kabir Khan <kabir.khan> updated the status of jira EAP6-182 to Resolved

Comment 5 JBoss JIRA Server 2014-10-22 09:08:11 UTC
Ondrej Lukas <olukas> updated the status of jira EAP6-182 to Reopened

Comment 6 Ondrej Lukas 2014-10-22 11:30:27 UTC
Verified in EAP 6.4.0.DR6.

Comment 7 JBoss JIRA Server 2014-11-05 07:05:40 UTC
Rostislav Svoboda <rsvoboda> updated the status of jira EAP6-182 to Resolved

Comment 8 JBoss JIRA Server 2016-03-17 08:36:18 UTC
Pedro Igor <pigor.craveiro> updated the status of jira WFLY-3978 to Resolved


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