[ https://issues.jboss.org/browse/WFCORE-1163?page=com.atlassian.jira.plugi... ] Heiko Braun commented on WFCORE-1163: ------------------------------------- Brian: ... since swarm is assembling together a config from elements fractions plus stuff from standalone.xml and exactly what from standalone.xml should be kept vs ignored is still somewhat in flux letting swarm be in charge of the overall assembly and letting it pull what it needs from kernel-provided parsers seems best at least initially ... the intent would be to allow access to a parser for the main elements i.e. first level children of the <server> element root, excluding 'extension' and 'profile' allowing that seems like a fairly simple refactoring of existing parsing classes ... one aspect to deal with is the parsers for some chunks do validation against data parsed from other chunks e.g. the 'socket-binding-group' parsing validates that 'interface' references point to previously parsed interfaces I think we would need to tweak the internals to disable that kind of validation if things are parsed this way since it's only if the full internal parser is used that we have the necessary state to pass between parser chunks unless we add some complicated API, which I'd prefer not to do ... that's no big loss though that kind of validation will still happen when the List<ModelNode> of operations is executed doing it in the parser is redundant we only do it to provide a better error message if validation fails one that can point to a line/column in the xml -- This message was sent by Atlassian JIRA (v6.4.11#64026)