Reported by ehsavoie on IRC:

<ehsavoie> it looks like wildfly is looking for a "hibernate-persistence-unit" element in the jpa subsystem which creates an error 500 on the jpa tab in the admin console with the standalone default configuration. Shouldn't there be a default working config there ?
<smarlow> ehsavoie: sounds like a bug, which build of WildFly?
<ehsavoie> master from this morning
<ehsavoie> the 500 error: http://fpaste.org/22146/
<ehsavoie> smarlow: commit b5367674f6b3efb778fee8baa2739ff8fda4b4a5
<smarlow> ehsavoie: okay, another question, is this with a JPA application deployed?
<ehsavoie> nope, blank standalone from the build
<smarlow> ehsavoie: I'll try to recreate after my (master) build finishes. I usually have some JPA application deployed when I use the management console so I probably missed this
<ehsavoie> smarlow: the error is 'logical' as there are no resource so the context.getFailureDescription().set(MESSAGES.noSuchResourceType(stepAddress)); is not surprising
<smarlow> ehsavoie: thanks, i reproduced it

• fharms has quit (Quit: This computer has gone to sleep)
  <ehsavoie> smarlow: you're welcome

Internal Server Error
"JBAS014883: No resource definition is registered for address [
(\"deployment\" => \"*\"),
(\"subsystem\" => \"jpa\"),
(\"hibernate-persistence-unit\" => \"*\")
]"

https://gist.github.com/scottmarlow/5902551