When attempting to use Parameter Insight into a class in a user-created library which is added to another project, the parameters are appearing as generic parameters (String p0, int p1) rather than their names (String name, int Value). Why is happening?

This behavior occurs when the library is does not have access to the source files. In this case, the decompiler will use the class files to generate a stub source, which will then be used by Parameter Insight. Now, if the source is added to the library, or is available to it, Parameter Insight will instead use the source and thus will show the actual parameter names. Anytime you can see actual parameter names, this is because the source is available.

Often, there are two or more separate archives which comprise a library in JBuilder: an archive that contains only class files, one that includes only source (and one for documentation). For example, the JBCL library definition file (JBCL.library) contains the following description. Notice the different path references that point to each type of archive (class, source, documentation):

---------------------------------------------------------------------

<?xml version="1.0" encoding="UTF-8"?>

<library>

<!--JBuilder Library Definition File-->

<fullname>JBCL</fullname>

<class> <path>[jbcl.jar]</path> </class>

<source> <path>[../src/jbcl-src.jar]</path><path>[../src/bean-res-src.jar]</path> </source>

<documentation> <path>[../doc/jb_jbclref.jar]/ref/jbcl</path> <path>[../doc/jb_reference.jar]/ref/dx</path> </documentation>

<required>Data Express</required> </library>

---------------------------------------------------------------------

If the library definition for JBCL did not have source files, Parameter Insite would use the stub files and would only show general parameter names.