|
|
JBuilder 4 Known Bugs |
| Bugs known to exist in JBuilder 4. If you have a work around, feel free to comment.
Patches for some of these issues may be found here:
http://www.borland.com/devsupport/jbuilder/ 2002-Apr-16 9:08am gyles19@visi.com | |
| Subcategories:
Answers in this category: | |
| [Add a New Answer in "JBuilder 4 Known Bugs"] | |
| 2002-Apr-16 9:08am | |
|
|
jbuilder -build throws a null pointer exception if there is an archive node in the project |
| Josh Fletcher of Borland writes: However, note that the archive should have been correctly built. This error doesn't seem to actually cause the build process to fail, it's just kind of annoying.
Bill Joy of Borland noted: (paraphrase) http://www.mers.com/MERLIST/BORLAND/PUBLIC/JBUILDER/DEPLOYMENT/4926.HTML 2001-Jan-08 11:50am gyles19@visi.com | |
| There is a patch for this issue here:
http://www.borland.com/devsupport/jbuilder/downloads/jb4_Archive_Builder_update/
| |
| [Append to This Answer] | |
| 2002-Apr-16 9:04am | |
|
|
My project references class files for which I have no source. JB3.5 would compile this, but JB4.0 won't. What's wrong? |
| There is a bug in JBuilder 4.0 where the compiler seems unable to find class files. Borland has logged this bug.
(Editor's Note: I seem to recall an older reference to this that implied it
was a problem with class files inside of or outside of jar files, one or the
other. If your classes are stand-alone, try sticking them into a jar, or
vice versa.) | |
| [Append to This Answer] | |
| 2001-Jan-08 11:40am | |
|
|
TogetherJ Javadoc comments confuse JBuilder 4.0? I'm getting "unclosed comment at line <line #>" |
| Yes, this is a known bug in JBuilder 4.0.
2001-Jan-08 10:17pm gyles19@visi.com | |
| [Append to This Answer] | |
| 2001-Jan-08 10:17pm | |
|
|
"Delete IIOP generated files" deletes everything! |
| Frank Nicolas wrote:
"I wanted to remove IIOP generated files. I selected all my files, including the folder, right clicked and selected Remove Generated Files... and ALL my files were gone !!! This seems to happen if you put a folder into your selection. Even worse, they have not been moved into the Garbage Can so I can't restore them. Is this bug already repported (I could not find anything on Borland site) ? Is there any patch fixing it ? Bill Joy replied: "Yes, this is a very nasty bug which was just noticed recently by an internal user. It appears to be in every all-Java version of JBuilder which has been shipped. I am working on a patch and will send you a copy when it is ready. Sorry for the problem and the loss of your code. Please avoid selecting any Folder or Package nodes when doing a Remove Generated Files operation until you have the fix."
(NOT IN MERS YET)
| |
| Josh Fletcher writes:
There's a patch for this on CodeCentral: http://codecentral.borland.com/codecentral/ccweb.exe/listing?id=15549 2001-Feb-05 8:30pm gyles19@visi.com | |
| [Append to This Answer] | |
| 2001-Feb-05 8:30pm | |
|
|
I can't define another application server. |
| Lionel Siau writes:
Bill Joy responds:
| |
| [Append to This Answer] | |
| 2001-Jan-15 8:51am | |
|
|
Should the "Include debug info" switch affect the serialVersionUID? |
| John McGrath wrote:
It should not, but I can tell you what is happening. When the class is compiled with debug, JBuilder generates code to initialize member variables that are initialized to compile-time constants. This affects the Serialization Version UID for the class, since it creates a static initializer block. This will only occur for classes where all of the static final variables are initialized with compile-time constants. I have a work-around that will eliminate the problem for you. If you create a static, non-final variable with an initializer, it should always create the static initializer, so the Serialization Version UID will be the same whether or not you compile with debug information. For example, add the the following to your class.
private static int DUMMY = 1;
The other thing you can do is to explicitly specify the Serialization
Version UID for the class. Although I am not that familiar with the
issues concerning serialization in CORBA, doing this is critical when
you store serialized versions of classes and may need to deserialize
them with a modified version of the class.
| |
| See also: 2001-Jul-09 2:28pm gyles19@visi.com | |
See also this Borland FAQ:http://community.borland.com/article/0,1410,27558,00.html 2001-Aug-09 6:58pm gyles19@visi.com | |
| [Append to This Answer] | |
| 2001-Aug-09 6:58pm | |
|
|
Find in Path won't search for wildcard characters even if 'pattern match' is unchecked. The current file 'Find' command will do this. |
JBuilder 4 Foundation will not attempt to 'Find in Path' search for
a string which contains only wildcard characters, even if 'Pattern
Match' is unchecked. It responds with an error dialog which says:Cannot search for a string containing only wildcards.
The 'Find' command which searches the current open file does do this
correctly, and searching for a string containing only wildcard
characters works okay.
| |
| [Append to This Answer] | |
| 2001-Jan-22 10:21pm | |
|
|
I'm using a non-English keyboard and JBuilder's license dialog won't accept the ? character. |
| There is some sort of problem with keymappings in the license dialog.
Special characters in the string aren't recognized.
To work around this, temporarily change your keyboard locale to US English. Launch JBuilder with the -license option and enter the serial number and registration string in English. Exit JBuilder.
Now change your keyboard locale back to your preferred setting.
| |
| See also this Borland FAQ:
http://community.borland.com/article/0,1410,27240,00.html 2001-Aug-08 7:46am gyles19@visi.com | |
| [Append to This Answer] | |
| 2001-Aug-08 7:46am | |
|
|
Team/CVS Project Create Module fails on Windows 2000 |
JBuilder's CVS support is using a form of Runtime.exec() which does not handle paths with spaces.
Windows 2000's user.home path contains, in part, C:\Documents and SettingsThe command line JBuilder is attempting to execute is: C:\Documents and Settings\...\cvscmd.batThe Runtime.exec() call is parsing the string and assuming the first space delimits the command from the parameters. So, the JVM is trying to execute the command "C:\Documents" instead. The workaround for this problem is to force JBuilder to use a different directory for user.home. Create a directory, say: C:\MyProfiles\mynameOr select something which already exists and which contains NO spaces in its path. Now edit JBuilder4/bin/jdk.config and add the following line at the end of the file: vmparam -Duser.home=C:\MyProfiles\mynameThis will create a new user.home location for JBuilder. JBuilder will ask you to re-enter your License information, and it will lose any customizations stored in your original .jbuilder4 directory. (You may be able to copy the contents of the original .jbuilder4 directory to the new location, but I haven't tested this. Beware any paths stored within any of those files, they may point back to the old location.) Another possibility would be to change the location of your Windows user profile. 2001-Jan-22 7:25pm gyles19@visi.com | |
| [Append to This Answer] | |
| 2001-Jan-22 7:25pm | |
|
|
Compiler Error: "Error #: 2301 : internal compiler error: java.lang.NullPointerException" |
See Borland FAQ:http://community.borland.com/article/0,1410,26450,00.html 2001-Jan-22 9:50pm gyles19@visi.com | |
| This compiler error can also be generated when by accident in your code is a lost 'count' variable which is used but never declared.
2003-Dec-19 9:40am jeroen@mvsd.nl | |
| [Append to This Answer] | |
| 2003-Dec-19 9:40am | |
|
|
Unreported Exception error message in an anonymous class |
Summary: When JBuilder compiles an anonymous class, it is required to provide
default anonymous constructors. However, some anonymous classes can throw
exceptions in the constructors and so these must be declared by the compiler.
JBuilder fails to provide the throws clause, thus causing the error message.
Because one isn't allowed to define an explicit constructor for an anonymous
class, the workaround is to convert the anonymous class into a named inner
class and explicitly declare the constructor and its throws clause there.
Example code from Vito:
Here follows a more straightforward TestClass that reproduces the bug,
followed by a TestClass2 that compiles correctly with JBuilder4:
----------TestClass
compilin with JBuilder 4 gives error "TestClass.java": Error #: 360 :
unreported exception: java.io.FileNotFoundException; must be caught or
declared to be thrown at line 15, column 43,
while compiles correctly with javac:
package test;
import java.io.*;
public class TestClass {
public TestClass() {
try {
instantiateAndClose();
}
catch (Exception x) {
}
}
public void instantiateAndClose() throws Exception{
FileInputStream fi=new FileInputStream("testfile"){
protected void finalize() throws IOException {
}
};
fi.close();
}
}
-----------------------------
Follows TestClass2, where I declare the class MyFileInputStream with the
correct constructor, that compiles correctly with JBuilder4:
---------TestClass2
package test;
import java.io.*;
public class TestClass2 {
class MyFileInputStream extends FileInputStream {
public MyFileInputStream(String name) throws FileNotFoundException {
super(name);
}
protected void finalize() throws IOException {
}
}
public TestClass2() {
try {
instantiateAndClose();
}
catch (Exception x) {
}
}
public void instantiateAndClose() throws Exception{
FileInputStream fi=new MyFileInputStream("testfile");
fi.close();
}
}
---------------
Vito.
2001-Feb-12 9:59pm gyles19@visi.com | |
| [Append to This Answer] | |
| 2001-Feb-12 9:59pm | |
|
|
UNVERIFIED: Jbuilder accepts assignments to 'final' variables. |
| JBuilder will compile code where you assign a value to a final. Javac will correctly flag this as an error.
2001-Feb-15 1:46pm gyles19@visi.com | |
| [Append to This Answer] | |
| 2001-Feb-15 1:46pm | |
|
|
Foundation won't compile a project created/altered by a sample, tutorial, or wizard. |
| I'm not sure exactly what the problem is, but it seems that some of
the JB4 samples, tutorials, and perhaps wizards assume that
automatic source discovery and compilation is enabled in the project
so they don't create file or package nodes for the files they create.
Sometimes the resulting project will not compile due to 'missing'
source files.
The workaround is to manually add subpackages or individual files within the subpackages to the project.
Since JBuilder uses its project pane more as a list of packages than
a list of individual files, this problem is visible only when a wizard
or sample creates a new subpackage which is not already noted in the
project pane. Adding a single source file from the new subpackage
should be sufficient to get the project to compile.
| |
| [Append to This Answer] | |
| 2001-Apr-20 10:37am | |
|
|
The JSP Tutorial doesn't work. |
|
The JSP Tutorial in JB4 doesn't match the current JSP Wizard very well. The Tutorial implies the Wizard has only one panel, but in fact it now has three or four. Just step through the wizard accepting the defaults.
Also, there is an error in the body of the Tutorial. When the Tutorial instructs you to alter the jsp file, it gives you the wrong jsp tag. The result is a compilation error within Tomcat when you try to run the altered JSP: Error in jsp service(): Unable to compile class for JSP {insert horribly long filename here} Where the Tutorial says to edit JspWithCountingBean.jsp and add the line: <P>This page has been visited <%= JspWithCountingBeanId.count() %> times.<BR> What you should really add is: <P>This page has been visited <%= JspWithCountingBeanBeanId.count() %> times.<BR> IE there is a Bean missing from the class name in the JSP
tag.
| |
| [Append to This Answer] | |
| 2001-Mar-16 5:23pm | |
|
|
JBuilder4 doesn't work properly with J2ME SDK. |
| Symptoms:
1 JBuilder4 forgets the configuration settings for the J2ME SDK. 2 After an HHE is created, JBuilder's main menu becomes unstable. 3 JBuilder won't exit properly. 4 File|New|Micro|Spotlet is disabled. Solution:
1 Ignore Tools|Configure J2ME SDK, use Tools|Configure SDK instead. Select the path to j2me_cldc. 2 Copy the preverifier.exe from the j2me_cldc\bin\win32 folder to j2me_cldc\bin 3 Verify that HandheldExpress4beta.jar is in jbuilder4\lib\ext.
| |
| [Append to This Answer] | |
| 2001-Apr-04 1:05pm | |
|
|
I can't find file setup_windows.html! |
| Borland placed file setup_windows.html, setup_linux.html, and setup_solaris.html on the cdroms they sell. Later, when they created the downloadable version of Foundation, they renamed this file to index.html.
Unfortuately, the last panel of the executable installer still refers to the original name of the file, setup_windows.html.
When you unpack the zip file you downloaded, it will create a subdirectory 'foundation', and the index.html file you are looking for is in this subdirectory.
| |
| [Append to This Answer] | |
| 2001-Apr-05 6:06pm | |
|
|
After running a wizard, keyboard context is stuck in a source file and won't move to the desired file. |
| Sometimes, especially after running some wizards, the keyboard context is stuck inside a particular source file even through the text cursor is visible in a different source file. Typing characters causes changes to the wrong source file.
I don't know why this happens. To regain control of the keyboard focus, you can use Window | New Browser to open a new window, then close the old browser window. The new browser window will have normal keyboard focus again. Another method is to right-click in the source pane and use one of the 'split view' functions to add a new vew. Close the original view. Keyboard focus should act normally. Closing JBuilder completely will also correct the problem.
| |
| [Append to This Answer] | |
| 2001-Apr-20 10:42am | |
|
|
Why does JB4f associate file-extensions like *.class, *.java, *.idletc. with itself even when I don't want to? (I clearly said 'No' when it JB asked. |
| Josh writes:
This is a bug. Even if you say "No" to the dialog the files still get associated with JBuilder (incorrectly as well I think). Unfortunately, once this is done there's no way to "undo" it other than to manually change the associations.
Also, for future reference, if you run with JBuilder.exe instead of JBuilderW.exe the file associations will never happen.
| |
| [Append to This Answer] | |
| 2001-May-03 6:16pm | |
|
|
My project pane isn't displaying complete package names, and won't let me browse packages I know exist in my source tree. |
| here is a patch that corrects the problem for all flavors of JBuilder 4:
http://codecentral.borland.com/codecentral/ccweb.exe/listing?id=15451 2001-May-03 6:28pm gyles19@visi.com | |
| [Append to This Answer] | |
| 2001-May-03 6:28pm | |
|
|
Enterprise's JSP Syntax highlighting is broken. |
!-- is not handled as a block comment in HTML part // is not handled as a comment after in <% /* is not handled as a block comment in <% <%-- is handled OK This is a known issue and is said to be fixed in the next release, according
to Vlad of Borland.
| |
| [Append to This Answer] | |
| 2001-May-03 7:00pm | |
|
|
I try to launch JBuilder 4 but I get the following exception: Exception occurred during event dispatching:java.lang.StringIndexOutOfBoundsException: String index out of range: 55 at java.lang.String.charAt(String.java:507) at com.borland.primetime.util.Strings$StringEncoding.b(Unknown Source) ... |
| Howard Stevens writes:
I may have a solution for this finally! We are using CVS for our project and the project jpx file is a file that resides in the repository. I seem to have problems when the jpx changes and merges with my local copy. I haven't exactly identified what it is in the file that causes the problem, but I do have a workaround that has worked for me the last two times this happened:
1) Open your project (if it opens to a JSP, edit your jpx.local file to remove references to the JSP's).
2) edit the project properties - change something minor (I use 'Deepest package exposed' in the General tab. Click OK.
3) save your project. Once you have JSP's opening again, you can change the project properties back if you want.
That seems to fix it for me.
| |
| [Append to This Answer] | |
| 2001-May-14 1:11pm | |
|
|
CVS doesn't function on Windows 95/98. |
| Gillmer J. Derge writes:
I have submitted a fix to CodeCentral that corrects errors in JBuilder's support for CVS on Windows 9x. The patch is known to work on JBuilder 4, but it may also work and/or be necessary for JBuilder 5. I've included the tool's detailed description below. This update addresses a problem with the CVS version control feature in Borland JBuilder version 4.0 (Enterprise) on Windows 9x operating systems. On those operating systems JBuilder does not see the output of the CVS command, so none of the CVS features work. After installing this update JBuilder's CVS support should work properly. Note that as discussed in the JBuilder release notes, CVS must be configured to run without asking for a password. This issue is most significant with respect to use with ssh and the Ext repository access method.
See http://codecentral.borland.com/codecentral/ccweb.exe/listing?id=16243
for more information. | |
| I found a simple way to make CVS in JBuilder5 run on Windows98.
The only thing to do is rename the file "cvs95.exe" (in JB's bin dirctory) to "cvs.exe". Of couse, don't forget adding the path to PATH setting.
2002-Mar-13 6:37am harry@tainet.com.cn | |
| [Append to This Answer] | |
| 2002-Mar-13 6:37am | |
|
|
CVS Diff (in the source pane's history tab) handles unicode characters incorrectly. |
| John McGrath writes:
It's a known bug. It only affects the diff display and not the file contents. | |
| [Append to This Answer] | |
| 2001-Jun-25 3:06pm | |
|
|
JBuilder 4 Enterprise: Solaris: Error when starting EJBs in WebLogic, "java.lang.NoClassDefFoundError" |
| See this Borland FAQ:
http://community.borland.com/article/0,1410,27288,00.html
This is reported fixed in JBuilder 5 Enterprise.
| |
| [Append to This Answer] | |
| 2001-Jul-06 10:56am | |
|
|
Designer can lose changes made directly in the source code. |
| Walter Liebich writes:
We were losing from time to time our edits, because Designer did not update source code, here is the path to always reproduce the problem, based on standart Java/Swing Components and JBuilder 4 defaultsettings on a german Windows NT 4 SP6: (This most probably applies to other environments as well): To reproduce, do the following: 1) File | New Project (use all default values) click on generate "main" and then Button "Finish" (without Next). 2) File | New and there choose JFrame from wizards (use all standart settings). 3) edit this new File called Frame1 with designer. 4) drop down 5 times Swings JButton from componentpalette into frame (which has Border Layout as default Layoutmanager).
5) go into source of Frame1 one and add to bottom of main the following
2 lines: frame1.setSize(500,500); frame1.show(); 6) "run" Frame1 (Rightclick Jbuilders Treenode with Frame1 and choose "Run"). 7) Application starts and shows JDialog. Close Application window, and hit red rectangle Button to stop application running. 8) Go to designer of Frame1 and change constraint of one of the Buttons to be "Center" (preferably not the one which is already in the middle). You see Designerpanel updating at once correctly. 9) "run" Frame1 (Rightclick Jbuilders Treenode with Frame1 and choose "Run"). 10) Notice: Jbuilder somehow starts previous version. (Application and Designer Panel are not equal. ) 11) check Source code of Frame1 and see that designer did not write code. (Constraint of the Button you changed to be "Center" is not "Center" in Source Code and started Application, however it is Displayed on Desinger Panel corre cly "Center"). There is no way to make Desinger write your changes to the source code anymore.
Notice: there was no Error on JBuilders Console or Designers Tab....
If you edit Source Code now then Designer updates to old version.... | |
| Rich Wilkman writes:
Known problem that keeps creeping up. The crux in his steps is the "Run" which compiles the classes and sometimes shuts out the Designer (Greg has more info and has posted about it a couple times). The Designer keeps writing to the buffer but the buffer never seems to get committed.
At one time the "safe" pattern was to go to the source tab before
running or compiling. The JB folks have chased variants of this for a
while (I know I've logged and verified fixes for this in different
versions) but there's still "something out there".
| |
| [Append to This Answer] | |
| 2001-Sep-08 2:32pm |
| 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 |
|||||||||||||||||
|
|||||||||||||||||