at the palma-training i learned that using the recent
feature "EAR-scoping" would prevent classes from going
to the central repository, allowing for "specific
versions" running in parallel.
But: does "EAR-scoping" simply mean "deployment
inside an .ear-file" or it this something which
would be applicable to .sar-deployments by using
a magic tag?
Right now it is only implemented for .ear files. The extension to any package is really easy for the 3.2/4.0 versions, but I haven't done it yet. Meanwhile you can package your .sar files in an .ear to use this feature.