This field sets the name of the attribute to be used in this JSP tag. Each attribute corresponds to a parameter in the EJB method call for this tag. The attribute name should be something descriptive that indicates its meaning, and the name should not conflict with any other attribute names on the same tag.
This indicates the expected java type for this attribute. It was derived from the method signature on the EJB.
Normally, all of the attributes for a tag must be specified when the tag is used on a JSP page. However, the EJB to JSP tool allows you to specify "default" values for attributes if those attributes are not specified in a tag instance. The default value may be a simple java EXPRESSION, or, if more complex processing is needed, a java METHOD may be written.
A simple java expression may be entered in this field to supply a value for the attribute when none is specified. For example, if an attribute expects java type int, you could enter 7 as the default expression. If the attribute expects a String, you could enter "WebLogic" (quotes included).
If more complex processing is needed to obtain a suitable value, you may write a java METHOD to do so. The text entered here will be the body of a java method in the generated tag code, declared to return the appropriate java type. The method body you are writing is a part of a standard JSP tag handler; thus the "pageContext" variable is available. From the pageContext, you can get access to the current ServletRequest and HttpSession, and use those objects to generate a default value. A common strategy is to derive default values from ServletRequest parameters or from objects in the session. The method must return a value of the appropriate type.
This indicates the name of the java method on the EJB. It was derived from introspecting the EJB interfaces.
This field sets the name of the JSP tag for this method. By default, the tag name will be the same as the method name, and methods on the EJB home will have "home-" prepended. The tag name should be unique with respect to other tag names in this tag library project.
This checkbox sets whether or not the tool will generate a tag for this EJB method. If unchecked, no tag will be generated. You may want to disable a tag if it will not be useful, or if it generates a conflict with another tag during the build process.
This field describes the EJB type that this tag/method operates on. It was derived from introspection of the EJB jar file.
This field describes the return type of the EJB method. It was derived from introspection of the EJB interfaces.
This field shows the signature of the EJB method corresponding to this tag.
You may use this field to write simple notes about this tag.
This displays the name of the EJB. It was derived from reading the EJB deployment descriptor.
This displays the java type of the home for this EJB. It was derived from the EJB deployment descriptor.
This displays the java type of the EJB interface. It was derived from the EJB deployment descriptor.
This describes the EJB type: STATELESS SESSION, ENTITY, or STATEFUL SESSION.
This checkbox sets whether or not the tool will generate tags for this EJB's methods. If unchecked, no tags will be generated for any methods on this EJB.
This sets the JNDI name that the tags will use to look up this bean's home. Normally, you should not modify this, since its default value was derived from the deployment descriptor in the EJB jar file. However, if the bean will be deployed on another weblogic server (i.e., it will not be deployed on the same server where the JSPs will be running), then you will want to modify this field to point to that other server (e.g., t3://otherhost:7001/ejbPath).
This displays the path on the filesystem to the EJB jar file.
This sets the java compiler command to be used when building the project.
This field may be used to set extra compiler flags when building the project (-g, etc).
This sets the java package for the generated java code.
This checkbox sets whether the generated java files should be retained for user inspection after building a project.
This field specifies the type of tag library output you want. For use in a J2EE web application, a tag library should be packaged one of two ways: as separate class files and a Tag Library Descriptor (.tld) file, or as a single taglib jar file. For development and testing purposes, DIRECTORY output is recommended, since a web application in WLS must be re-deployed before a jar file may be overwritten.
This sets the location of the Tag Library Descriptor file when DIRECTORY output is used. It should be a file below /WEB-INF/ of a web application.
This sets the directory where generated classes will be compiled for DIRECTORY output. It should typically be the WEB-INF/classes directory of a web application.
This sets the tag library jar file location for JAR output.
This sets the temporary working directory to be used for assembly of JAR output.
The tool can infer reasonable attribute names by parsing java source files of the EJB interfaces. This field is used to set the directories where the tool will search for source files. You may use the File -> Resolve Attributes menu to re-run the resolve process. When looking for java source files corresponding to an interface class, the tool will look in both the directory specified, and in a sub-directory implied by the interface's java package. For example, for my.ejb.Trader, if the directory given is C:/src, the tool will look for both C:/src/Trader.java and C:/src/my/ejb/Trader.java.
This field is used to set additional jar/directories that need to be specified during the compilation phase of building a project. Normally, you shouldn't need to add any additional elements, but you may need to do so if you use classes in a METHOD body that are not present in the EJB or the core WebLogic distribution.