I know I am a bit late to the game .. :)
Am 06.02.2013 um 08:49 schrieb Lukas Krejci:
This makes a lot of sense. Maybe we should concentrate on having a
clean
representation of the storage without any attached or assumed deployment
requirements (both in the model and in the UI). This then would enable us to
extend this with more, even wilder, deployment mechanisms in the future or on
the other hand use this storage for data without any deployment requirements.
I think this makes sense (If I understood it).
AS7 has this central "content store" (/deployment=xyz), where you
first upload content, but this is not "used" and then only in a 2nd stage
you tell the server what to do with it ("deploy, deploy to server-group xy").
Here the content can even be deployed multiple times (e.g. to different
server groups).
I think our bundles are similar in this regard.
Now I think it may make sense to extend this further. Take a user that
wants to deploy a .war file to as4, as5, as7 and tomcat. He should
be able to upload it only once and then on the resources (or groups of resources)
just say "deploy the existing content with id 123)