Right now the benefits are only packaging and redeployment and JNDI lookup. If you can think of anything else let us know.
I just started looking into this, but the main problem I need to resolve is the usage of classloaders in spring's configuration:
We have a number of apps, each with several jar modules containing their respective spring descriptors. Spring's default mechanism is to add these as classpath:* resources, springs hibernate integration in turn scans the classpath for hibernate mappings. This forces us to use the .ear-scoped classloading, which in turn is mutualy exclusive with the use of some of JBossAS's Hibernate integration.
What we need is more explicit (external) control on the lifecycle of this hierarchy of deployables. Preferably without filename suffixes, as extracting .har and .spring archives would triple the amount of jars.
So, the question stands: is this eanywhere near that?