Answers in this category:
Why did Borland change the licensing and pricing between JBuilder 4 and JBuilder 5?
I'm having difficulty installing JB 5 Enterprise on NT4 Service Pack 5.
Please describe JBuilder 5's Visual Age support. Will it be possible to create forms, components and actions like the way I do in Visual Age?
Is VSS support functional on Linux and Solaris?
I've just installed JBuilder 5 Enterprise on an NT 4.0/SP6 Workstation which already has JB3.5 and JB4.0 installed. When I try to launch JBuilder via a command line, I get the java command's own -help output, and JBuilder itself doesn't launch. JB4 and JB35 stil run just fine. What's wrong?
I just upgraded to JBuilder 5. When I try to run a simple "Hello World" application, I get this error: Exception occurred during event dispatching: java.lang.NoSuchFieldError: BUILD_WITH_PROJECT at archivebuilderfix.Fix.updateBuildProcess(Fix.java:45)
I just installed JBuilder 5.0 (or 6.0) Personal but there are no on-line help, samples, or tutorials. What's the deal?
I'm trying to launch JBuilder and/or open an XML project and JBuilder is tossing this exception: Exception occured during event dispatching:java.lang.NoClassDefFoundError: org/jdom/Elementat com.borland.jbuilder.web.xml.WebXmlWriter.write (unknown Source)...
I've installed JBuilder5 successfully, but the documentation and samples installers won't execute. They insist JBuilder itself isn't present even when I point them directly at the JBuilder5 folder.
On trying to read a very simple xml file (validated by a schema), I get: "General Schema Error: Grammar with uri : http://www.xyz.com/abc , can not found." I am using JBuilder5.0 and the latest vesrion for the Xerces Parser. My classpath also includes crimson and jdom.
I'm going through the servlet tutorial and I'm getting this error message: IOException in: R( + / + null) Connection reset by peer: socket write error""
Using Java compiler of the JDK by sun. Is it possible under JB5 ?
Can JBuilder5 integrate with Oracle 9iAS?
Using Tomcat 4 with JBuilder 5

All,

As many of you know, we have changed the licensing model, name and pricing of JBuilder Foundation, now known as JBuilder 5 Personal for several reasons and I'd like to take this opportunity to share our reasoning behind these changes with you, our customers.

1. The features and functionality of JBuilder Foundation were actually sufficient for many users so that the need to actually purchase Pro or Enterprise versions from Borland was lessened or simply not necessary. This allowed customers to be able to standardize on Foundation for their Java development needs without purchasing licenses from Borland. While Foundation was intended as seeding mechanism for JBuilder, the unintended side effect was a reduction in Professional and Enterprise sales. We have cases where large companies standardized on Foundation as their IDE and did not need or want to purchase JBuilder licenses from us. Foundation was available as a purchased product for $49.95 and as a free download from our web site.

2. We had a choice, to remove functionality from the Foundation, rendering it a much lesser product or to change the licensing terms and limit the product's use for non-commercial development purposes only. We thought the better choice is to leave all the great productivity features in JBuilder Personal, but to limit it's use to learning Java programming or to create applications for non business reasons. For those customers that would be realizing the benefits of JBuilder in a business setting, we felt it would be fair if they could share the benefits of their increased efficiency with Borland through purchases of Professional or Enterprise versions.

We feel we made the best choice, to not limit the functionality of Personal, but to only narrow the scope of it use through a change in licensing terms. So, starting in JBuilder 5 we renamed Foundation to the new name "Personal" and included a license that allows JBuilder to be used for personal, non-commercial purposes.

3. Since we have value added items in the box with the product CD such as documentation and learning materials, we felt a price of $99 more accurately reflected the cost to produce and manufacture the product and still provide Borland with a fair return on its investment for this package. Personal will still be available as a web download without cost in July.

In summary, I can understand the concern that many of you have regarding the changes in the pricing and licensing structure from JBuilder Foundation to JBuilder Personal, but I believe we have taken the best possible approach given the circumstances. JBuilder Foundation was actually my idea (okay I'll take the credit and the heat) and was a very successful seeding mechanism for JBuilder in 1999 and 2000. Except for the changes I've mentioned, we will continue to make this version available to all developers who would like to use it.

I would also like to say thank you *very much* for your support of Borland products and especially JBuilder over the years. In my 10 years at Borland, I have always been extremely proud of the work our people have done on a daily basis...building such unbelievably great products and selling them to the best and most loyal customers in the world.

If we provide a product with high value, at a fair price and support it to the best of our ability, I believe Borland's success will soar and in turn, so will our customers fortunes.

Best Regards, Tony

2001-May-25 11:27am gyles19@visi.com

They are roughly equivalent in visual composition, with JBuilder getting the edge mainly in handling of bean properties. (Example: try to set borders in Swing GUI) It's easier to modify grid bag constraints in JBuilder, however it is more difficult to go between controls while changing constraints.

If you are indeed creating forms using VAJ's Quick Form feature, there is no equivalent in JBuilder.

Both are equal in handling importing components (as Java Beans) and placing them on paletes. VAJ gives a visual representation to non-visual beans while JBuilder places them in a list. VAJ displays BeanInfo descriptions of bean and properties, while JBuilder doesn't.

For actions, JBuilder will do "connections" from events but not properties (you have to use the PropertyChange event and then write code to check for correct property change). There is actually no concept of a connection. You must add code (you are directed to the spot in autogenerated methods) to set target properties. Of course, connections to methods is trivial in JBuilder.

JBuilder does a better job of handling non-bean-aware properties of Swing components.

If you use factory or variable "beans" in VAJ, there is no equivalent in JBuilder, nor is there a "promote bean feature" feature.
2001-Jun-29 11:52am gyles19@visi.com

  Migrating from IBM® VisualAge® to Borland JBuilder 6
  http://www.borland.com/jbuilder/papers/jb6_migrating_visualage.pdf

  Migrating IBM VisualAge to JBuilder 5
  http://www.borland.com/jbuilder/papers/migrating_visualageto_jb5.pdf

If there are feature lists which claim cross-platform support for VSS in JB 5.0 they are in error.

It is possible that Linux/Solaris support for VSS could be available in a future release, if Borland can develop support for 3rd product VSS clients such as SourceGear's SourceOffSite ( http://www.sourcegear.com/sos/index.htm ) but this is not present today.
2001-Jun-21 3:33pm gyles19@visi.com

  # Specify location of Visual SourceSafe and Database
  vmparam -DVSSLocation="E:\VSS\win32"
  vmparam -DVSSCurrentDBase="\\VSSServer\VSS\"

Since VSS is no longer used, these settings are invalid. Edit JBuilder.config and comment out the two vmparam lines above. JBuilder should launch.
2001-Jun-15 3:28pm gyles19@visi.com

For this situation, open the JBuilder 5 cdrom, setup folder, and read the setup_windows_alt.html file with your brower. It contains an alternate method of installing JBuilder 5 which bypasses the auto-launched master installer and takes you through launching the individual installers separately.

(JBuilder Enterprise consists of multiple installers, one for Foundation features, one for Enterprise features, one for documentation, and one for samples/tutorials.)

2001-Jun-15 3:30pm gyles19@visi.com

Convert any UNC paths in your VSS setup to drive-letter paths and edit the JBuilder.config file to reflect the change.

If you don't want or need to use VSS from within JBuilder (IE you won't be using the TEAM menu) then you can comment out or delete the VSS-related settings in the JBuilder.config file.
2001-Aug-21 9:01am gyles19@visi.com

  Failed to start Java VM:3

  http://community.borland.com/article/0,1410,27455,00.html

Remove ArchiveBuilderFix.jar from jbuilder5/lib/ext.

2001-Jul-06 4:39pm gyles19@visi.com

  1) Personal itself
  2) Documentation
  3) Samples and Tutorials

(Actually, I don't recall if the Tutorials are in the samples download or the documentation doanload. )

If you want the entire package, you must download and execute each installer seperately.

If you have Personal but are missing the rest, go here to find them:

   http://www.borland.com/jbuilder/download/addons.html

This page offers the Documentation and Samples downloads for English, French, German, and Spanish for both Windows and Linux/Solaris platforms.
2002-Apr-08 8:59am gyles19@visi.com

If you attempt to replace these packages, especially jdom, JBuilder itself breaks. There was a recent thread where someone wished to use a newer version of JDom so they replaced JBuilder's default jdom.jar with a different one, and JBuilder broke, hard.

You should not make any changes to *any* jar files or library definitions stored within jbuilder5/lib because these jars are on JBuilder's own classpath. Any jars you provide yourself should be elsewhere.
2001-Sep-28 12:22pm gyles19@visi.com

Workarounds people have posted include:

  1) removing extra JDKs from the search path, leaving only JBuilder's JDK
  2) ininstalling all other JDKs temporarily, including 1.2.x and 1.1.x versions.

On windows you may need to reboot before the changes become visible to the installers.

This problem is most common on windows but may also happen on unix platforms as well.

2001-Oct-03 9:43am gyles19@visi.com

2. Type 'set PATH=<path to JBuilder's JDK>' e.g.

   set PATH=C:\jbuilder5\jdk1.3

3. Run doc_install.exe from that same prompt.

2002-Jan-05 8:04am gyles19@visi.com

This is a bug in Crimson.jar. Try to put crimson.jar after xerces.jar in your class path.

2001-Dec-05 10:02am gyles19@visi.com

This is typically due to the fact that your computer is not connected to a network, _and_ you have not defined "localhost" in a "hosts" file.

If you are using Windows, find or create a "hosts" file in the appropriate place (do a search on Google for "Windows hosts file" if you've never heard of such a file, just for background info), and add the following line:

  localhost   127.0.0.1

Editor: On NT4, this file can be found here:

  C:\WinNT\System32\Drivers\etc\hosts

  http://codecentral.borland.com/codecentral/ccweb.exe/listing?id=15463
         

1) Download Tomcat 4 and unzip it to C:\jbuilder5 or whatever location you installed JBuilder. (Remember to preserve the directory structure of Tomcat.)

2) Download the patch for Tomcat 4 from Borland (codecentral.borland.com) It is ID# 16697 and is called "JBuilder 5 Tomcat 4.0 Fix". Unzip the Tomcat4NamingFix.jar file to C:\jbuilder5\lib\ext. (Note: There are also some instructions included in the .zip file that you can look at. The instructions also explain exactly what the patch does).

3) Close JBuilder and then re-open it. Click on Project | Project Properties | Web Server. In the drop-down box, there should now be an option for "Tomcat 4 -nonaming". Select that item and then click on Setup. Browse to the location where you unzipped Tomcat 4 (i.e. c:\jbuilder5\tomcat4.0.x). Select the main Tomcat folder (tomcat4.0.x) and click OK.

4) You will also need to create a new library for the Tomcat 4 jars. To do this, select Tools | Configure Libraries | New. Create a new library called Tomcat 4.0 Servlet (if there is already a library for Tomcat 4.0 Servlet, you don't need to create a new one). If you created a new library, enter the name for the library (Tomcat 4.0 Servlet). Under Library Paths, click on Add and select the following jar files:

  C:\jbuilder5\jakarta-tomcat-4.0.x/common/lib/servlet.jar
  C:\jbuilder5\jakarta-tomcat-4.0.x/lib/jasper-compiler.jar
  C:\jbuilder5\jakarta-tomcat-4.0.x/lib/jasper-runtime.jar

Click OK.

If the Tomcat 4.0 Servlet library was already present, make sure that the jar files above are listed under the Class tab for that library.

5) Now, you should add the Tomcat 4.0 Servlet library to your project. To do this, click on Project | Project Properties | Paths | Required Libraries | Add. Select the Tomcat 4.0 Servlet library that was created in Step 4.

Now you should be able to compile and run your application using Tomcat 4.0.

If you have any additions or corrections to this process, please post them.
2002-Apr-11 7:21am allan_bond@yahoo.com, gyles19@visi.com