(I
actually prefer to start JRun manually and keep this window open as I often
change jrun.xml, web.xml etc and restart the server)
There's a benefit to keeping the JRun command prompt
window open when developing Flex applications... it's convenient
to use console logging to trace HttpService, WebService and RemoteObject
requests when developing locally.
-----Original Message-----
From: GroupOne Dev. [mailto:[EMAIL PROTECTED]
Sent: Monday, February 28, 2005 1:28 PM
To: [email protected]
Subject: RE: [flexcoders] Flex Trial Edition - Setting up JRun as Windows Service?
I am using the integrated
Jrun as I am just playing with this on my personal workstation right now.
I just was hoping to be able to start it automatically and then not have the
command prompt window up all the time as well.From: GroupOne Dev. [mailto:[EMAIL PROTECTED]
Sent: Monday, February 28, 2005 1:28 PM
To: [email protected]
Subject: RE: [flexcoders] Flex Trial Edition - Setting up JRun as Windows Service?
Thanks
-- Jeff
From: "Clint Tredway" <[EMAIL PROTECTED]>
Sent: Monday, February 28, 2005 12:24 PM
To: [email protected]
Subject: RE: [flexcoders] Flex Trial Edition - Setting up JRun as Windows Service?
are you using
the integrated Jrun or full Jrun? If you are using the integrated Jrun, I
*don't believe* you can run it as a service. Full Jrun will run as a windows
service.
I use the
integrated version for dev purposes and I have a shortcut setup to start it when
I need to.
-----Original Message-----A little off topic, but hopefully somebody knows a bit more about this than I do. I downloaded and installed the trial version of Flex about a week ago. Out of the box, it appears I have to go find the jrun.exe file and start it manually every time. Has anybody set this up as a Windows service that can start automatically?
From: GroupOne Dev. [mailto:[EMAIL PROTECTED]
Sent: Monday, February 28, 2005 12:20 PM
To: [email protected]
Subject: [flexcoders] Flex Trial Edition - Setting up JRun as Windows Service?
Thanks
-- Jeff

