Coming Soon: JBuilder 3.5
Using Borland's JBuilder with WebLogic
Here are a few tips for using Borland's JBuilder 2.0 IDE and runtime environment with WebLogic software. You will need to do some minor configuring of your system to use JBuilder. Here is how to set up the JBuilder IDE.
For example, here is the URL for connecting to an Oracle database "emp" on port 7001 of the WebLogic Server host "bigbox.com":
Connection URL=jdbc:weblogic:t3:oracle:emp? weblogic.t3.serverURL=t3://bigbox.com:7001 Driver Class weblogic.jdbc.t3.Driver
For a two-tier connection (from a Java application to a database):
Connection URL=jdbc:weblogic:oracle:nameOfDB Driver Class weblogic.jdbc.oci.Driver
You can test the connections to the database using the connection dialog box. If you have everything set up correctly, you should get a success message.
Load a query data set and make a select statement to verify connections. Then drop a grid onto JBuilder's Design tool and tie it to your query data set. While in the Design mode you should see your query data populated in JBuilder's grid box.
Some of our customers have reported problems using JBuilder to compile tutorials and other sample code that are part of the WebLogic 3.0 release, related to a feature in the JBuilder IDE called "Smart Dependencies Checking." This utility checks the dependencies for every class that it finds and tests all of the dependencies in all of the WebLogic classes, even though these classes are not required to compile sample code. Importing even a single WebLogic package that refers to third-party classes, such as the Visibroker CORBA classes, will cause this problem.
There is no way to to disable the "Smart Dependencies Checking" feature when using the JBuilder IDE, but there are two options for working around it:
If you do not have a .zip file utility available, create a .jar file with the manifest disabled, which will function the same as a .zip file. Here is an example of the syntax:
$ jar cvfM jarFile.jar *.class
where jarFile.jar is the name of the .jar file to be created and *.class is a file description of the classes needed to compile your application. The "M" creates a .jar file with the manifest disabled.
Once the .zip or .jar archive is created, follow these steps to add it to your JBuilder environment as described above.
For more information useful for working with JBuilder, see Using URLs to set properties for a JDBC Connection
and Testing connections.
Copyright © 2000 BEA Systems, Inc. All rights reserved.