Wrapping process makes PL/SQL source code unreadable. Developers can wrap package specifications, package bodies, functions, procedures, type specifications and type bodies. Unfortunately triggers cannot be wrapped. To wrap the trigger code you need to place your source code to a package or procedure and call it from the trigger.
There are two ways to wrap PL/SQL source code.
1. Wrapping PL/SQL source code with wrap utility
Wrap utility takes two parameters. First one (iname) is the PL/SQL source code file and the second one (oname) is the output file that will hold the wrapped code.
wrap iname=example_input_file.sql oname=example_output_file.plb
This is an easy way to wrap source code because you do not need to handle DDLs bigger than 32767 bytes. But this way, you need to save DDLs into different files and execute the wrap command frmo the command prompt for each file.
2. Wrapping PL/SQL source code with DBMSL_DDL package
The DBMS_DDL package contains an overloaded wrap API to wrap PL…
The sample application consists of one page that allows the user to upload files to the server. When the upload starts, a progress indicator displays the current status of the upload operation. The uploaded files are not stored anywhere. Controlling the progressIndicator <f:view>
It is implemented to fulfill our basic needs such as prefix, suffix, comma separation, min/max digits and percentage(%) values.