Hi Pierre,
I would recommend this way to launch your WOApp:
Select the application class in the left.
Select Run->Run... from the menu.
Create a new WOApplication or ProfiledWOApplication launch
configuration.
Click run.
This will set
- the application class name
- the DWORoot if required on your plattform
- the NSProjectSearchPath (rapid turnaround mode for applications and
frameworks)
- the working directory
for you.
The next time you can choose this configuration from the debug and
launch buttons in the wolips perspective. The little triangles will
open a popup with list of your launch configurations.
I will take a llok at the application jar problem.
Ulrich
Am Dienstag, 04.02.03 um 17:18 Uhr schrieb Pierre Bernard:
> Hi!
>
> I am wondering what is the recommended way of launching an application
> with WOLips. Besides using the generated Apple-style launcher scripts
> I have determined two methods.
>
> First, the easy one: create a run configuration with the name of the
> application class specified as a main class. Strightforward. Drawback:
> differs notably from Apple's way of launching the application. Most
> importantly, the custom bootstrap class is not used. Thus the
> WebObjects extensions directory is ignored.
>
> This is not a straightforward as it sound as the run configuration has
> to be slightly modified in order to work correctly:
>
> - The WORootDirectory needs to be set for auto-open in browser to work
> (Windows only?)
> - The projects JAR file from the .woa directory need to be added to
> the classpath for WOComponents to find their classes
>
> With these modifications, the run configuration no longer updates
> manually to reflect classpath changes.
>
> Second: Use Apple's class loader by applying the folowing procedure:
>
> 1. Modify the build.xml file in your application project to specify
> the fully qualified name of your application class. This is also
> required for WOLips to correctly generate the standard launch scripts.
>
> 2. Change your run configuration to include the WOBootstrap.jar file
> from your project's .woa in the classpath
>
> 3. Set the main class of your run configuration to
> "com.webobjects._bootstrap.WOBootstrap". One main class to rule them
> all!
>
> This closely resembles Apple's way of starting the application.
> However there are still a few oddities:
>
> - Again, one needs to modify the default classpath
> - The WORootDirectory needs to be set for auto-open in browser to work
> (Windows only?)
> - One needs to add a few VM arguments: -DWOPlatform=Windows
> -DWOLocalRootDirectory=D:\Apple\Local -DWORootDirectory=D:\Apple
> - Stripping down the classpath to only WOBoostrap.jar does not seem to
> work
>
>
> Any thoughts, comments or suggestions?
>
> Why doesn't WOLips define the WOPlatform, WOLocalRootDirectory,
> WORootDirectory and WOUserDirectory properties?
>
> Why doesn't WOLips include the generated JAR file in the default
> classpath?
>
>
> Best
> Pierre Bernard
>
>
> **********************************************************************
> This email and any files transmitted with it are intended solely for
> the use of the individual or entity to whom they are addressed.
> If you have received this email in error please notify the sender
> of this message. (Pierre.Bernar..cl.lu)
> This email message has been checked for the presence of computer
> viruses; however this protection does not ensure this message is
> virus free.
> Banque centrale du Luxembourg; Tel ++352-4774-1; http://www.bcl.lu
> **********************************************************************
>
This archive was generated by hypermail 2.0.0 : Tue Feb 04 2003 - 11:35:42 EST