|
|
JBuilder 5 Known Bugs |
|
2001-Jun-25 11:20am gyles19@visi.com | |
| Subcategories:
Answers in this category: | |
| [Add a New Answer in "JBuilder 5 Known Bugs"] | |
| 2002-Jun-10 2:48pm | |
|
|
JBuilder 5's JDatastore won't launch from outside the IDE. |
| See this:
2001-Jun-25 11:19am gyles19@visi.com | |
| [Append to This Answer] | |
| 2001-Jun-25 11:21am | |
|
|
CVSHelper doesn't work on Linux and I can't find it anywhere. |
| A packaging error in the final release of the JBuilder 5 CDROM sent
to manufacturing overwrote the Linux 'cvshelper' binary with the
Solaris 'cvshelper' binary. So, the CDROM contains binaries for
Windows and for Solaris, but not for Linux.
As of 7/4/01, Borland knows of the problem and will make the missing
binary available as soon as possible. Paolo Ciccone of Borland is following
thread "JB5: anyone got CVSHelper working?" in group
news://newsgroups.borland.com/borland/public/jbuilder/ide and will
send the file to anyone who asks while a more convenient distribution method is
being configured.
| |
| [Append to This Answer] | |
| 2001-Jul-04 9:09am | |
|
|
Help | Java Reference does not take you to the correct API JavaDoc. |
| There is a bug in the JB5 help index. It takes you to the javax API Javadoc instead of the java API Javadoc.
To find the java API Javadoc from the javax API Javadoc,
1) Open the 'Content' tab on the left side of the Help viewer. 2) Double click on 'Java 2 JDK 1.3 Documentation' to expand the topic. 3) Click on 'Java 2 Standard Edition 1.3 API Documentation'.
This gets you to the same place JB4 took you.
| |
|
Try renaming the file:
jbuilder5/doc/j2ee12_docs.jar to
jbuilder5/doc/zj2ee12_docs.jar On Unix this changes the order the files are searched and seems to solve the problem. J2EE topics are still findable and the Help | Java Reference works as it did in JBuilder 4. Unix users, be certain to use a lowercase 'z', not an uppercase 'Z'.
| |
| [Append to This Answer] | |
| 2001-Aug-07 3:37pm | |
|
|
JBuilder 5 Bugs inherited from JBuilder 4 |
| |
| [Append to This Answer] | |
| 2001-Aug-07 3:49pm | |
|
|
"Search | Find in Path" refuses to search for string "???" even if pattern matching is disabled. "Search | Find" does allow this to work. |
| The "Find in Path" search is apparently enforcing a pattern match validity test it should be ignoring. Regular "Find/Replace" does not enforce this test unless pattern matching is enabled.
One workaround I use is to preface the search string with a space. IE, search for " ???" instead of "???". (I disabled hard tabs in source files, if you have tabs before the ???, this may or may not work, I haven't tried it.)
| |
| [Append to This Answer] | |
| 2001-Aug-29 10:43am | |
|
|
Sometimes, import package.* statements seem to be ignored. JBuilder's compiler says the classes within such packages can not be found when they are referenced. If the import statements are changed from a package (wildcard) import to a set of class imports, the errors disappear. |
| This is a known bug. It does not happen under all conditions. If it does happen, workarounds are to expand the wildcard into a list of classes you actually used from the package, or to use explicit package.class naming in the source code.
Thus, import javax.swing.*; ... JFrame frame = new JFrame(); could be changed to one of the following forms:
import javax.swing.JFrame; ... JFrame frame = new JFrame();
import javax.swing.*; ... javax.swing.JFrame frame = new javax.swing.JFrame(); 2001-Sep-11 8:46am gyles19@visi.com | |
| [Append to This Answer] | |
| 2001-Sep-11 8:46am | |
|
|
JBuilder5 Memory Leak |
| JBuilder 5 comes back with simular memory leaks I noticed in versions 3.x, but that were fixed in version 4.0. If you do EJB programming, you can watch this leaking especially when you change the EJB pages view between graphical display and XML display of you EJBs. Every time you do this, there is a new request for memory, so if you have a project with many EJBs, at some point you must close JBuilder and start again, because your JBuilder gets at system limit.
2001-Dec-03 2:31am cluib@psi.de | |
| [Append to This Answer] | |
| 2001-Dec-03 2:31am | |
|
|
While trying to restructure a datastore in the designer, I get the following error: "Java Virtual Machine Launcher: Could not find the main class. Program will exit!" |
| To reproduce the problem, perform these steps:
1) Create a new data module and add it to current project. 2) In designer for data module, I add a DataStore and a TableDataSet. 3) Connect the DataStore to "example.jds" and set user name. 4) TableDataSet, I set storeName to the Table name and store to DataStore name. 5) Blue icon for restructure is activated, but it gives me the error if I try and use it. HELP!
You found a bug in JBuilder.
As a workaround you could have DataSet.restructure() be called from your own code at run-time. | |
| [Append to This Answer] | |
| 2002-Jun-10 2:51pm |
| Previous: |
|
| Next: |
|
| ||||||||
|
Java Community
Java Tools |
Code Central JB OpenTools |
Community Recent Threads |
Borland Chat Chat FAQ |
||||||||||||||
|
Feature Matrices 3.0 | 3.5 | 4.0 5.0 | 6.0 | 7.0 |
Shop for JBuilder |
JBuilder Downloads and reg keys |
Report Piracy | ||||||||||||||
|
Online Manuals 4.0 | 5.0 | 6.0 7.0 |
Borland DevSupport's Bug/RFE Form Quality Central Client |
JB Patches & Updates |
JBuilder FAQs TIs | ||||||||||||||
|
JBuilder Newsgroups |
Tamaracka's News Archive |
Mr. Haki's JBuilder Machine |
JGuru's JBuilder FAQ |
||||||||||||||
|
Sun's Bug Parade |
|||||||||||||||||
|
|||||||||||||||||