This week's book giveaway is in the Spring forum. We're giving away four copies of Pro Spring MVC with WebFlux: Web Development in Spring Framework 5 and Spring Boot 2 and have Marten Deinum & Iuliana Cosmina on-line! See this thread for details.
I have a commercial Confluence license, but I want to serve parts of the Wiki to the public, allowing registered users to comment and discuss. I don't have the $8K to upgrade Confluence to handle this. Jforum can definitely handle this commenting aspect, but I need some way to integrate the two. Could somebody knowledgeable about Jforum customization opine about the practicality of the following approaches?
Have jForum at the top level and work as usual, but have the root post of the topics consist of the content of the target Confluence wiki page. Add a new Jforum (square-bracket) markup tag so that authorized users can inline the content of the target Confluence Wiki page being served by my Confluence server, similar to JSP-including.
Similar to previous item, but instead of having the Jforum instance perform the fetch, just write an inline HTML frame and let the browser do the including. I'd think this would be simpler to implement and manage, and more efficient, but I'd have more work dealing with browser compatibility issues around inline frames.
Conversely, leave jForum in its off-the-shelf state ,and display the entire jForum pages inside another page. The content of the jForum topic's root post would just say something like "The document above". Either make a wrapper page that will include or inline-frame the two related Confluence + jForum pages; or modify Confluence to include or inline-frame the entire jForum page after the main Wiki page content.
You could create a striped down version of the templates to display just a topic and replies with a minimum of the overall forum navigation needed. Then put this in an iFrame at the end of the wiki page so people can comment.
An alternative route might be to look at writing your own code to get information from the jforum DB tables about topics and postings. Then just have a list of the subjects of the replies at the bottom with links that take you to the native jforum interface. Thats where uses read the full comments and reply. I've some some stuff like this with some custom tags (sorry work related and I can't share.. but it's not that hard..). The advantage here is that there is less template mods and it's easier to upgrade over time.
The hard part here would be to link the topic to the page. You might be able to pass this info to the templates via a request parameter or some other mechanism.
I've made much progress already. Since the jForum interface is so economical, by using conservative permissions, the jForum header is so small and useful that I have no desire to improve it by dynamically generating my own forum header.
The only limitation that I knew going in, but which is distasteful to me nonetheless, is the inability to dynamically size the iframe vertically without internal scroll bar. I just put a bunch of white space at the bottom. In the case of a really long forum page, the user will get an internal scrolll bar and can also use my custom button to eliminate the Wiki part and just go to the normal page. I wish vertical sizing/scrolling of iframes worked the same as horizontal (which works fine once you know the quirks of how % works).
I'm not concerned about auto-generating forum Topics or auto-generating links back to the Wiki. When my team wants public access to a Wiki page, they'll create the Wiki topic for it, and the external URL to bring up the "dual page" (regardless of whether the URL is used in a forum entry) is just a simple URL. I've implemented the Spring MVC infrastructure so that this all works right. [originally posted on jforum.net by blaine]
Excellent. I'll give that a try. I had tried the same approach in the past, but the tactics I used to get the sizes either calculated too early or too late (wrt HTML assembly) with the result that the resultant size was not the size that I needed to resize to). If you know this works, then I must not have known about the scrollHeight method. [originally posted on jforum.net by blaine]
If I inline it and eliminate the object lookup, I get permission failure on the "contentWindow".
I do have a working method (in production for about a year now) that resizes, but it avoids the permission and hierarchy problems by resizing in the content HTML of the child page. I don't want to do that with this project because I don't think the benefit would be worth the extra maintenance work of customizing jForum content. If I could just redeploy the jForum webapp that would be one thing, but since jForum mixes data with the webapp itself, it makes redeployment much riskier and entails much more down time.
I'm starting to believe my previous conclusion that the desired size can't be obtained and then set, excep from the page inside the embedded frame. [originally posted on jforum.net by blaine]
The URL is just the exact Confluence URL + ?forum=X where X is the corresponding JForum list page number. Not much to see in the forum at the time I'm writing this, since nobody's left any replies yet. I'm only allowing registered users to leave comments. [originally posted on jforum.net by blaine]
if you think brussel sprouts are yummy, you should try any other food. And this tiny ad: