NullPointerException in weblogic.jspc in WL6.1

[Lewin Chan]

Hey,
This has been bugging me for a couple of days now, and I don't really understand what's going on. I'm trying to pre-compile some jsps for a project, and using weblogic.jspc like they suggest, however, all I'm getting is a NullPointerException.

C:\work\cc>c:\bea\jdk131\bin\java -D"weblogic.Domain=mydomain" -Dweblogic.Name="myserver" -D"bea.home=c:\bea" -classpath "C:\bea\wlserver6.1\lib\weblogic.jar" weblogic.jspc -webapp build/call_centre -compileAll -k -keepgenerated -d build -verbose -verboseJavac -commentary -classpath "C:\dev\jar\ant.jar;C:\dev\jar\bsf.jar;C:\dev\jar\crimson.jar; C:\dev\jar\jaxp.jar;C:\dev\jar\xalan.jar;C:\dev\jar\xerces.jar;C:\bea\wlserver6.1\lib\weblogic.jar; C:\dev\jar\activation.jar;C:\dev\jar\commons-beanutils.jar;C:\dev\jar\commons-collections.jar;C:\dev\jar\commons-digester.jar;C:\dev\jar\commons-logging.jar;C:\dev\jar\datetime.jar;C:\dev\jar\dom4j-full-1.1.jar;C:\dev\jar\jakarta-collection.jar;C:\dev\jar\jakarta-regexp.jar;C:\dev\jar\jdom.jar;C:\dev\jar\log4j.jar;C:\dev\jar\mail.jar;C:\ dev\jar\rhino.jar;C:\dev\jar\sax.jar;C:\dev\jar\struts.jar;C:\dev\jar\tiles.jar; C:\dev\jar\xml-apis.jar;C:\dev\cc\lib\NSJscript.jar;C:\dev\uif\lib\gwsclient.jar; C:\dev\uif\lib\gwssecurity.jar;C:\dev\uif\lib\gwsstubs.jar; C:\dev\datamodel\dist\datamodel.jar;C:\dev\uif\dist\uif.jar;C:\dev\cc\cfg" -skipJavac
java.lang.NullPointerException
at weblogic.management.Admin.getServer(Admin.java:1252)
at weblogic.servlet.internal.dd.ServletEntityResolver.initServerMBean(ServletEntityResolver.java:69)
at weblogic.servlet.internal.dd.ServletEntityResolver.resolveEntity(ServletEntityResolver.java:94)
at weblogic.apache.xerces.readers.DefaultEntityHandler.startReadingFromExternalEntity(DefaultEntityHandler.java:749)
at weblogic.apache.xerces.readers.DefaultEntityHandler.startReadingFromExternalSubset(DefaultEntityHandler.java:566)
at weblogic.apache.xerces.framework.XMLDTDScanner.scanDoctypeDecl(XMLDTDScanner.java:1139)
at weblogic.apache.xerces.framework.XMLDocumentScanner.scanDoctypeDecl(XMLDocumentScanner.java:2215)
at weblogic.apache.xerces.framework.XMLDocumentScanner.access$0(XMLDocumentScanner.java:2170)
at weblogic.apache.xerces.framework.XMLDocumentScanner$PrologDispatcher.dispatch(XMLDocumentScanner.java:901)
at weblogic.apache.xerces.framework.XMLDocumentScanner.parseSome(XMLDocumentScanner.java:381)
at weblogic.apache.xerces.framework.XMLParser.parse(XMLParser.java:967)
at weblogic.apache.xerces.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:175)
at weblogic.servlet.internal.dd.DescriptorLoader.parse(DescriptorLoader.java:311)
at weblogic.servlet.internal.dd.DescriptorLoader.initializeWebXml(DescriptorLoader.java:327)
at weblogic.servlet.internal.dd.DescriptorLoader.initialize(DescriptorLoader.java:242)
at weblogic.servlet.internal.dd.DescriptorLoader.<init>(DescriptorLoader.java:176)
at weblogic.servlet.internal.dd.DescriptorLoader.loadDescriptor(DescriptorLoader.java:396)
at weblogic.jspc.runBodyInternal(jspc.java:227)
at weblogic.jspc.runBody(jspc.java:169)
at weblogic.utils.compiler.Tool.run(Tool.java:79)
at weblogic.jspc.main(jspc.java:360)
--------------- nested within: ------------------
weblogic.utils.AssertionError: ***** ASSERTION FAILED ***** - with nested exception:
(Stack trace repeated).
As far as I can make out, error is in the method (within weblogic.management.Admin)

    public static ServerMBean getServer()
    {
        try
        {
            return (ServerMBean)adminMBeanHome.getAdminMBean(serverName, "Server", domainName);
        }
        catch(Exception exception)
        {
            throw new AssertionError(exception);
        }
    }

so the question I must ask is why is adminMBeanHome null, and does it matter, if all I'm trying to do is compile some JSPs?
My config.xml is simply the config.xml that was installed by WL (specifically, mydomain\config.xml.FROM_INSTALLER), weblogic does start using this config.xml.
Thanks for any pointers
Lewin
[ October 15, 2002: Message edited by: Thomas Paul ]
[ October 15, 2002: Message edited by: Thomas Paul ]

[Lewin Chan]

Ok, having done some monkeying around... I've managed to get weblogic.jspc to execute by writing my own wrapper class that does a weblogic.management.Admin.initialize()
I guess it's not such a big error after all, but if some WL expert can explain to me why weblogic.jspc doesn't do the initialization properly, or even why it's required, i'd be most grateful

import weblogic.*;
import weblogic.management.*;
import java.util.*;
public class myjspc {
    public static void main(String args[])
        throws Exception
    {
        weblogic.management.Admin.initialize();
// This is just a direct copy of what was
        // already in jspc.main()  
        for(int i = 0; i < args.length; i++)
        {
            if(!args[i].equals("-compileAll"))
                continue;
            String args1[] = new String[args.length + 1];
            System.arraycopy(args, 0, args1, 0, args.length);
            args1[args.length] = "bogus.jsp";
            args = args1;
            break;
        }
        try
        {
            (new weblogic.jspc(args)).run();
        }
        catch(Throwable throwable)
        {
            throwable.printStackTrace();
        }
    }
}

[Dave Landers]

Just get rid of all the -Dweblogic.Name etc from your command line. They are confusing weblogic into thinking you want to start a server.
It should be:
java -classpath weblogic.jar weblogic.jspc [options]