The snippet you sent looks like it's from a Cocoa-Java application;
mine's a Swing app. I wonder if that's my problem - has anyone tried
this with a Swing application?
Just did. It doesn't work.
Oh good. I though I was going mad.
Going back to your original question, maybe you should eliminate
the Swing
alerts. That would let you make your Java app a true headless
daemon, and
you could deploy and launch it as such.
If the daemon still has to present occasional alerts, consider
doing it by
exec'ing another process from the daemon. For example, 'osascript'
can
present an alert, or you could exec() 'java ...' to present a Swing
alert.
If you go the 'java ...' route, you can put all the classes into a
single
jar and exec() a different main class than the Main-Class in the
manifest
that presumably runs the daemon.
Now that's a sensible idea - thanks Greg. Think I'll go the osascript
route.
Adrian
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Java-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/java-dev/email@hidden
