Hi Benjamin,
At 15:10 09/03/2005, [EMAIL PROTECTED] wrote:
One problem is: JForum has its own user management, so I possibly have to reenter fields, which I already may have entered in the portals user registration, or user profile form. For the end user it is surely better if he has to enter information, e.g. his email address - only once. Or if he changes his email address within JForum it should also be changed in the portal. ....
The idea was not to fork (at least too much) the official Jforum project. Else we will have problems to upgrade to new release of the official Jforum project. That is why we tried to keep the forum webapp more and less as it is (or tried to committ changes in the official Jforum CVS).
Regarding the user profile, that is true that we have not mapped all the possible fields. But this should be possible if this information is for example in the session.
Another problem: when I integrate the portlet within the page, I can decide which Jahia groups, will be mapped to which JForum roles (admin, manager). This works well. But when I change this mapping later, e.g. remove one Jahia group from role JForum-manager, users of that group who have been registered as JForum-manager in the meantime will remain JForum-administrators, because their role is already stored in the JForum DB-tables, and the change of the mapping does not propagate ...
In fact this is the case for all webapps :-( . This is a bug we will have to correct in one of the next release.
But once you have setup your jfoum, you do not need to modify the users roles through Jahia any more. You can directly use the Jforum Administration to modify some users permissions, no?
-- I have thought of this solution: Since JForum and Jahia use the same database, I can extend the portals user managment, in a way that it also persists relevant JForum information into the JForum tables. For example when the user enters his email adress in a portal form, it will be stored twice, one time in the portal user table, and another time in the JForum user table. So I could remove the user management forms from JForum because al relevant data is entered from "outside". Maybe this is not a good solution because it bypasses what portlets are for?.
Yes and it is very specific to your project/templates.
-- another solution would be: to integrate JForum as it is in the portal application, not as a portal, but running within the same context. I do not know how much problems this will bring, or how easy it will be?
Never tried but a cleaner manner should (must) be possible ;-)
-- JSR 128 Portlet API I do not know much about JSR 128 but maybe it would provide some features to couple portlets and portals more tightely. Does anybody know about this?
You mean JSR168...
We also developed a JSR168 version of Jforum but you will have to add Jahia 4.5 in order to used it. And finally you still have some Java cross-context issues.
But you may check some articles here: http://community.java.net/portlet/
Else Khaled who integrated Jforum is not here today but I will ask him as soon as he is back if has other (clean) solutions.
Cheers St�phane
_____ kind regards Wilhelm Berger
