Advanced Search

Log In | Not a Member?

Contact ADC

< Previous PageNext Page > Hide TOC

Java HotSpot

Radar #3065092

JBuilder 7 does not launch.

Description:

Once Java 1.4.1 has been installed, JBuilder 7 stops working.

Workaround:

You can modify JBuilder to allow it to launch again under Java 1.3.1. Alternatively, you can launch JBuilder in Java 1.4.1, but only from the command line.

To launch JBuilder 7 in Java 1.3.1:

1. In your JBuilder7 folder, navigate to JBuilder.framework/bin/.

2. Open the jdk.config file in a text editor. You may need to do this from the shell with the sudo command depending on how the permissions to JBuilder7 are set. For example, type sudo vi jdk.config.

3. Add the following line: javapath /System/Library/Frameworks/JavaVM.framework/Versions/1.4.1/Libraries/libjvm_compat.dylib.

4. Save the file and launch JBuilder7 by double clicking the icon.

To launch JBuilder7 in Java 1.4.1 from the command line, navigate to the JBuilder.framework/bin directory inside of the JBuilder7 folder and enter the following command:

System/Library/Frameworks/JavaVM.framework/Versions/1.4.1/Commands/java  -

Xbootclasspath/p:../lib/lawt.jar:/System/Library/Java/Extensions/

MRJToolkit.jar -cp ../lib/activation.jar:../lib/ant.jar:../lib/

beandt.jar:../lib/borlandxml.jar:../lib/bsf.jar:../lib/castor-xml.jar:../

lib/castor.jar:../lib/cx.jar:../lib/dbswing.jar:../lib/dbswingdt.jar:../lib/

dbtools.jar:../lib/dt.jar:../lib/dx.jar:../lib/gnuregexp.jar:../lib/

help.jar:../lib/ias_common60.jar:../lib/ias_common65.jar:../lib/

iastools.jar:../lib/internetbeans.jar:../lib/jakarta-regexp-1.1.jar:../lib/

javaws.jar:../lib/jbcl.jar:../lib/jbuilder.jar:../lib/jdbcx.jar:../lib/

jdom.jar:../lib/jds.jar:../lib/jdsremote.jar:../lib/jdsserver.jar:../lib/

junit.jar:../lib/lawt.jar:../lib/linuxDesktopConfigurator.jar:../lib/

mail.jar:../lib/optional.jar:../lib/sqltools.jar:../lib/unittest.jar:../lib/

webserverglue.jar:../lib/xalan.jar:../lib/xerces.jar:../lib/xml4j.jar:../

lib/xmlbeans.jar:../lib/xmldbms.jar:../lib/bes/agentclient.jar:../lib/bes/

asrt.jar:../lib/bes/client.jar:../lib/bes/guicore.jar:../lib/bes/

jaas.jar:../lib/bes/jcert.jar:../lib/bes/jnet.jar:../lib/bes/jsse.jar:../

lib/bes/lm.jar:../lib/bes/vbdev.jar:../lib/bes/vbejb.jar:../lib/bes/

vbjdev.jar:../lib/bes/vbjorb.jar:../lib/bes/vbsec.jar:../lib/bes/xmlrt.jar

com.borland.jbuilder.JBuilder

Radar #3123712

Applications that use java.endorsed.dirs generate errors.

Description:

If an application specifies JAR files to load with java.endorsed.dirs that application generates an error noting that sharing is disabled.

Resolution:

Using java.endorsed.dirs no longer generates this message. Note that using java.endorsed.dirs prepends the boot classpath. This means that the shared archive normally used in Mac OS X to decrease memory usage and launch time of Java applications, cannot be used. If you use java.endorsed.dirs in an application, that application will not make use of the default shared archive.

< Previous PageNext Page > Hide TOC

Did this document help you? Yes: Tell us what works for you. It’s good, but: Report typos, inaccuracies, and so forth. It wasn’t helpful: Tell us what would have helped.

	Get information on Apple products. Visit the Apple Store online or at retail locations. 1-800-MY-APPLE Copyright © 2007 Apple Inc. All rights reserved. | Terms of use | Privacy Notice