Hello,
Currently, the client directory contains client-side jars needed to work
with JBoss.
While it is very modular to have one jar per "function" (clustering,
security, ...) (and it is also easier to build as each module is responsible
for building its own set of client-side JARs), in many cases, we end-up
launching client side applications with a huuugge classpath containing at
least 5 JBoss jars.
Why not *also* build a "jbossall-client.jar" (or something like this) that
would contain all client JARs generally needed? This would still allow
fine-grained tuning for experts but also bring simplicity for quick-setup.
Cheers,
Sacha
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
