Mailing List Archive: 49091 messages
  • Home
  • Script library
  • AltME Archive
  • Mailing list
  • Articles Index
  • Site search
 

Calling rebol script from inside java application

 [1/3] from: hallvard::ystad::helpinhand::com at: 11-Dec-2000 22:47


-- Unable to decode HTML file!! --

 [2/3] from: hallvard:ystad:helpinhand at: 12-Dec-2000 8:19


Hello everyone, Sorry about the multiple submissions. It seems I need to be rough with my email client to have it obey. Hope it works this time. I have a problem with calling a compiled rebol executable (R/command runtime) from inside a java application. The script.r is fairly simple: it computes a few values and simply prints them out. It works fine as cgi, and also when I call it *as a script* from the java application. But the compiled code won't work, and I can't even get the output to an MS-DOS console... However, when I run the executable from within my java application with the statement Process p = Runtime.getRuntime().exec(Command); the exit value returned is 0, even if my rebol script ends with make error!. If I run the executable with the -cs flags, java catches the output Unable to find encapsulated data . If I send only the -s flag, I have the Rebol console popping up, and java catches "no name". Can anyone tell me what I am doing wrong? How can I get output from the executable to the DOS console instead of to the Rebol console? Has anyone any experience in running Rebol (executables) from java? Regards, Hallvard Ystad

 [3/3] from: dan:rolander at: 12-Dec-2000 3:43


Hallvard, This sounds very similar to the problem I was having: When running a compiled Rebol executable from DOS while passing it command-line arguments, I get the error "Unable to find encapsulated data", and when running it as a Windows application I lose the first argument (if there is only one argument 'none' is returned). I reported this to commandcare as a bug yesterday and Bo/RT reported back to me that he verified that command-line arguments are not working properly in the current version of Runtime and he's entered it into their bug database as a high priority. Regarding when we can expect it to be fixed, we'll have to wait until the next release of Runtime and he wasn't sure when that would be. Bummer, eh? Dan