[jboss-as7-dev] [Proposal] Dyanmic console module loading for multi-product in EAP6*

[Heiko Braun]

I am not sure I fully understand the proposal. 

Serial version stream that includes all plugins? Can you elaborate on that?
You mean one console project, containing all possible extensions?

Every product bundles a version of the console:
I think that is what we have atm, no? What's wrong with that?

Generally speaking ("emulate pluggability"):
Why is everybody so worried about the compile time extensions? It's a perfectly valid use case IMO, that fully leverages all benefits we gain from using GWT in the first place. Can you elaborate why this should be done differently?

Regards, Heiko

On Dec 17, 2012, at 11:12 PM, Jason Greene <jason.greene at redhat.com> wrote:

> In order to support multiple derived products based on EAP, we need a solution that allows the console to "emulate" plug-ability. By "emulate", I mean that until we have a dynamic rendering engine (AS8/EAP7), we still have to deal with the fact that GWT requires static compilation.
> 
> The first component of the proposal is that the console have a serial version stream which includes *all* plugins. Every derivative product will need to contribute a plugin which is pulled into the serial version stream via reference. This means that every console release will need to verify compatibility with old and new versions of all products. This should not be too big of a deal because the management policies require that we maintain compatibility anyway.
> 
> The second component is that every product (and its patch updates if features are added) will bundle a version of the console which includes support for the product. At runtime the server will then simply pick the most recent version available. This will allow for every copy to maintain a clear ownership. So for example, if you install a patch which brings in console version 1.7, that version can be removed and the other available versions can be used.
> 
> An example is:
> 
> /consoles/1.1 (Installed by EAP)
> /consoles/1.2 (Installed by Portal)
> /consoles/1.3 (Installed by BRMS)
> /consoles/1.4 (installed by a Portal patch)
> 
> So in this case the server would start with 1.4. If BRMS was removed, 1.4 would be picked. If the portal patch was then rolled back, 1.2 would be picked.
> 
> Alternatively we could always just leave all versions, and always pick the most recent console version, however rollbacks would be an issue. We would need some way for the user to manually revert if there was a bug (perhaps just having them delete the bad version).
> 
> -Jason
>