> Depends on the version of Jbuilder. I have found Jbuilder 1.xx -- Pro to > 'bloat' > the code. However, using the Sun JDK instead I get much better performing > code. I > also reduce the number of potential problems by removing Jbuilder from the > 'mix'. > Look at your imports. Try to only import what you need. Instead of import > java.io.* use import java.io.DataStream.*. I realize the IDE is > wonderful, but, > we aren't getting to the 'write once, run anywhere' goal with Jbuilder. Changing the import statement as you suggest will have no effect on the compiled class file. The "import" is simply a compiler directive that limits the set of classes it looks for when attempting to resolve names. A more fully qualified import will help the compiler generate your code a bit faster, but the resulting class will not be any smaller or faster. Marshall Dunbar DPS, Inc. Co-Author of the Redbook _Accessing the AS/400 System with Java_ +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to JAVA400-L@midrange.com. | To subscribe to this list send email to JAVA400-L-SUB@midrange.com. | To unsubscribe from this list send email to JAVA400-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: firstname.lastname@example.org +---
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.