Hello Dominique!
Here's a short answer from me, I will probably address only a part of your question :-)
Hope that others will complement my answer, and especially point out which is preferred I.1 or I.2 (Berin? ;-)
Wednesday, May 28, 2003, 12:04:56 AM, you wrote:
DP> 3) What puzzles me, in the example above, is that I see that we simply
DP> do the getContainer()!?!?! (shouldn't it be named a getService() or
DP> something like that??? ) with absolutely no parameter to select the one
DP> that I want and then do a run on the returned Object. What I need is to
DP> be able to select a particular service based in a parameter to the
DP> getContainer and then call the getA or getB from one another with the
DP> returned reference and system.out.println the result.
I. As I understand Fortress spirit and design you have two alternatives:
Both examples will work. In my approach with the GUIApp application framework, we had to wait for the user to end the application naturally. What we did was override the container class to implement Runnable. That way we have something like this:
fortressConfig.setContainerClass(
"org.d_haven.guiapp.container.GUIApp" );// ....
((Runnable) cm.getContainer()).run();
When run() ended, we clean up nicely. It works rather well.
II Swing-specific
I have a Swing framework based on Fortress at http://d-haven.org/guiapp You might be able to learn something from it, or even better, help out with it.
-- "You know the world is going crazy when the best rapper is a white guy, the best golfer is a black guy, The Swiss hold the America's Cup, France is accusing the US of arrogance, and Germany doesn't want to go to war. And the 3 most powerful men in America are named 'Bush', 'Dick', and 'Colon' (sic)".
-----Chris Rock
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
