Release Notes - WildFly Core - Version 2.0.0.Beta5 - HTML format

Component Upgrade

  • [WFCORE-926] - wildfly-core uses an older version of jboss-metadata-common than wildfly
  • [WFCORE-927] - Upgrade sql-api from 2.0.0.Beta1 to 2.0.0.Final
  • [WFCORE-941] - The file javax/sql/rowset/ is not present in jboss-javax-sql-api_7.0_spec-1.1.0.Final.jar


  • [WFCORE-74] - Use 'filesystem-path' arbitrary descriptor for attributes/params that represent a path
  • [WFCORE-693] - Don't require the exclusive management lock to run the "kill" or "destroy" ops on the HC
  • [WFCORE-831] - Rework handling of metrics
  • [WFCORE-893] - Remoting extension should register a ProfileParsingCompletionHandler to ensure the IO subsystem is created

Feature Request


  • [WFCORE-736] - Memory leak in server management controller
  • [WFCORE-904] - Future returned from Bootstrap.startup(...0) and ServerService.getValue() may never complete
  • [WFCORE-905] - CLI command "/host=master/server-config=server-one:remove" did not work if used in a batch
  • [WFCORE-907] - CLI's embed-host-controller command does not work in a non-modular CLI
  • [WFCORE-921] - Remove n2 model node cloning in ServerOperationResolver
  • [WFCORE-922] - Remove unneeded cloning of model nodes when persisting the kernel configs
  • [WFCORE-925] - Ability to use proxy in MavenUtil


  • [WFCORE-900] - Temporarily don't require a dependent capability to register a runtime-only requirement
  • [WFCORE-901] - ModelParserUtils isn't doing much
  • [WFCORE-906] - The default log file name in the file should be server.log


  • [WFCORE-806] - Collect capabilty data & references

Edit/Copy Release Notes

The text area below allows the project release notes to be edited and copied to another document.