The definition of method calls at development time is made much easier by the Method Lookup Wizard. This wizard offers:
•Lookup of Java archive files and Java packages.
•Lookup of available classes.
•Lookup of constructors, fields and method.
To use the Method Lookup Wizard:
|1.||From the Definer menu bar, choose Define, RDMI, J2EE Components.|
|2.||Execute a query to retrieve the component that you want to work with.|
|3.||Click the Lookup button next to Physical Method on the Method tab page. The first of the Method Lookup Wizard pages appears. |
|The first page of the wizard allows you to select a Java package name or a Java archive name to limit the number of component classes that will be retrieved. If you supply a Java archive, that archive should be in the class path so that it is visible in the Definer. You can then select this archive name on the first wizard page.|
|4.||Click Next. The second Wizard page appears.|
|The second wizard page displays all the class names that were selected using the first wizard page.|
|5.||From this list, one class can now be selected.|
|6.||Click Next. The third and final wizard page appears, displaying all fields, methods and class methods of the class selected in the previous step:|
|You can recognize the physical constructors of the Java components by their syntax. Their syntax is:|
this=new java-package-name.method-name(argument, ...)
|7.||Select one of the methods and click Finish to insert the selected method into the Physical Method field of the J2EE Components window. This causes the current content (if any) to be overwritten. If this is not what you want, copy and paste the Method from the wizard to the Physical Method field.|
|8.||The method selected from the wizard passes RDMI parameters sequentially via placeholders. For example in:|
|The ":0" will pass the first parameter of the parameter. You can edit the method to pass parameters in a different order or to pass literal values. For example, a literal value (a file name in this example) could be passed as follows:|
For more details, refer to "Method invocation syntax".