[
https://issues.jboss.org/browse/WFCORE-42?page=com.atlassian.jira.plugin....
]
Darran Lofthouse commented on WFCORE-42:
----------------------------------------
Looks like we also need to go one step further, whilst AppClientXml parses the
'server' element it only supports a subset of it's content. For better or
worse the schemas are the document that describes the XML we support - deliberately
rejecting configuration that is valid against the schema is not good.
Add a ServerXml Parser which extends CommonXml
----------------------------------------------
Key: WFCORE-42
URL:
https://issues.jboss.org/browse/WFCORE-42
Project: WildFly Core
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Domain Management
Reporter: Darran Lofthouse
Assignee: Darran Lofthouse
Fix For: 1.0.0.Alpha4
Both StandaloneXml and AppclientXml parse XML starting from the server element.
This duplication has always been problematic as AppclientXml is completely separate from
the remaining domain config parsing, however with the core split this is even worse.
This change is to introduce a ServerXml that can be the common base for both
StandaloneXml and AppclientXml - except in extreme cases it will then be safe to ignore
AppclientXml for further schema updates.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)