Try the SQL plugin. There's a place to specify where to find JDBC drivers. The jars defined there will be included in jEdit's classpath once jEdit has started up.

If you don't want to install the SQL plugin. It'll help to know how jEdit loads it's plugins.

Under your installation directory and your settings directory (usually found in your home directory ~/.jedit) you'll see a "jars" directory. Any jars under either of these directories will automatically get included in jEdit's classpath when jEdit starts up.

It's probably better if you use either of these methods as a new installation of jEdit might overwrite your shortcut and thus the classpath changes you made there in.

Hope that helps.

Also, if you just want to run SQL statements against a database, the SQL plugin will let you do that as well.

Learn from the past. Live in the present. Plan for the future.
11101000

Thank you for your answer,

I have tried both SQL and DBTerminal plugins and got them to work by putting oracle jdbc jars in ~/.jedit/jars directory and I do know that jars placed in .jedit/jars get loaded in classpath as far as plugins are concerned.

However macros do not seem to see the jars in classpath when you only putting them in ~/.jedit/jars directory. And putting them in jdbc path using SQL plugin does not help also (it only helps for SQL plugin itself but not macros).

You can try for yourself running the classpath macro included in my first post. Enable activity log to see the output that print gives.

NB: I would be interested to know if it acts differently for you.

The way I run it to get it works for macros I found by looking in jedit.jar MANIFEST file so I can always look there when new jEdit version arrives and make proper replacements. But still I would like to know if there is another way.

Ah. Right. I missed that you were using the System ClassLoader (sorry). Try using some reflection and the JARClassLoader.

[code]

import org.gjt.sp.jedit.JARClassLoader;
import java.sql.*;

JARClassLoader jarClassLoader = new JARClassLoader();
Class driverClass = jarClassLoader.loadClass("oracle.jdbc.OracleDriver");
if(driverClass != null) {
	Driver driver = driverClass.newInstance();
	if(driver != null) {
		DriverManager.registerDriver(driver);
	}
}

Connection conn = DriverManager.getConnection("jdbc:oracle:thin:@my.oracle.server:1521:MYBASE", "user", "pass");

[/code]

This worked for me, but I'm using SQL plugin to manage the JDBC jars. The SQL plugin injects your jdbc jars into jEdit's plugin JARClassLoader.

Learn from the past. Live in the present. Plan for the future.
11101000

I have to try this out. Looks promising.

Thanks

Tried it out (both commented and outcommented versions), and included some additional debug output. Also SQL plugin under options JDBC I have full path to my oracle.jar (Classpath elements). But it always gives me "Test output and the driver that I tried to load" and none of the debug output I included: ("Can not register driver" or "Can not load driver") and also displays the error I got before. When I include oracle.jar from my classpath (by starting jedit with java command line) everything works fine.

import org.gjt.sp.jedit.JARClassLoader;
import java.sql.*;

JARClassLoader jarClassLoader = new JARClassLoader();
Class driverClass = jarClassLoader.loadClass("oracle.jdbc.driver.OracleDriver");
//jarClassLoader.loadClass("oracle.jdbc.OracleDriver");

print("Test output: " + driverClass);

if(driverClass != null) {
    Driver driver = driverClass.newInstance();
    if(driver != null) {
       //DriverManager.registerDriver(driver); 
       DriverManager.registerDriver(new oracle.jdbc.driver.OracleDriver());
    } else {
        print("Can not register driver");
    }
} else {
    print("Can not load driver");
}
//exit();
DriverManager.registerDriver (new oracle.jdbc.driver.OracleDriver());        

Connection conn = DriverManager.getConnection("jdbc:oracle:thin:@my.host.name:1521:MYDB", "myuser", "mypass");

Statement stmt = conn.createStatement();
ResultSet rset = stmt.executeQuery("select BANNER from SYS.V_$VERSION");
        
while (rset.next())
     print (rset.getString(1));   // Print col 1
stmt.close();

Phade,
I think you should use a DataSource instead. In a lot of ways, it's preferred over the Driver and DriverManager anyway. You would instantiate it as you would the Driver, and I think it's easier to use.

Here's an example using MySQL (since I don't want to install Oracle Express on my Mac).

[code]

import org.gjt.sp.jedit.JARClassLoader;
import java.sql.*;
import javax.sql.*;

JARClassLoader jarClassLoader = new JARClassLoader();
String dataSourceClassName = "com.mysql.jdbc.jdbc2.optional.MysqlDataSource";
String username = "myUsername";
String password = "myPassword";
String databaseUrl = "jdbc:mysql://localhost:3306/mysql";
Class dataSourceClass = jarClassLoader.loadClass(dataSourceClassName);

Macros.message(view, "DataSource class: " + dataSourceClass);

if(dataSourceClass != null) {
   DataSource dataSource = dataSourceClass.newInstance();
   if(dataSource != null) {
      Macros.message(view, "DataSource is not null, using it.");
      dataSource.setUrl(databaseUrl);
      Connection conn = null;
      try {
         conn = dataSource.getConnection(username, password);
      } catch(Exception e) {
         e.printStackTrace();
      }
      if(conn != null) {
         Macros.message(view, "Connection established - trying a query.");
         PreparedStatement statement = null;
         try {
            statement = conn.prepareStatement("SHOW DATABASES");
         } catch(Exception e) {
            e.printStackTrace();
         }
         if(statement != null) {
            Macros.message(view, "Statement created - executing.");
            ResultSet resultSet = null;
            try {
               resultSet = statement.executeQuery();
            } catch(Exception e) {
               e.printStackTrace();
            }
            if(resultSet != null) {
               Macros.message(view, "Statement executed successfully");
               resultSet.close();
            }
            statement.close();
         } else {
            Macros.message(view, "Statement could not be created, check Activity Log for errors.");
         }
         conn.close();
      } else {
         Macros.message(view, "Connection could not be made, check Activity Log for errors.");
      }
   } else {
      Macros.message(view, "DataSource was null.");
   }
}

[/code]

There's a lot of debug statements in there, which you can remove.

Hope that works for you.

Learn from the past. Live in the present. Plan for the future.
11101000