There exact jars you need on the client side is explained in detail in section 4.4 of the user manual, and yes, it does also say in a yellow note box that they must appear in a different order:
It's always worth looking in the documentation before asking a question like this.
Ok, the thing about the order is there, sorry I haven't saw it, I just used the order from the examples.
But the question I wanted to ask was :) :
What is the minimal set of jars to be included from $JBOSS_HOME/client in order to replace the evil jbossall-client.jar in a remote JBM client?
To be honest, I don't know. :)
jbossall-client.jar is maintained by the AS team. It includes classes from various packages including some JBM and remoting ones. But there are still other classes from other packages in it which may or may not needed for a jbm client.
You'd better included it in you classpath and in the right order. If you want to get rid of it badly, you need to consult the AS team IMO.
May be we can reverse engineer it somehow (jar classes intersection for example) .. but I hoped that someone knows the answer..
So, probably nobody knows if for a remote JBM client it would be sufficient to take all the jars from $JBOSS_HOME/client without jbossall-client.jar?
Having a requirement on the order of the jars is a bad thing, so it is duplicating classes in jars. Sooner or later this leads to various kinds of problems.
jar hell has been a known issue for a long time in JBoss Messaging.
But all new dev is on HornetQ - which doesn't have these issues.