Error:Java not initialized.
>> I isolated the OBJECT tag from this template on a test page with all > the parameters hard-coded, and I still receive the same error message > - Java not initialized.>> I'm able to run the command line javatest.pl script successfully (i.e. > I get a valid reply from the Verisign test server), so I know that > there's nothing wrong with the new java vm (1.4.1) talking to > Verisign's java app or the verisign website via ssl.>> The hack we're using to get around this problem is a modified version > of javatest.pl called with [SHELL] from the ProcessOrders.tpl page, > but it's far from ideal.>> As another test I copied my WC451 directories and config from our > production server onto this box and was able to process a test order > through ProcessOrders.tpl without any problems. This points more > toward a problem with Webcat 5.1 than with OSX 10.3 (in my mind, at > least).>> I haven't tried WC5.1e and PayflowPro on a 10.2 machine yet. My > desktop and home machines are already running 10.3 and I'm not going > back! :)>> Questions:> Is anyone using Verisign Payflow and Webcat 5?>> If so, are you also using Panther (10.3)?>> If you're still running 10.2, do you have the Java 1.4 update > installed?>>> My conclusion is that there appears to be a bug in the [OBJECT] tag in > 5.1 (5.1c & e) that fails to initialize Java on OSX 10.3.1. If anyone > else has evidence to the contrary, please let me know.>> Thanks,>> Dale>>> -------------------------------------------------------------> This message is sent to you because you are subscribed to> the mailing list Error:Java not initialized. >> I isolated the OBJECT tag from this template on a test page with all > the parameters hard-coded, and I still receive the same error message > - Java not initialized.>> I'm able to run the command line javatest.pl script successfully (i.e. > I get a valid reply from the Verisign test server), so I know that > there's nothing wrong with the new java vm (1.4.1) talking to > Verisign's java app or the verisign website via ssl.>> The hack we're using to get around this problem is a modified version > of javatest.pl called with [shell] from the ProcessOrders.tpl page, > but it's far from ideal.>> As another test I copied my WC451 directories and config from our > production server onto this box and was able to process a test order > through ProcessOrders.tpl without any problems. This points more > toward a problem with Webcat 5.1 than with OSX 10.3 (in my mind, at > least).>> I haven't tried WC5.1e and PayflowPro on a 10.2 machine yet. My > desktop and home machines are already running 10.3 and I'm not going > back! :)>> Questions:> Is anyone using Verisign Payflow and Webcat 5?>> If so, are you also using Panther (10.3)?>> If you're still running 10.2, do you have the Java 1.4 update > installed?>>> My conclusion is that there appears to be a bug in the [object] tag in > 5.1 (5.1c & e) that fails to initialize Java on OSX 10.3.1. If anyone > else has evidence to the contrary, please let me know.>> Thanks,>> Dale>>> -------------------------------------------------------------> This message is sent to you because you are subscribed to> the mailing list DOWNLOAD WEBDNA NOW! The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
DaleI just spend 3 days sorting this out on w2k.Java not initialized is due to WebDNA engine not having access to the Java Virtual Machine.WebDNA required the latest Java virtual machine which I downloaded from Sun.You will also need to open WebCatalog prefs file in a text editor and make sure that the path to this is correct.Then just to make sure EVERTHING resets properly ... reboot the machine.On Monday, November 24, 2003, at 07:58 PM, Dale LaFountain wrote:> Hi all,>> I'm finally trying to upgrade our main ecommerce server to 5.1 on our > new Dual 2Ghz G5 running OSX 10.3.1, but I'm having problems getting > the Verisign Payflow Pro module to function properly.>> I fixed several configuration errors in the default install that > entirely prevent Payflow from having a remote chance of functioning at > all (I'll detail these in a separate email). After several hours of > tweaking prefs, soft links, and templates, I'm confident that > everything is now configured identically to our fully functioning > 4.5.1 installation.>> When running the ProcessOrders.tpl template, the LastPayflorProHit.txt > file is updated to contain:> OHS:
Top Articles:
Talk List
Related Readings:
showcart is slow (1998)
WebCatalog NT (1996)
random within a specified range (2001)
emailer (1997)
Opinion: [input] should be called [output] ... (1997)
Mixing and/or in searches (1998)
[SearchString] usage (1997)
Help! WebCat2 bug (1997)
preserving the zero's (1999)
Databases.tpl (2000)
FoxPro & WebDNA (2006)
Am I going senile? (Price recalc based on quantity) (1997)
Grep Ampersands (2008)
PCS Frames-Default page is solution! (1997)
Re2: Calculating multiple shipping... (1997)
Redirect (1998)
Search Question (2003)
Using WebCat for product info requests (1997)
Dual 2GHz G5 (2003)
Help name our technology! I found it (1997)