Creating an External Custom Webject
You can create Info*Engine external custom webjects by coding a public class within a unique Java package. The class name must be unique and should follow the standard Java naming rules.
The Info*Engine webject name is derived from the class name by separating each word in the name with a hyphen. For example, if the class name is “averageColumn” then the webject name is “Average-Column.”
Webject names are not case sensitive.
You must code the class so the custom webjects in the class:
• Are implemented as static methods.
• Take a com.infoengine.object.factory.Task object as their only argument.
• Return a com.infoengine.object.factory.Task object.
• Throw IEException on error.
For example, the signature for the method that implements the Average-Column custom webject is the following:
import com.infoengine.object.factory.Task;
public static Task averageColumn ( Task task ) throws IEException {
:
:
Task response = new Task();
response.addVdb ( group_out );
return response;
:
:
}
You can put the code for multiple custom webjects in the same class. For example, if you have private methods that are used by multiple custom webject methods, the private methods and the custom webject methods can be in one class in a package.
When compiling the NumericColumnWebjects.java file, you must add the ieWeb.jar and servlet.jar files to the classpath. To make your compiled class files automatically available to Info*Engine through the JSP engine, you can put the files in the WEB-INF/classes directory where Info*Engine is installed. If this directory does not exist you can create it.