On Fri, Jan 5, 2018 at 8:20 AM, Brian Stansberry
In practice the suffix is required. The deployment unit processors
know whether they are interested in the deployment, and in the end that gets
back to some DUP or other checking the suffix. The alternative would be DUPs
speculatively digging into the deployment, checking for deployment
descriptors or annotations and the like and that would be more expensive,
likely buggy (e.g. false positives when some class in the classpath includes
an annotation not relevant to the deployment) and could mess up some use
cases where we want to defer classloading.
Another alternative is for an early processor to identify the type,
tag it on to the deployment context, and then we modify all other DUPs
to use that information. It seems pretty fragile to rely on the name,
particularly if that mechanism allows the "type" of deployment to
change in mid-deploy.