Re: Make JForum Portlet site aware

At 08:59 27/04/2005, you wrote:
>I have thought about of adding a site_key field to each relevant JFORUM
>TABLE, and passing somehow the current site_key to the JForum DAO's, so
>that it can be considered within the queries. This solution has drawbacks,
>because I have to change the DB-schema and make also many changes in the
>JForum Source Code. Another problem are the caches, that JForum uses, I
>think in a "site-aware" solution I have to disable them, which surely will
>decrease perormance ..... Doing all this it will also make it difficult to
>switch to a newer version of JForum portlet, if one will come...

Yes, and the idea is not to fork the official JForum project (or then 
someone will have to spend a lot of time resynchronizing all the changes 
with all the newest upgrade of JForum - I just saw that they launch JForum 
2.1 for example and we are still based on the 2.0!).

The best things which could occur is if the lead committer of JForum 
accepts to integrate most of our generic changes in the core CVS of JForum 
so that we may only really restrict the "fork" to only what is necessary to 
Jahia (and for example clearly listed in a upgrade.me txt file). I sent a 
msg in this sense on JForum.net: http://www.jforum.net/posts/list/91.page 
but no news from Raphaël...

>So my question is, if anyone has a better advice, for accomplishing this
>task.... ?

Perhaps you can just redeploy another copy of the webapp for each virtual 
site with a slightly modified name (e.g. sitename_jforum)

>Or is there maybe another Portlet or template that fits more better for
>"site-awareness" .....?

The problem risks to be the same with all the external webapp forums as no 
one was originally developed to support such a feature...

Cheers
Stéphane


>____
>kind regards
>Wilhelm Berger