Details
-
Type:
Improvement
-
Status:
Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: 0.7
-
Fix Version/s: None
-
Component/s: Core
-
Labels:None
-
Number of attachments :
Description
This will make it more visible if expanded WAR are supported or not by the different containers using the ContainerCapability.supportsDeployableType(DeployableType).
IMHO, it's not ideal to merge the (content) type of a deployable and its file organization (packed/expanded) into one value. I think adding ContainerCapability.supportsDeployable(DeployableType type, boolean expanded) would make more sense.
On the other hand. does it really matter whether a container natively supports packaged/expanded WARs? The container-specific deployers could also pack/unpack the deployables on the fly if needed, couldn't they?