Releases: nvanwyen/plsql-ws
Release v0.0.6.6
New functionality, this release (2019-05-02):
- Uses table-based Java properties for adding, updating, reading and loading
- Includes views on top of new table structures
- Adds table-based logging for run-time and error messages
- Fix issue #2 (commit: bfc409c)
- Odd issue with
NoClassDefbeing thrown after initial install.
Distribution
ce7ea9fa89c265410a4a7fc7e50a350ef4d5e332 ws-v0.0.6.6.tgz
v0.0.6.3
v0.0.6.1
Adds java_properties, so that System.setProperty( name, value ) can be closely controlled by the called. Also cleans up overlapping items, replacing them with synonyms for backwards compatibility and ease of understanding and requests now return CLOB data, supporting large strings.
b03798cbf81f040fb875f7929af6bc92a004a51f ws-v0.0.6.1.tgz
de29a63c7f1d801d0de2a43ae54fa30147f4c6c5 ws-v0.0.6.1.sha
Also, System.out.println() is now controlled by the property ws.system.output. When set to enabled the dbms_output.get_line()/get_lines() contains the tracing information:
Example:
select ws.rest_request( 'https://remote-services:12345/xml',
'post',
'{"flag":"D", "state":"B"}',
ws.rest_properties( ws.rest_property( 'user-agent',
'mozilla/4.0' ),
ws.rest_property( 'content-type',
'application/json' ),
ws.rest_property( 'Content-Length',
'40' ) ),
ws.java_properties( ws.java_property( 'ws.system.output',
'enabled' ),
ws.java_property( 'javax.net.debug',
'all' ),
ws.java_property( 'https.protocols',
'TLSv1.2' ),
ws.java_property( 'https.cipherSuites',
'TLS_RSA_WITH_AES_256_CBC_SHA256' ) ) ) response
from dual;
In the above example, the backwards compatible rest_properties and rest_property objects can still be used (same thing applies for soap_header and soap_headers). with introduction of java_properties and java_property, we programmatically turned on java network debugging. We also set the https.protocols and https.cipherSuites for establishing the handshake. The use or java_property is equlviant to use -D<property>=<value>.
Finally we set the property ws.system.output to enabled so the when using set serveroutput on in our script, we can see the results.
Finally the API signature has changed for both the rest_request and the soap_request calls. They now return a CLOB for data exceeding 4000 characters, and the headers/properties are now optional. Both of these changes will work with any current implementation dependency against WS. New prototype:
function rest_request( url in varchar2,
mth in varchar2,
doc in varchar2,
pro in rest_properties default null,
jva in java_properties default null ) return clob;
function soap_request( url in varchar2,
xml in varchar2,
hdr in soap_headers default null,
jva in java_properties default null ) return clob;
v0.0.5.16
v0.0.5.11
v0.0.5.7
Fixed HTTPS for REST service calls
b28ca78e4697858292c79f4e7a6c6492b3afc544 ws-v0.0.5.7.sha
deeacc72663d629853527b2980659d2bcbef4f7d ws-v0.0.5.7.tgz
Note: There is a problem is the prime size. The maximum-acceptable size that Java accepts is 1024 bits. This is a known issue (see JDK-6521495). This was reported as bug JDK-7044060 and fixed recently.However, that the limit was only raised to 2048 bit. For sizes > 2048 bit, there is JDK-8072452 - Remove the maximum prime size of DH Keys.
See: