RE: [Imbrium-developer] dynamic deployment of portlets

SourceForge Headquarters 1320 Columbia Street Suite 310 San Diego, CA 92101 +1 (858) 422-6466

Of course, all necessary mmbase parts must be included in the deployment
descriptor.
This includes the builder configuration and the application
configuration.
It is best to define all files in the archive with it's function. This
means that although the mmbase application configuration already
describes it's builders, the builders must also be specified in the
deployment descriptor. It could be possible that an application
configuration uses new and default builders from mmbase.
It is hard to find out which is new and which not.

Edvard Scheffers
E-ID! Internet Strategies

-----Original Message-----
From: imb...@li...
[mailto:imb...@li...] On Behalf Of
Rogier Schaaf
Sent: vrijdag 9 mei 2003 12:22
To: imb...@li...
Subject: Re: [Imbrium-developer] dynamic deplyment of portlets

I agree. By deploying applications you assure a consistent definition of
all necessary relations between builders used by your portlet. However,
you should of course also supply the builders in packaged file.

----- Original Message -----
From: "Gerard van de Looi" <gv...@e-...>
To: <imb...@li...>
Sent: Friday, May 09, 2003 10:23 AM
Subject: Re: [Imbrium-developer] dynamic deplyment of portlets

> Instead of defining builders, I think it should be possible to 
> describe mmbase applications in the deployment descriptor. In this way

> it's also possible to define relations between builders ans to 
> initialize your application with data.
>
> ----- Original Message -----
> From: "Rogier Schaaf" <rs...@e-...>
> To: "Imbrium Developer List" <imb...@li...>
> Sent: Friday, May 09, 2003 7:54 AM
> Subject: [Imbrium-developer] dynamic deplyment of portlets
>
>
> > Below is the draft design posted by Edvard to support dynamic 
> > deployment
> of
> > portlets, including MMBase content types and relations.
> >
> > I will try to tie this as document to outstanding Feature request on

> > SF.
> >
> > Any comments?
> >
> >
> > Support dynamic deployment of portlets
> >
> > It should be possible to place a file in a specified directory
(specified
> in
> > a config file) which makes it possible to deploy new portlets. The 
> > file should be a kind of archive preferably in the jar format (zip).

> > The file should contain a deployment descriptor describing the 
> > contents
of
> > the file.
> > The file can not only contain an implementation of a portlet, but 
> > also several mmbase components. These components can include 
> > builders and content.
> >
> > The goal of the dynamic deployment is to automatically pickup the 
> > new archive and dynamically use it's contents in the running server.

> > This should be done without unpacking the file. So, the contents is 
> > read
> in
> > the memory but is not stored on disk.
> > With the deployment a running Imbrium instance should be able to
> initialize
> > the new builders (create needed tables),
> > insert content into the database, add and start portlets, controls 
> > etc. Also, it should be possibly do load any class from included jar

> > files. An alternative approach which is available is to unpack the 
> > archive to
an
> > appropriate directory on the server. Then from here the 
> > initialization will take place.
> >
> > Deployment of an archive will never result in visable changes in a 
> > users portal. It will only add the possibillity to add a new portlet

> > to a
users
> > portal. So changes are only visible in customize mode.
> >
> > The files which containes the new deployment information should be
> described
> > in the deployment descriptor.
> > The descriptor describes which files should be deployed. The 
> > deployment descriptor could look something like this: <imbrium-app>
> >  <portlets>
> >   <portlet>new_portlets1.xreg</portlet>
> >   <portlet>new_portlets2.xreg</portlet>
> >  </portlets>
> >  <controls>
> >   <control>new_control.xreg</control>
> >  </controls>
> >  <controllers>
> >   <controller>new_controller.xreg</controller>
> >  </controllers>
> >  <medias>
> >   <media>new_media.xreg</media>
> >  </medias>
> >  <skins>
> >   <skin>new_skin.xreg</skin>
> >  </skins>
> >  <builders>
> >   <builder>new_builder1.xml</builder>
> >   <builder>new_builder2.xml</builder>
> >   <builder>new_builder3.xml</builder>
> >  </builders>
> >  <contents>
> >   <content>content.xml</content>
> >  </contents>
> >  <libraries>
> >   <library>portlets.jar</library>
> >  </libraries>
> > </imbrium-app>
> >
> >
> >
> > -------------------------------------------------------
> > Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa 
> > Clara The only event dedicated to issues related to Linux enterprise

> > solutions www.enterpriselinuxforum.com
> >
> > _______________________________________________
> > Imbrium-developer mailing list 
> > Imb...@li...
> > https://lists.sourceforge.net/lists/listinfo/imbrium-developer
> >
>
>
>
> -------------------------------------------------------
> Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara 
> The only event dedicated to issues related to Linux enterprise 
> solutions www.enterpriselinuxforum.com
>
> _______________________________________________
> Imbrium-developer mailing list Imb...@li...
> https://lists.sourceforge.net/lists/listinfo/imbrium-developer
>

-------------------------------------------------------
Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara
The only event dedicated to issues related to Linux enterprise solutions
www.enterpriselinuxforum.com

_______________________________________________
Imbrium-developer mailing list Imb...@li...
https://lists.sourceforge.net/lists/listinfo/imbrium-developer