I haven't tried it against EAP6. Are you sure this is a problem against EAP 6 too and not just upstream WildFly?

I found it with EAP and then checked wildfly. Would you create a push request for EAP or should I do?

I was ready to create one so did it anyways, please see
https://github.com/jbossas/jboss-eap/pull/305

Thank you.

Carlo de Wolf <cdewolf> made a comment on jira WFLY-1914

How can a change in namespace definition be a fix here?
The server should behave just fine on an old namespace version.

Brian Stansberry <brian.stansberry> made a comment on jira WFLY-1914

Carlo:

The subsystem was written such that the parsers treat

{code}
<subsystem xmlns="urn:jboss:domain:naming:1.0"/>
{code}

as equivalent to

{code}
<subsystem xmlns="urn:jboss:domain:naming:2.0">
   <remote-naming/>
</subsystem>
{code}

The latter requires the remoting subsystem which is not present in appclient.xml.

We can't change the parser for 1.0 without breaking existing working configs.

PR: https://github.com/jbossas/jboss-eap/pull/489

We still see the issue with 6.2.0 ER3.1.. just saying

Brian, I speculated that it is ER3.1, I'm using RPM distro that's possibly not exactly matching 3.1. I'll try again when ER5 is out.

Ah, I see. ER3.1 was just some sort of respin of ER3 that didn't include any new fixes.

I do not see the issue with ER5.