Jolt 1.2 Readme

JoltBeans to your Java development environment.
A Windows NT 4.0 machine with IIS 4.0 installed (included with
Windows NT Option Pack 4).
Required to use the machine as a Web server to use ASP
connectivity for Jolt.
Refer to the README file in the Jolt asp bankapp example for
installation instructions.
Any webserver with servlet execution support to use servlet
connectivity for Jolt.
Refer to the README file in the Jolt servlet examples for
installation instructions.
IX. Known Problems List
1. Case 10-981019-9089
When the Jolt Listener server CLOPT contains "-C ANY -T 2" to set the
session timeout value to 2 minutes, calls to
JoltSessionBean.getSessionTimeOut() to retrieve the session timeout
value always return 0.
2. Case 10-000714-5720
bea.jolt.beans.JoltOutputEvent.getSource() in
bea.jolt.beans.JoltOutputListener prints the following message when it
is invoked when the event received is a Tuxedo application event
(i.e., it is an event sent to the client by an application server
using tpnotify()):
"ERROR:JoltOutputEvent() - jmessage.getDefinition()"
and
JoltOutputEvent.getTextValue("FIELD") returns NullPointerException.
If the event received is a TUXEDO system event, than getSource() and
getTextValue("FIELD") work correctly.
3. Case 10-000714-5723
After a Jolt bean client creates a session, subscribes to an
event, and then calls a service which posts the event using tppost(),
the event listener registered by the client is never called.
This problem always occurs when the server posts an event using
tppost(), and sometimes occurs when the server posts an event using
tpnotify().
4. Case 10-000814-5966
The following sequence of interactions generates incorrect code:
-Create an interaction between a textField and joltServiceBean
-Select source of the interaction to be a textField
-Select JoltServiceBean to response to the dataChanged event of the
file:///C|/Jolt12/ReadmeJolt12.txt
file:///C|/Jolt12/ReadmeJolt12.txt (6 of 8) [4/27/2004 10:35:04 AM]