Re: Make JForum Portlet site aware

"Daniel Zimmermann" <[email protected]>
Newsgroups gmane.comp.cms.jahia.devel
Message-ID <[email protected]>
Hello Wilhelm,

>we are using Jahia's JForum portlet in our portal, and
>are quite happy

Since your company is based on a german speaking country I wonder 
if you could solve the UTF-8 (or better the umlaut) problem with 
the JForum Portlet. If you aren't using hsqldb I would be highly 
interested in how you fixed/tweaked the Portlet to not create 
garbage.

Cheers
Daniel Zimmermann


On Tue, 26 Apr 2005 23:59:37 -0700 [email protected] wrote:
>Hi devlist folks!
>
>currently we are using Jahia's JForum portlet in our portal, and 
>are quite
>happy. Now we want to extend our portal solution that it supports 
>more than
>one site, on a single platform. For this reason we also want the
>JForum-Portlet to be "site-aware" - i.e. on each site an 
>administrator can
>instantiate and configure a forum for it's own. E.g. If company A 
>on site A
>instantiates a forum it should not see or disturb forum content of 
>company
>B on site B, and vice versa.
>
>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...
>
>So my question is, if anyone has a better advice, for 
>accomplishing this
>task.... ?
>
>Or is there maybe another Portlet or template that fits more 
>better for
>"site-awareness" .....?
>
>____
>kind regards
>Wilhelm Berger
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.