Hi guys,
I have a REALLY strange problem. This is the function I have:
public static void generateXLS() {
try {
String[] command = { cmd.exe, /C, Start, C://
exports//convert.bat };
Process p = Runtime.getRuntime().exec(command);
BufferedReader in =
Why do you think this is related to GWT?
Ian
http://examples.roughian.com
2009/4/29 Scientist ma...@gl-power.nl
Hi guys,
I have a REALLY strange problem. This is the function I have:
public static void generateXLS() {
try {
String[] command = { cmd.exe, /C, Start,
On Apr 29, 1:08 pm, Ian Bambury ianbamb...@gmail.com wrote:
Why do you think this is related to GWT?
Ian
Cause it's working perfectly in Netbeans, and the compile gives no errors.
http://examples.roughian.com
2009/4/29 Scientist ma...@gl-power.nl
Hi guys,
I have a REALLY
OK.
I don't know how much experience you have, but my first question would be:
How do you know it hasn't run - i.e. where do you look for a result?
Ian
http://examples.roughian.com
2009/4/29 Scientist ma...@gl-power.nl
On Apr 29, 1:08 pm, Ian Bambury ianbamb...@gmail.com wrote:
Why do
My experience is very little, my source for checking is the batch file
self. In NetBeans, the batch gets executed perfectly. The batch is
used to convert a .csv file into a .xls, and delete the .csv. I just
can't imagine why the batch would be the problem if it runs well in
another development
The thing is, you have to work out where the failure is happening.
If you know that the batch file isn't being called, then it must be failing
before that (by 'failing' I don't just mean error, but include logic errors
that mean things don't get called).
Personally, I'd put an alert in the
Why not just step through the code in a debugger? Put breakpoints on both
ends of the RPC call go from there.
On Wed, Apr 29, 2009 at 9:59 AM, Ian Bambury ianbamb...@gmail.com wrote:
The thing is, you have to work out where the failure is happening.
If you know that the batch file isn't
I've written this code now:
public static void generateXLS()
{
try {
FileWriter schrijver = new FileWriter(c:\\test.txt);
String[] command = { C://exports//convert.bat };
Process p = Runtime.getRuntime().exec(command);
BufferedReader in = new
It's worth working out why your debugger doesn't work...it really should
and is very useful.
Anyway, it could be that your problem is that you don't call p.waitFor()
after starting the process - this is because when you call
Runtime.exec() it runs the command in a separate process, and your code
