The naming convention for the generated PL/SQL is to name the corresponding PL/SQL function or procedure with the same name as the corresponding Java program element. In the following cases, however, the PL/SQL naming will not be identical to the Java program element name:
For example, two different Java methods called methodA
methodA(int)
and methodA(java.long.Float)
would
continue to have the same names in the PL/SQL package because the PL/SQL
signatures are unique: methodA
(NUMBER)
and methodA
(ORA_JAVA.JOBJECT
).
In another example, however, for two different Java methods called methodB
methodB(char)
and methodB(byte)
different names
are required in the PL/SQL package because the PL/SQL signatures would be
identical: methodB(PLS_INTEGER)
. So the
first methodB in the Java class remains methodB
in the PL/SQL package, but the second methodB becomes methodB_0
.
For example, a Java method named value would generate the name
value_
in the PL/SQL package.
Understanding the Persistent Naming Option