• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
  • Campbell Ritchie
  • Ron McLeod
  • Rob Spoor
  • Tim Cooke
  • Junilu Lacar
  • Henry Wong
  • Liutauras Vilda
  • Jeanne Boyarsky
Saloon Keepers:
  • Jesse Silverman
  • Tim Holloway
  • Stephan van Hulst
  • Tim Moores
  • Carey Brown
  • Al Hobbs
  • Mikalai Zaikin
  • Piet Souris

Integrating Jforum with other application but within a single ear

Ranch Hand
Posts: 17424
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi all,
Thanks for this cool application. Kudos to all brainees. We integrated Jforum with one application within a single ear. After logging into application, user will click the Jforum link and user shouldbe able to access Jforum. We are using Acegi to store user after authentiction. Acegi puts all user profile information in session.I found different approaches in documentation to achieve SSO. We have no cookies in our application. Which is the best approach to get SSO. If we use request.getRemoteUser() how will it pick up user info from session dynamically.

1)using cookies
2)using request .getRemoteUser
3)Implementing my own SSO class

[originally posted on jforum.net by gregjhonson]
Migrated From Jforum.net
Ranch Hand
Posts: 17424
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

I'm also trying to integrate jforum into an ear file / another web application (Precisely Seam Web Application in Netbeans 6.1 with Seam and facelets Plugin). Could you help me out with a step by step guide on how you did it

Thanks in advance

[originally posted on jforum.net by ngonidan2]
Migrated From Jforum.net
Ranch Hand
Posts: 17424
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Got it,
This might also help others with the same question, so thanks to Monroe and GregJohnson and a few additions i found out. Sorry Images could not be attached,


When would someone want to package 2 war files together


Your application might be made up of 2 completely separate web applications e.g. a website utilising a open source Forum package e.g. Jforum. In this case the 2 web applications are difficult to combine into one, see Bottom for Pros and cons
Java EE projects are either EAR or WAR deployments that use Java EE technology. If you have a WAR with JSPs and JDBC access of a relational database, that's a Java EE project. The original intent was that EAR files were "enterprise", and that meant EJBs. An EAR file an contain EJBs, WARs, JARs, the whole enchilada.
Thinking in terms of services are a little different. I think deployment deserves careful consideration, because components that are packaged together must be brought down and up together if any maintenance has to be done.
So think carefully about how you package your services. It's not an all or none blanket answer, IMO. You should look at what your services are doing and how they might be used together to decide how they should be packaged and deployed.
Also I think what you decide to put in each EAR is governed by organizational and technical issues.
I think most important technical role of an EAR is a classloader root in a runtime environment. This normally means you can deploy different versions of libraries and your own classes in different EAR's. This means you should keep your container root classpath fairly empty (or as supplied by the container vendor), because it may allow one phsyical container to service multiple applications using possibly conflicting libraries. This is great news if you're developing a number of different applications using a common code-base. You can have a number of projects deploying to the same farm of servers without messing up for eachother.
You will normally never deploy a smaller unit of software than the EAR. Each EAR can be more or less fully self-contained. I would normally let the content of these refelect what the owning organization thinks of as applications or subsystems. You can usually package the same components in multiple EAR's.

Single war or Two separate wars - which is the best solution for Integrating Jforum

Single War file i.e. Same context with 2 apps:


Everything is in the same class loader so stuff like session variables, jforum repository cache objects, and the like are available to both apps. This can make tight integration much easier.
you should be just be able to get everything you need directly from the session.

i.e. in authenticateUser method, just do something like:

SessionContext sctx =ctx.getSessionContext();
User u = (User)sctx.getAttribute("USER"); // or what ever acegi uses for here at login
if (u != null){
// user is loged in with valid session.
// note: if u still want the email to persist..I think u still need to place this into cookie.
// else u need to hack the jforum code to get in the right place.
return user.userName();
// not logged, return null;


Dependency conflicts, harder to upgrade to a new version because everything needs to be checked again.

Potential security issues (low probablity... but).. You've got "other peoples" code running with your code.

Scalablity... - You have to set up a completely different jforum instance for each application instance.. may not be an issue except if you need to support many clients or communities.

Separate contexts (2 wars)


Better security

Easier to update jForum to new versions

No dependencies problems


More complex to integrate apps, e.g. SSO and the like.

i.e. If you decide to keep the JForum logic its own war, your only option is to use a cookie, or JAAS...The advantage of the cookie solution is, it will work cross Servers, in case we need load balancing

Look and feel / Navigational issues. E.g., do you modify jForum to look like your main app or use iframes to provide the "wrapping".

How to package 2 war files in one ear File Using Netbeans

Simple just create an Enterprise Application in Netbeans and call it e.g. testenterpriseapp

You get 3 projects in the Projects Window, a war, EJB and the Ear project as below

So how do we add the other war project ??? Simple, just create a New web application along the way, the wizard will give the Server Setting Dialogue Box

Choose Add to Enterprise application and choose the Ear file e.g testenterpriseapp in the case, and simply run/Build!!!

[originally posted on jforum.net by ngonidan2]
You showed up just in time for the waffles! And this tiny ad:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koop
    Bookmark Topic Watch Topic
  • New Topic