FAQs (Frequently Asked Questions)

Why doesn't the XMLC wizard ever finish processing files on Linux?

The XMLC wizard requires that you do not use the VM parameter -Xverify:none when compiling non-html document types. By default, JBuilder 4 is configured with the -Xverify setting. To successfully use the XMLC wizard with JBuilder 4 on Linux, you can comment out the following line the <jbuilder_root>/bin/jdk.config file.

vmparam -Xverify:none

How come the application wizard does not generate a multiserver.conf file?

The application wizard generates servlet.conf instead of multiserver.conf for compatibility with both Enhydra 3.x and Enhydra 4. The Enhydra 3.x web server configuration file can have any name, but the default file name is multiserver.conf. Enhydra 4 provides many other services and each may have it's own configuration information. Enhydra 4 requires that the web server configuration file be named servlet.conf and that it reside in a servlet directory.

Can I customize what files the application wizard will generate?

Yes, you can modify and add templates to customize application generator. Starting with Kelp 2.02, the templates are included in the toolbox.jar file. The application wizard looks in the <enhydra_root>/tool directory and within the toolbox.jar file. Files outside of the jar take precedence.

The default templates do not include support for the administration console. You could add support by adding a mutliserverAdmin.conf template and by adding a reference to the new multiserverAdmin.conf file in the servlet.conf.template. The following steps guide you through the process

  1. Extract...
    template/en3app/input/conf/servlet/servlet.conf.in.template
    ...from...
    <enhydra_root>/tool/lib/toolbox.jar
    ...into...
    <enhydra_root>/tool/template/en3app/input/conf/servlet/servlet.conf.in.template
     
  2. Add the following lines to the extracted servlet.conf.in.template file:
     
    Application.MultiserverAdmin.ConfFile = multiserverAdmin.conf
    Application.MultiserverAdmin.Description = "Multiserver Management Console."
    Application.MultiserverAdmin.Running = yes

    Channel.HttpConn8001.AdminChannel.Servlet = MultiserverAdmin
    Channel.HttpConn8001.AdminChannel.Url = /
    Channel.HttpConn8001.AdminChannel.Enabled = yes
     
  3. Copy and rename the muliserverAdmin.conf file from...
    <enhydra_root>/apps/multiserverAdmin.conf
    ...to...
    <enhydra_root>/template/en3app/input/conf/multiserverAdmin.conf.in
     
  4. Edit the multiserverAdmin.conf.in and replace the line..
    Server.ClassPath[] = <enhydra_root>/lib/admin.jar
    ...with...
    Server.ClassPath[] = @JAVA_ENHYDRA_PATH@/lib/admin.jar

Now when you generate an Enhydra super-servlet with the application wizard, it will have support for the administration console on port 8001.

How can I use Enhydra's administration console with generated applications?

The application wizard generates startup files for a test environment that includes only the application you are currently developing. The test environment is intended for development only. The test environment does not support the administration console. Once your application is complete, you can deploy the application into the production Enhydra configuration that is launched through the multiserver script. When you start Enhydra with the multiserver script, you get full support for the administration console.

You can also modify the application wizard templates to add support for the administration console to the generated test configuration. For more information on the steps required to modify the templates, see the FAQ on customizing templates

Why does the Java compiler fail to find some classes when I use make to build a generated application?

The templates included with Kelp 2.0 contain incorrect class path settings. The invalid CLASSPATH statement is in the generated config.mk files. The problem does not show up until you add a class that references another class in your source directory. To correct the problem, replace each instance of...
CLASSPATH="./src/"$(PS)...
...with...
CLASSPATH="$(ROOT)/src/"$(PS)...

The problem has been corrected in the templates that come with Kelp 2.0.2.

What tools are in the toolbox.jar?

The toolbox jar contains 3 tools that you can run from the <enhydra_root>/tool/lib directory. The tools are run using java's -jar option as shown:

java -jar toolbox.jar

The three tools include an archive builder, the application wizard and a configuration utility. The archive builder is used to create jar files for Enhydra super-servlets and war files for web applications. The application wizard is the same wizard that appears within a Java IDE when using the Kelp add-in. The configuration utility is used within generated makefiles to copy files from the input directory to the output directory and make replacements to input template (.in) files.