You may have only one Eclipse project, but you are creating _two_ WebObjects applications. The server-side application and the client-side application. While they may share some common classes and the source code may be in the same Sources directory in your project, each application has completely independent build output. The server-side java code is built into /build/MyApp.woa/Contents/Resources/Java/. The client-side is built into build/MyApp.woa/Contents/WebServerResources/Java/
The client application is an independent application in the same way that a Safari/Firefox/IE/etc. are independent applications and not a part of a "standard" WebObjects application. They both just make HTTP requests to a server-side WebObjects application. One gets HTML in return, the other gets serialized EOs. In fact, you can have the same server-side application serve both web clients and Java Clients.
It just happens that when you use Java WebStart the server-side application knows how to distribute the client-side application to the user on-demand via a link on a web page, which makes it seem like you are just running part of the server-side application. Without Java WebStart you would simply need to distribute the client-side application yourself and launch the executable in the finder, instead of launching it via a link in a WebBrowser.
In fact, that's exactly what that launch script is doing. It's launching the client without using Java WebStart. Eclipse doesn't need to be the one that runs that script. You can run it yourself and it should launch the client-side app.
Dave
On Feb 28, 2012, at 3:44 PM, Raymond NANEON wrote:
Hi Dave,
Thank you for your availability and your valuable advice. I found the script and I will modify according to my applications. I do not create 2client / server applications, but only one. All work is done at levels of packages (client and server).
Thank you for your help and your support.