My Oracle Support Banner

Jolt 1.2 - method to print the input buffer looks before invoking call(). (Doc ID 776019.1)

Last updated on MAY 19, 2020

Applies to:

Oracle Tuxedo Jolt - Version 1.2 and later
Information in this document applies to any platform.
Information in this document applies to any platform


The customer would like to know a way/method in JoltRemoteService clsss to print the input buffer before invoking a
call () in Jolt client.

The customer has following in the code:
String[] arr = { "a", "b", null, "c"};
for (int i=0; i<arr.length; i++)
setStringItem("CUSTOMIZED_PARAM_VALUE", i , arr[i]);
Calling setStringItem in the JoltRemoteService class.
After they call the call method JoltRemoteService and then Tuxedo code seems to get the following structure:
{ "a", "b","c" } .. so null in between is skipped 

If it was { "a", "b", null, null, null, "c"}, then tuxedo would get { "a",
"b", c, null, null}. Thus, 
first null gets replaced.  

The order of occurences is certainly not maintained based upon looking at the Jolt code. The items for a message are
maintained in a Java hashtable. Hashtables have no 
guaranteed ordering. Hashtables do not allow null keys or values according to the JDK documentation. 

However, customer insists that they still want to print the buffer before invoking call().  They would like a way to
print how the input buffer looks before they invoke call().

They tried the following and it does not seem to produce meaningful results.
1. getInputs().toString(); - Always results in a null pointer exception
2. getInputs().getHashtable().toString(); - results in printing a
numeric key and a bea.jolt.VNode@<instanceCode>. No details of the
fieldname_value pairs are printed.

They want a way to somehow print what is going across the client-jsl interface as they are not able to figure out how
occurrences work exactly. 
Occurrences do not seem to be maintaining the order.

Jolt 1.2

NOTE:  The attribute values used in this article represent fictitious sample names that are made up as example. Any similarity to actual code, is purely coincidental and not intended in any other manner.


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.