This is a followup of JBIDE-18373 which was originally about deployment via management api not handling "mark as deployable" files properly. This was fixed, but there's still a problem of ordering. The use case here was a seam project deployed to EAP 6.3. There are three parts:
1. Seam project war
2. database driver jar
3. datasource xml

When you click "Add and Remove..." on the server in server view, it will sometimes be deployed in the wrong order and fail to deploy.
Specifically, when you click "Add All" in the dialog, it will not work, whereas if you click "Add" for each of the three resources, it will deploy alright.

As Rob pointed out, it can get really tricky to guess the right ordering.

See JBIDE-18373 for more details.