Thanks Christopher, I'll give this a try.
Dave
- Original Message -
From: Christopher Williams [EMAIL PROTECTED]
To: Tomcat Users List [EMAIL PROTECTED]
Sent: Tuesday, September 23, 2003 1:17 AM
Subject: Re: Javaw
Use Windows Scripting. Let's say that your program is called myApp
I cannot add all the class files I need to a shortcut that calls Javaw (due to the
number of characters) so I have created a batch file for same. In order to suppress
the DOS window I call the file from another batch file. Does someone have a more
elegant method?
TIA,
Dave
Hi All,
TomcatEmbedded stops unrepentantly and I cannot see a pattern. I have successfully
queried and updated the database (Pointbase) and I receive the following error:
LifecycleException: Container StandardContext[/examples] has not been started
at
Yoav, All,
BrowserLauncher works great! Once EmbeddedTomcat has started I call the
openURL method.
In creating a desktop icon to call javaw, I receive the error Could not
find the main class. Program will exit. This is the target string:
C:\WINNT\system32\javaw.exe -classpath C:\EmbeddedTomcat
Hi,
After starting EmbeddedTomcat I run my application by entering a starting jsp page.
Something that is not obvious to me is how to accomplish both in one fell swoop. What
is the best way to do this?
TIA,
Dave
When attempting to start Tomcat embedded my process fails when adding the connector.
Any help/insight is greatly appreciated. Dave
snippit
Connector connector = embedded.createConnector(null, 8080, false);
embedded.addConnector(connector);
/snippit
C:\EmbeddedTomcatjava EmbeddedTomcat
John, Schalk, all,
I had copied a servlet jar file from JRun to the Tomcat/shared/lib
directory. Once this was removed the JSPs compile! Moral: JRun and Tomcat
are very different.
Thanks for the replies.
Dave
Hi, After reading the archives I see this is not an uncommon error. I've
tried a
Hi, After reading the archives I see this is not an uncommon error. I've tried a
couple suggestions (of removing java.exe from the winnt/system32 directory as well as
changing the JDK version from 1.4.1_03 to 1.4.1_05), but no luck. Any help in
resolving this issue is greatly appreciated. Dave
