I wrapped those two lines in a try block, compiled & inserted my new
roller-web.jar into the WAR file. With good luck, Roller starts, creates
its tables, then dies thusly:
java.lang.NullPointerException
at
org.apache.roller.weblogger.ui.core.filters.PersistenceSessionFilter.
doFilter(PersistenceSessionFilter.java:64)
when continuing the install
Lines 62-64 are rather simple:
if (WebloggerFactory.isBootstrapped()) {
log.debug("Releasing Roller Session");
WebloggerFactory.getWeblogger().release();
I assume that I must have missed something exceedingly crucial in the
WebLogic deployment (I've never used WLS before, so it is quite likely).
I'll poke around & write down the process once it's together.
Any other ideas?
Thanks again,
-- Stefan
Dave wrote:
On Dec 14, 2007 2:10 PM, Stefan Edwards <[EMAIL PROTECTED]> wrote:
Hello,
Here's the deal: Roller 4.0 works fine on Tomcat 6.0, which is used for
internal testing. However, WebLogic 9.2 (soon 10.0) is used for
internet-facing appservers. We're upgrading to 10.0, but I cannot get
Roller to run on WL; each time it is told to start, I receive an error
(see below).
The environment is:
- Solaris 10 SPARC
- MySQL 5.x
- WebLogic 10.0
- Roller 4.0final (had the same issue with rc9/rc10)
Thanks for any help in advance,
-- Stefan
The errors look like this:
Error Message 1 (added for legibility)
------------------------
User defined listener org.apache.roller.weblogger.ui.core.RollerContext
failed: java.lang.NullPointerException. java.lang.NullPointerException
at
org.apache.roller.weblogger.ui.core.RollerContext.contextInitialized(RollerContext.java:110)
Here are lines 109 and 110 of RollerContext.java.
109 String ctxPath = servletContext.getRealPath("/");
110 if(!ctxPath.endsWith(File.separator)) {
Could it be that ServletContext.getRealPath("/") returns null on
Weblogic? And if so, can you configure Weblogic so that it returns a
proper path instead?
- Dave
