Hello! I’m currently reviewing the proposal [1] of WFLY-14934 [2] feature request and I’m struggling to understand what are the objectives of this feature. The “Relevant Installation Types” section with selected “OpenShift s2i” in the proposal [1] suggest this feature is OpenShift focused. However the only differences between this new feature and existing bootable JAR can be observed on bare metal. On bare metal this feature brings the same features as bootable JAR does but it adds three things: persistent configuration, multiple deployments and direct access to each file of the provisioned server. In S2I scenarios there seems to be no difference between bootable JAR and this feature. Form of the server in the application image is as far as I know transparent for the user. What are the real use-case scenarios of this feature? Regards, Honza [1] https://github.com/wildfly/wildfly-proposals/pull/401/files [2] https://issues.redhat.com/browse/WFLY-14934 and https://issues.redhat.com/browse/EAP7-1734 -- Jan (Honza) Kasik Quality Engineer, EAP QE