Re: How to manage differente welcome_file for a webapp depending jahia page context...

"Khue Nguyen" <[email protected]>
Newsgroups gmane.comp.cms.jahia.devel
Message-ID <001701c59c40$e6da66c0$7c02a8c0@SINGASONG>
Hi,


>Do you know a JAVA API in order to manage flat configuration files?

this really depends of your need. The flat file can be a properties file or 
an xml one.


>An other solution will be to get the portlet ID into the page and to store 
>specifique parameter into the database...

yes.

>By the way, what about memory if I install my portlet into several pages of 
>my web site?

Sorry if I'm misunderstanding your question.
If this is the same instance of a webapp ( deployed in one single context ), 
adding into several pages or just into one page is the same ( one single 
portlet).
On another hand, deploying it in several different webapp context as many 
different portlets and adding each one into a different page is more
resources consuming.


Regards,

Khue Nguyen



----- Original Message ----- 
From: "Gelin Patrick" <[email protected]>
To: <[email protected]>
Sent: Friday, August 05, 2005 8:18 AM
Subject: RE : How to manage differente welcome_file for a webapp depending 
jahia page context...



> It's not possible to pass parameters through the page url.
> Theses parameters are actually hidden from the application
> parameters scope
> to avoid conflict.
Ok

> A solution that requires a bit more codes is to add a portlet
> setting menu
> within your webapp so that it can be configured to use
> specific welcome
> file. Theses settings can then be stored in a flat text file
> and reloaded
> when the webapp is called.

Very good idea!

Do you know a JAVA API in order to manage flat configuration files?

An other solution will be to get the portlet ID into the page and to store 
specifique parameter into the database...

By the way, what about memory if I install my portlet into several pages of 
my web site?

Thanks.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.