|
|
|
[
Permlink
| « Hide
]
Scott N. Smith - [09/Sep/03 01:22 AM ]
Patch to add getServletContext() to RequestLifecycleFilter
Diff file for FilterDispatcher.java. This removes an useless setter method for filterConfig, and improves the method comment for the getter.
Diff file that adds getServletContext(HttpSession)
The three diff files are patch files that enable the WebWork JAR to be subclassed to make WebWork run under Weblogic Server 6.1 SP4.
RequestLifecycleFilter.java adapted to work under Weblogic 6.1 SP4. This must be in a separate JAR so that this can be linked to weblogic.jar instead of servlet.jar.
SessionLifecycleListener.java adapted to work under Weblogic 6.1 SP4. This must be in a separate JAR so that this can be linked to weblogic.jar instead of servlet.jar.
FilterDispatcher.java adapted to work with weblogic.jar instead of servlet.jar.
Add this class to the webwork.jar. It contains a singleton that stores the servlet context.
Here's the summary on how to incorporate the above files:
1. Process the diff and patch files into the current webwork project. These files are: a) FilterDispatcher.diff b) RequestLifecycleFilter.diff c) SessionLifecycleListener.diff d) ServletContextSingleton.java (new file) Note that there is no changed functionality; just minor added functionality. 2. Build the webwork.jar normally (i.e. using servlet.jar). 3. In a separate project, build a separate jar (i.e. webworkweblogic61.jar) using the following: a) the above webwork.jar. b) the following new Java files: 1) FilterDispatcherCompatWeblogic61.java 2) RequestLifecycleFilterCompatWeblogic61.java 3) SessionLifecycleListenerCompatWeblogic61.java c) all of the jar files required by webwork EXCEPT servlet.jar. d) weblogic.jar (Weblogic Server 6.1 SP4 version). 4. Wherever you would use one of the above filters or listeners in web.xml, substitute the "FooCompatWeblogic61.java" variant instead. If you have questions, contact scottnelsonsmith@yahoo.com Sorry for the duplicate file names; please use ONLY THE FIRST duplicate file name
Hi Smith,
Your effort is highly appreciated. Just one more thing to consider. If the changes are incorporated into the latest build-war file or on cvs, that would be highly commendable. I am at present integrating ww2 with weblogic6.1, sp4. What is your thought on this. Whether I should go for 7.0, which supports servlet2.3 fully well. Regards Chandramoulee One more thought. The group should baseline a release, such its compatability is fully tested with J2EE compliant App. servers, especially with weblogic 7.0 and websphere 5.0. This would give the required limelight for webwork2.
Regards Chandramoulee Chandra,
If you follow the above instructions in this issue, WebWork 2 will work under Weblogic 6.1. However, if you have Weblogic 7.0 available, then you do not have to make these mods, since Weblogic 7.0 is fully Servlet 2.3 complient (I believe). Currently my group is "stuck" at Weblogic 6.1 which is why I went to this effort. If I had the choice, I would far rather be using the current Weblogic release. My mistake; my Eclipse is set up to auto-generate the Washington Mutual file comment. I'm working on (to the point of final debugging) a direct submission of these same files to CVS.
Unfortunately, I don't know a way to delete attachments. Matt, if you know of a way, I'd appreciate deleting the duplicate submissions that I had to post to get rid of the Washington Mutual references. Indeed, I'd like to delete all of the attachments, since shortly they won't be necessary since they (modified) will be in CVS. I've added a subproject under top directory "misc" that
provides the additional classes and build files to run WebWork 2 under Weblogic 6.1. This should close this issue. | ||||||||||||||||||||||||||||||||||||||||||||||