| Author |
JSF outcome across contexts
|
Mohammad Jaber
Ranch Hand
Joined: Apr 10, 2006
Posts: 46
|
|
Hi,
I am trying to seperate my JSF application into many sub application, so i am thinking of creating a .war file for each module , my question is incase i have a jsf navigation outcome entries on faces config file that redirects to a page that will reside on another .war (faces config) file, is this applicable on any way on JSF.
Thanks in advance
|
OCP , SCJP 5.0
|
 |
Cameron Wallace McKenzie
author and cow tipper
Saloon Keeper
Joined: Aug 26, 2006
Posts: 4967
|
|
You will want to keep these in the same war. Remember, session data can't be shared across war files.
-Cameron McKenzie
|
Author of Hibernate Made Easy, What is WebSphere???, JSF 2.0 Made Easy and the SCJA Certification Guides
|
 |
Mohammad Jaber
Ranch Hand
Joined: Apr 10, 2006
Posts: 46
|
|
|
i managed to share the session across the *.war files, using the extended functionality of IBM WebSphere, but my concern now is the way of handling the outcome navigation issue across these war files, so is there any suggestions!
|
 |
Cameron Wallace McKenzie
author and cow tipper
Saloon Keeper
Joined: Aug 26, 2006
Posts: 4967
|
|
using the extended functionality of IBM WebSphere
That can be a dangerous strategy. If anything, that indicates that these applications probably SHOULD be included in a single war file. That setting is really used to make older apps forwards compatible. Using that functionality in 2009 as a starting point may cause trouble in the short term.
Using multiple wars solely as a partitioning mechanism is a bit dicey if you ask me.
-Cameron McKenzie
|
 |
Mohammad Jaber
Ranch Hand
Joined: Apr 10, 2006
Posts: 46
|
|
|
Me Nither happy to use this, but we have to apply this on a legacy application with minimum cost of time and code modification
|
 |
Tim Holloway
Saloon Keeper
Joined: Jun 25, 2001
Posts: 14572
|
|
Mohammad Jaber wrote:Me Nither happy to use this, but we have to apply this on a legacy application with minimum cost of time and code modification
Alas, EVERYTHING these days is done with a minimum cost of time. I've seen some really serious "bit rot" as a result.
Theoretically software is immutable, never degrades, and "If it Ain't Broke, Don't Fix It". In reality, software doesn't exist in a vacuum, and if you don't do ongoing maintenance - including periodic overhauls - Murphy's Law dictates that it will completely train-wreck at the worst possible moment.
|
Customer surveys are for companies who didn't pay proper attention to begin with.
|
 |
 |
|
|
subject: JSF outcome across contexts
|
|
|