Andrzej said:
>Also the design practices/paradigms of Separation of
>Concern, Modularity, Layering and Encapsulation apply
>to the build/deploy/management process implementations
>as much as to the Container design itself. In a nutshell:
>"keep 'em all decoupled as much as possible".
I have found the build/deploy diagram in the Architecture document to be
extremely useful for envisioning how all the pieces we have been talking about
fit together. One thing that comes to mind here is that it would be nice if we
could abstract the deployment target to just be an Embedlet Container (no
matter where is it hosted) and the deployment artifact to be something similar
to a WAR file (perhaps BAR (emBedded Application aRchive) ) that would contain
all of the resources needed to run the Embedlet based application.
Even though the Embedlet specification's responsibilities would need to stop
here I could still see us developing a number of Ant targets for deploying BAR
files into various Embedlet Container hosts including muivums, TStik/TINIs,
JStamps, etc.
Ted
__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
|
