Mailing Lists: Apple Mailing Lists

Image of Mac OS face in stamp
 
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Application does not start (on some Mac OS X 10.2 systems)



Dan Caprioara <email@hidden> wrote:

>I have an editor written in Java packed as an .app. The application runs
>fine on Mac OS X 10.1.
>
>On some Mac OS X 10.2 systems, the application just displays the dock
>icon and the system menu and nothing else. The user can only quit. This
>situation is persistent: there are systems that always allow the editor
>to run, and others that do not.
>
>I verified two installations, one working, the other not working, and
>there were no differences in files or permissions.

When was the app-bundle created? With what tool? Under which version of
Java? How did you compare files, the 'cmp' command?

When an app-bundle is built, the creating tool (MRJAppBuilder,
ProjectBuilder, etc.) copies the "app-launcher stub" executable from the
Java framework into the Contents/MacOS/ directory. Depending on the tool,
it will name it with the target-name, or leave it "JavaApplicationStub".

Anyway, each version of Java on Mac OS X has had a different launcher-stub.
In my experience, these stubs work fairly well across different OS
versions, but maybe there's a problem with one particular combination of
launcher-stub and OS version.

Another possibility is that somehow the bundled launcher-stub has gotten
corrupted. If this happens on one copy of the program but not another, you
can have mysterious "unlaunchable" apps, whose misbehavior depends on their
origin (fruit of a poison tree or not).

You can use the Finder to copy the stub from one app-bundle to another.
Just contextual-click on the app-icon (won't work in 10.1 List views) and
choose "Show Package Contents".

The master launcher-stub is in:
/System/Library/Frameworks/JavaVM.framework/Resources/MacOS/

You can use it as a master-copy for doing your own "brain transplants" on
bundled Java apps, or simply for comparing with what you have in a given
bundled app.

I have also done "personality transplants" on app-bundles, adding a jar
with a different program (frequently a diagnostic that prints all
properties to console) and changing the classpath and main-class. I've
found misconfigured plists and other oddities this way.

Finally, if you're still using the "MRJApp.properties" file, consider
translating its declarations to the equivalent Info.plist form. The
MRJApp.properties technique may have a subtle problem that only shows up on
some 10.2 systems.

-- GG





Message: 2
Date: Wed, 27 Nov 2002 10:32:05 +0200
From:
To: Java-dev <email@hidden>
Subject:

Hello,

I have an editor written in Java packed as an .app. The application runs
fine on Mac OS X 10.1.

On some Mac OS X 10.2 systems, the application just displays the dock
icon and the system menu and nothing else. The user can only quit. This
situation is persistent: there are systems that always allow the editor
to run, and others that do not.

I verified two installations, one working, the other not working, and
there were no differences in files or permissions.

Other aspect. I have inserted a debug section creating a file in the
user home in the very begining of the program. The file was never
created. I also tried to connect via a socket to a logging server, but
with no success. I think the main class is not executed.

Please advise.

Thank you,
_______________________________________________
java-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/java-dev
Be sure to read the FAQ http://developer.apple.com/java/faq/ before posting
Do not post admin requests to the list. They will be ignored.



Visit the Apple Store online or at retail locations.
1-800-MY-APPLE

Contact Apple | Terms of Use | Privacy Policy

Copyright © 2007 Apple Inc. All rights reserved.