JBoss EAP 6.4.0 works fine with Netbeans 8.1, however, if you are like me and would like to take advantage of JSF 2.2, which were added only in JBoss EAP 7.0.0, you will need to do some work.
In Netbeans 8.1, I was able to get around the problem with an empty domain by setting up JBoss EAP 7.0.0, choosing "WildFly Application Server" instead of "JBoss Application Server". Below are more detailed instructions:
In Netbeans 8.0.1, select "Services", right-click "Servers" and select "Add Server ...", select the "WildFly Application Server" option, specify "server location" in the JBoss EAP 7 root directory (for example, c : \ jboss7), and then specify the server configuration parameter: c: \ jboss7 \ standalone \ configuration \ standalone-full.xml and what it is.
However, even after this an application server has now been added, there is still an error in which your code will not be deployed correctly, see details here:
https://netbeans.org/bugzilla/show_bug.cgi?id=258091
Fortunately, this was fixed in the Netbeans nightly build. It seems that the error was fixed in February 2016. I installed NetBeans IDE Build 201607140002, which includes this hotfix (like any other newer one I assume). So, you can take the nightly build here (otherwise you can wait until Netbeans 8.2 fixes the bugs when it will):
http://bits.netbeans.org/dev/nightly/
It should be noted that even after using the nightly build, I still had to add the server to Netbeans using the technique described above (add it as “WildFly application server” and not “JBoss application server”, otherwise you still get an empty domain problem) .
Everything seems to work as expected, in any case, using the foregoing ... of course, there is a risk element using the nightly build, as it is technically still in the testing phase. This is the price we pay for living on the sharp edge of the sword! :)