When you specify the class that extends the application (Plug-in Class Name) and the path to that class (Class Path Items), your entries fall into one of four categories:
Package, No; JAR, No The class is not part of a package or a JAR file.
Plug-in Class Name – enter the class file name; for example, “myBob”.
Class Path Items – enter the path to the class; for example, D:\working\.
Package, No; JAR, Yes The class is not part of a package, but is part of a JAR file.
Plug-in Class Name – enter the class name; for example, “myBob”.
Class Path Items – enter the path to the JAR file that contains the class; for example, D:\working\MyJar.jar.
Package Yes; JAR, No The class is part of a package file, but not part of a JAR file.
Plug-in Class Name – enter the class name; for example, “com.foo.myBob”.
Class Path Items – enter the path to the package file; for example, D:\working\.
Package, Yes; JAR, Yes The class is part of a package and a JAR file.
Plug-in Class Name – enter the class name; for example, “com.foo.myBob”.
Class Path Items – enter the path to the class; for example, D:\working\com\foo\MyJar.jar; .
Class Path Items can also take a relative path. “.” corresponds to the controller working directory.
Java package names consists of a series of alphanumeric characters separated by periods. Java expects one-to-one mapping of the package name and the file system directory structure; that is, place the file in the directory structure that mirrors the package name. For example:
Working directory – C:\working
Package – com.foo.myBob
File – C:\working\com\myBob.java
Classpath – C:\working\com\foo\myBob.class
| Copyright © 2005. Sybase Inc. All rights reserved. |
|
|
