Matthew Aidekman

Sorry for this uninformed/naive question. I'm attempting to get up and running with java and install HSQLDB. I'm also attempting to UNDERSTAND THIS CRAZY FILE FOLDER SYSTEM.

***I made it through the HTML tutorial "configuring" section

/Library/Application Support/Cycling '74/java/lib/loadbang-sql/

***I've added the following lines to the max.java.config.txt file:

max.dynamic.class.dir "/Library/Application Support/Cycling '74/lib/classes/loadbang-sql/" //is that right?

max.dynamic.jar.dir "/Library/Application Support/Cycling '74/java/lib/loadbang-sql/" //is that right?

***when opening db-test.Noddy.mxt I get this in the max window and a greyed MXJ box

? error:     at org.hsqldb.Database.reopen(Unknown Source)

? error:     at org.hsqldb.Database.open(Unknown Source)

? error:     at org.hsqldb.DatabaseManager.getDatabase(Unknown Source)

? error:     at org.hsqldb.DatabaseManager.newSession(Unknown Source)

? error:     at org.hsqldb.jdbc.jdbcConnection.(Unknown Source)

? error:     at org.hsqldb.jdbcDriver.getConnection(Unknown Source)

? error:     at org.hsqldb.jdbcDriver.connect(Unknown Source)

? error:     at java.sql.DriverManager.getConnection(DriverManager.java:525)

? error:     at java.sql.DriverManager.getConnection(DriverManager.java:171)

? error:     at net.loadbang.sql.Database.open(Database.java:95)

? error:     at net.loadbang.sql.mxj.MXJ_SQL.setDatabase(MXJ_SQL.java:57)

? error:     at net.loadbang.sql.mxj.NoddySQL.(NoddySQL.java:40)

? error: (mxj) unable to construct instance of net.loadbang.sql.mxj.NoddySQL

Sorry for this uninformed/naive question.  I'm attempting to get up and running with java and install HSQLDB.  I'm also attempting to UNDERSTAND THIS CRAZY FILE FOLDER SYSTEM.
A: have I done the right thing
B: what else do I need to do?

***I created this folder:
/Library/Application Support/Cycling '74/java/lib/loadbang-sql/

***and put these files into it :
NoddySQL (directory)
log4j-1.2.12.jar
hsqldb-1.8.0.jar
net.loadbang-SQL-1.1.jar
net.loadbang-lib-1.0.jar

***I've added the following lines to the max.java.config.txt file:
max.dynamic.class.dir "/Library/Application Support/Cycling '74/lib/classes/loadbang-sql/"      //is that right?
max.dynamic.jar.dir "/Library/Application Support/Cycling '74/java/lib/loadbang-sql/"           //is that right?
max.java.jvm.version 1.5

? error: java.lang.NoClassDefFoundError
? error: 	at org.hsqldb.Database.reopen(Unknown Source)
? error: 	at org.hsqldb.Database.open(Unknown Source)
? error: 	at org.hsqldb.DatabaseManager.getDatabase(Unknown Source)
? error: 	at org.hsqldb.DatabaseManager.newSession(Unknown Source)
? error: 	at org.hsqldb.jdbc.jdbcConnection.(Unknown Source)
? error: 	at org.hsqldb.jdbcDriver.getConnection(Unknown Source)
? error: 	at org.hsqldb.jdbcDriver.connect(Unknown Source)
? error: 	at java.sql.DriverManager.getConnection(DriverManager.java:525)
? error: 	at java.sql.DriverManager.getConnection(DriverManager.java:171)
? error: 	at net.loadbang.sql.Database.open(Database.java:95)
? error: 	at net.loadbang.sql.mxj.MXJ_SQL.setDatabase(MXJ_SQL.java:57)
? error: 	at net.loadbang.sql.mxj.NoddySQL.(NoddySQL.java:40)
? error: (mxj) unable to construct instance of net.loadbang.sql.mxj.NoddySQL

newbie-installing-hsqldb

On 24 Jun 2006, at 05:08, Matthew Aidekman wrote:

> I'm also attempting to UNDERSTAND THIS CRAZY FILE FOLDER SYSTEM.

It's pretty simple (although the Java searching world and the Max/MSP 

searching world are completely different, which is unfortunate). 

(i) put all the JAR files in Cycling '74/java/lib (alongside max.jar, 

(ii) create a place-holder file (something.PLACE_HOLDER) somewhere in 

> /Library/Application Support/Cycling '74/java/lib/loadbang-sql/

Ah: no. The Java classpath will have C74/java/lib in it, but not any 

> ***I've added the following lines to the max.java.config.txt file:

If you use Cycling '74/java/lib you shouldn't need to make any 

changes to max.java.config.txt (except possibly to choose Java 1.5).

> ? error: java.lang.NoClassDefFoundError

> ? error: (mxj) unable to construct instance of 

Yep: that's because the JAR file isn't being found.

nick rothwell -- composition, systems, performance -- 

It's pretty simple (although the Java searching world and the Max/MSP  
searching world are completely different, which is unfortunate).  
Instructions:

(i) put all the JAR files in Cycling '74/java/lib (alongside max.jar,  
jode-XXXX.jar et. al.)
(ii) create a place-holder file (something.PLACE_HOLDER) somewhere in  
Max's search path
(iii) that's it.

> ***I created this folder:
> /Library/Application Support/Cycling '74/java/lib/loadbang-sql/

Ah: no. The Java classpath will have C74/java/lib in it, but not any  
sub-folders.

If you use Cycling '74/java/lib you shouldn't need to make any  
changes to max.java.config.txt (except possibly to choose Java 1.5).

> ? error: (mxj) unable to construct instance of  
> net.loadbang.sql.mxj.NoddySQL

   nick rothwell -- composition, systems, performance -- http:// 
www.cassiel.com


If you use XCode or compile via the Terminal, what follows may help.

Since I develop other Java applications, I put common .jar files inot

/Library/Java/Extensions or /Library/Java/, and put some useful

environment variables into my ~/.bash_profile file.

You can also drag .jars from just about anywhere right into an XCode project.

https://cycling74.com/forums/index.php?t=msg&th=20363&start=0&rid=0&S=3d8a80c5bccddf97a1caf46820fa8a78

I have found that a pretty reasonable development cycle can work like

Create an XCode project, adding the mxj.jar and jitter.jar files as necessary.

Create one mxj class and any necessary utility and supporting classes.

Compile/debug until you get the code right.

Save the .jar file (which has utility and supporting classes) to a

directory where you also put the .java file for the mxj class you

Modify your .bash_profile file in your home directory by adding:

export MAX_LIB="/Library/Application Support/Cycling '74/java/lib"

export MAXCLASSPATH=$MAX_LIB/max.jar:$MAX_LIB/jode-1.1.2-pre-embedd

Open a Terminal window and navigate to your development directory.

javac -cp ".:$MAXCLASSPATH:IgnoGameTool.jar" buf2jmTest.java

Note the quotes around the classpath string. These are necessary to

handle the spaces in the directory paths to the MaxMSP .jar files.

Once I have the utility and support classes compiled, this gives me a

very speedy turnaround while I develop the mxj class.

> Sorry for this uninformed/naive question. I'm attempting to get up and running with java and install HSQLDB. I'm also attempting to UNDERSTAND THIS CRAZY FILE FOLDER SYSTEM.

> ***I made it through the HTML tutorial "configuring" section

> max.dynamic.class.dir "/Library/Application Support/Cycling '74/lib/classes/loadbang-sql/" //is that right?

> max.dynamic.jar.dir "/Library/Application Support/Cycling '74/java/lib/loadbang-sql/" //is that right?

> ***when opening db-test.Noddy.mxt I get this in the max window and a greyed MXJ box

> ? error: at org.hsqldb.Database.reopen(Unknown Source)

> ? error: at org.hsqldb.Database.open(Unknown Source)

> ? error: at org.hsqldb.DatabaseManager.getDatabase(Unknown Source)

> ? error: at org.hsqldb.DatabaseManager.newSession(Unknown Source)

> ? error: at org.hsqldb.jdbc.jdbcConnection.(Unknown Source)

> ? error: at org.hsqldb.jdbcDriver.getConnection(Unknown Source)

> ? error: at org.hsqldb.jdbcDriver.connect(Unknown Source)

> ? error: at java.sql.DriverManager.getConnection(DriverManager.java:525)

> ? error: at java.sql.DriverManager.getConnection(DriverManager.java:171)

> ? error: at net.loadbang.sql.Database.open(Database.java:95)

> ? error: at net.loadbang.sql.mxj.MXJ_SQL.setDatabase(MXJ_SQL.java:57)

> ? error: at net.loadbang.sql.mxj.NoddySQL.(NoddySQL.java:40)

> ? error: (mxj) unable to construct instance of net.loadbang.sql.mxj.NoddySQL

----- |(*,+,#,=)(#,=,*,+)(=,#,+,*)(+,*,=,#)| -----

If you use XCode or compile via the Terminal, what follows may help.
Since I develop other Java applications, I put common .jar files inot
/Library/Java/Extensions or /Library/Java/, and put some useful
environment variables into my ~/.bash_profile file.

I copy from: https://cycling74.com/forums/index.php?t=msg&th=20363&start=0&rid=0&S=3d8a80c5bccddf97a1caf46820fa8a78

I have found that a pretty reasonable development cycle can work like
so using XCode.

Create an XCode project, adding the mxj.jar and jitter.jar files as necessary.
Create one mxj class and any necessary utility and supporting classes.
Compile/debug until you get the code right.
Compile a .jar file.
Save the .jar file (which has utility and supporting classes) to a
directory where you also put the .java file for the mxj class you
created.

export MAX_LIB="/Library/Application Support/Cycling '74/java/lib"
export MAXCLASSPATH=$MAX_LIB/max.jar:$MAX_LIB/jode-1.1.2-pre-embedd
ed.jar:$MAX_LIB/jitter.jar

Note the quotes around the classpath string. These are necessary to
handle the spaces in the directory paths to the MaxMSP .jar files.

Once I have the utility and support classes compiled, this gives me a
very speedy turnaround while I develop the mxj class.

On 6/23/06, Matthew Aidekman  wrote:
>
> Sorry for this uninformed/naive question.  I'm attempting to get up and running with java and install HSQLDB.  I'm also attempting to UNDERSTAND THIS CRAZY FILE FOLDER SYSTEM.
> A: have I done the right thing
> B: what else do I need to do?
>
>
> ***I made it through the HTML tutorial "configuring" section
>
> ***I created this folder:
> /Library/Application Support/Cycling '74/java/lib/loadbang-sql/
>
> ***and put these files into it :
> NoddySQL (directory)
> log4j-1.2.12.jar
> hsqldb-1.8.0.jar
> net.loadbang-SQL-1.1.jar
> net.loadbang-lib-1.0.jar
>
> ***I've added the following lines to the max.java.config.txt file:
> max.dynamic.class.dir "/Library/Application Support/Cycling '74/lib/classes/loadbang-sql/"      //is that right?
> max.dynamic.jar.dir "/Library/Application Support/Cycling '74/java/lib/loadbang-sql/"           //is that right?
> max.java.jvm.version 1.5
>
>
> ***when opening db-test.Noddy.mxt I get this in the max window and a greyed MXJ box
>
> ? error: java.lang.NoClassDefFoundError
> ? error:        at org.hsqldb.Database.reopen(Unknown Source)
> ? error:        at org.hsqldb.Database.open(Unknown Source)
> ? error:        at org.hsqldb.DatabaseManager.getDatabase(Unknown Source)
> ? error:        at org.hsqldb.DatabaseManager.newSession(Unknown Source)
> ? error:        at org.hsqldb.jdbc.jdbcConnection.(Unknown Source)
> ? error:        at org.hsqldb.jdbcDriver.getConnection(Unknown Source)
> ? error:        at org.hsqldb.jdbcDriver.connect(Unknown Source)
> ? error:        at java.sql.DriverManager.getConnection(DriverManager.java:525)
> ? error:        at java.sql.DriverManager.getConnection(DriverManager.java:171)
> ? error:        at net.loadbang.sql.Database.open(Database.java:95)
> ? error:        at net.loadbang.sql.mxj.MXJ_SQL.setDatabase(MXJ_SQL.java:57)
> ? error:        at net.loadbang.sql.mxj.NoddySQL.(NoddySQL.java:40)
> ? error: (mxj) unable to construct instance of net.loadbang.sql.mxj.NoddySQL
>
>
>
> sorry for the long message
> -matt
>

-- 
-----   |(*,+,#,=)(#,=,*,+)(=,#,+,*)(+,*,=,#)|   -----


Ha, one more important detail--put the .jar file you have created and

/Library/Application Support/Cycling '74/java/classes/

maybe even into your own directory there.

While Max can find the files elsewhere in its search path, this seems

like the optimal place to keep track of finished work and avoid having

other stale files pulled out of other directories.

> Oho, an opportunity to quote myself 8^}

> If you use XCode or compile via the Terminal, what follows may help.

> Since I develop other Java applications, I put common .jar files inot

> /Library/Java/Extensions or /Library/Java/, and put some useful

> environment variables into my ~/.bash_profile file.

> You can also drag .jars from just about anywhere right into an XCode project.

> I have found that a pretty reasonable development cycle can work like

> Create an XCode project, adding the mxj.jar and jitter.jar files as necessary.

> Create one mxj class and any necessary utility and supporting classes.

> Compile/debug until you get the code right.

> Save the .jar file (which has utility and supporting classes) to a

> directory where you also put the .java file for the mxj class you

> The rest of the cycle uses the Terminal.

> Modify your .bash_profile file in your home directory by adding:

> export MAX_LIB="/Library/Application Support/Cycling '74/java/lib"

> export MAXCLASSPATH=$MAX_LIB/max.jar:$MAX_LIB/jode-1.1.2-pre-embedd

> Open a Terminal window and navigate to your development directory.

> javac -cp ".:$MAXCLASSPATH:IgnoGameTool.jar" buf2jmTest.java

> Note the quotes around the classpath string. These are necessary to

> handle the spaces in the directory paths to the MaxMSP .jar files.

> Once I have the utility and support classes compiled, this gives me a

> very speedy turnaround while I develop the mxj class.

Ha, one more important detail--put the .jar file you have created and
the .class file into

While Max can find the files elsewhere in its search path, this seems
like the optimal place to keep track of finished work and avoid having
other stale files pulled out of other directories.

On 6/27/06, Paul Hertz  wrote:
> Oho, an opportunity to quote myself 8^}
>
> If you use XCode or compile via the Terminal, what follows may help.
> Since I develop other Java applications, I put common .jar files inot
> /Library/Java/Extensions or /Library/Java/, and put some useful
> environment variables into my ~/.bash_profile file.
>
> You can also drag .jars from just about anywhere right into an XCode project.
>
> I copy from: https://cycling74.com/forums/index.php?t=msg&th=20363&start=0&rid=0&S=3d8a80c5bccddf97a1caf46820fa8a78
>
> which says:
>
> I have found that a pretty reasonable development cycle can work like
> so using XCode.
>
> Create an XCode project, adding the mxj.jar and jitter.jar files as necessary.
> Create one mxj class and any necessary utility and supporting classes.
> Compile/debug until you get the code right.
> Compile a .jar file.
> Save the .jar file (which has utility and supporting classes) to a
> directory where you also put the .java file for the mxj class you
> created.
>
> The rest of the cycle uses the Terminal.
>
> Modify your .bash_profile file in your home directory by adding:
>
> export MAX_LIB="/Library/Application Support/Cycling '74/java/lib"
> export MAXCLASSPATH=$MAX_LIB/max.jar:$MAX_LIB/jode-1.1.2-pre-embedd
> ed.jar:$MAX_LIB/jitter.jar
>
> Open a Terminal window and navigate to your development directory.
>
> compile with something like this:
>
> javac -cp ".:$MAXCLASSPATH:IgnoGameTool.jar" buf2jmTest.java
>
> Note the quotes around the classpath string. These are necessary to
> handle the spaces in the directory paths to the MaxMSP .jar files.
>
> Once I have the utility and support classes compiled, this gives me a
> very speedy turnaround while I develop the mxj class.
>
> Hope this is useful.
>
> -- Paul
>
>
> On 6/23/06, Matthew Aidekman  wrote:
> >
> > Sorry for this uninformed/naive question.  I'm attempting to get up and running with java and install HSQLDB.  I'm also attempting to UNDERSTAND THIS CRAZY FILE FOLDER SYSTEM.
> > A: have I done the right thing
> > B: what else do I need to do?
> >
> >
> > ***I made it through the HTML tutorial "configuring" section
> >
> > ***I created this folder:
> > /Library/Application Support/Cycling '74/java/lib/loadbang-sql/
> >
> > ***and put these files into it :
> > NoddySQL (directory)
> > log4j-1.2.12.jar
> > hsqldb-1.8.0.jar
> > net.loadbang-SQL-1.1.jar
> > net.loadbang-lib-1.0.jar
> >
> > ***I've added the following lines to the max.java.config.txt file:
> > max.dynamic.class.dir "/Library/Application Support/Cycling '74/lib/classes/loadbang-sql/"      //is that right?
> > max.dynamic.jar.dir "/Library/Application Support/Cycling '74/java/lib/loadbang-sql/"           //is that right?
> > max.java.jvm.version 1.5
> >
> >
> > ***when opening db-test.Noddy.mxt I get this in the max window and a greyed MXJ box
> >
> > ? error: java.lang.NoClassDefFoundError
> > ? error:        at org.hsqldb.Database.reopen(Unknown Source)
> > ? error:        at org.hsqldb.Database.open(Unknown Source)
> > ? error:        at org.hsqldb.DatabaseManager.getDatabase(Unknown Source)
> > ? error:        at org.hsqldb.DatabaseManager.newSession(Unknown Source)
> > ? error:        at org.hsqldb.jdbc.jdbcConnection.(Unknown Source)
> > ? error:        at org.hsqldb.jdbcDriver.getConnection(Unknown Source)
> > ? error:        at org.hsqldb.jdbcDriver.connect(Unknown Source)
> > ? error:        at java.sql.DriverManager.getConnection(DriverManager.java:525)
> > ? error:        at java.sql.DriverManager.getConnection(DriverManager.java:171)
> > ? error:        at net.loadbang.sql.Database.open(Database.java:95)
> > ? error:        at net.loadbang.sql.mxj.MXJ_SQL.setDatabase(MXJ_SQL.java:57)
> > ? error:        at net.loadbang.sql.mxj.NoddySQL.(NoddySQL.java:40)
> > ? error: (mxj) unable to construct instance of net.loadbang.sql.mxj.NoddySQL
> >
> >
> >
> > sorry for the long message
> > -matt
> >
>
>
> --
> -----   |(*,+,#,=)(#,=,*,+)(=,#,+,*)(+,*,=,#)|   -----
>

On 27 Jun 2006, at 06:32, Paul Hertz wrote:

> Ha, one more important detail--put the .jar file you have created and

> /Library/Application Support/Cycling '74/java/classes/

The JAR files should go into java/lib (although the documentation 

claims java/classes, so I suspect it's a different choice of 

classloader: system vs. dynamic). Class files must go into a 

directory structure which reflects the package heirarchy.

> Ha, one more important detail--put the .jar file you have created and
> the .class file into
>
> /Library/Application Support/Cycling '74/java/classes/

The JAR files should go into java/lib (although the documentation  
claims java/classes, so I suspect it's a different choice of  
classloader: system vs. dynamic). Class files must go into a  
directory structure which reflects the package heirarchy.

For mxj objects there seems to be little point to building a package

structure--they are generally not multi-class structures but fairly

simple dealies with few dependencies--at least the way I write them

The .jar files contain the package structure, which you can peek at with

If you built your classes in a single directory and with no "package"

directive, the .jar file will show a flat hierarchy. Pre-compiled jar

files--ie.e, libraries from third parties--have their package

structure all set. In that sense, at least, it doesn't matter where

you put them as long as they are accessible in the runtime classpath.

If you want a visible file hierararchy, you can extract the classes

but generally there's no need to do that.

In the development pattern I was suggesting, you put your subsidiary

classes into a jar file and build one more class, a subclass of

MaxObject, that will access them. You keep them together for

convenience. As long as mxj can find your class, it will find the

accompanying jar file. If you want to build a set of utility classes

that a lot of MaxObject classes will access, then I suppose that

java/lib is a logical place to put them--but there is no force of

So, sure, class files must go in a directory structure that reflects

their package hierarchy, but that is at compile tile. At run time

things are different, as long as your are using a .jar file.

> On 27 Jun 2006, at 06:32, Paul Hertz wrote:

> > Ha, one more important detail--put the .jar file you have created and

> > /Library/Application Support/Cycling '74/java/classes/

> The JAR files should go into java/lib (although the documentation

> claims java/classes, so I suspect it's a different choice of

> classloader: system vs. dynamic). Class files must go into a

> directory structure which reflects the package heirarchy.

> nick rothwell -- composition, systems, performance -- 

For mxj objects there seems to be little point to building a package
structure--they are generally not multi-class structures but fairly
simple dealies with few dependencies--at least the way I write them
8-).

If you built your classes in a single directory and with no "package"
directive, the .jar file will show a flat hierarchy. Pre-compiled jar
files--ie.e, libraries from third parties--have their package
structure all set. In that sense, at least, it doesn't matter where
you put them as long as they are accessible in the runtime classpath.
If you want a visible file hierararchy, you can extract the classes
with

 but generally there's no need to do that.

In the development pattern I was suggesting, you put your subsidiary
classes into a jar file and build one more class, a subclass of
MaxObject, that will access them. You keep them together for
convenience. As long as mxj can find your class, it will find the
accompanying jar file. If you want to build a set of utility classes
that a lot of MaxObject classes will access, then I suppose that
java/lib is a logical place to put them--but there is no force of
necessity in that.

So, sure, class files must go in a directory structure that reflects
their package hierarchy, but that is at compile tile. At run time
things are different, as long as your are using a .jar file.

On 6/27/06, Nick Rothwell  wrote:
>
> On 27 Jun 2006, at 06:32, Paul Hertz wrote:
>
> > Ha, one more important detail--put the .jar file you have created and
> > the .class file into
> >
> > /Library/Application Support/Cycling '74/java/classes/
>
> The JAR files should go into java/lib (although the documentation
> claims java/classes, so I suspect it's a different choice of
> classloader: system vs. dynamic). Class files must go into a
> directory structure which reflects the package heirarchy.
>
>         -- N.
>
>
>    nick rothwell -- composition, systems, performance -- http://
> www.cassiel.com
>
>
>
>

> For mxj objects there seems to be little point to building a package

> structure--they are generally not multi-class structures but fairly

> simple dealies with few dependencies--at least the way I write them

A couple of data points: my Triptychos installation piece is around 

20 class files, not counting libraries; the Audiobounce gallery piece 

is about 30. These are relatively small projects from a programming 

point of view; I have older Max/Java projects (using OSC, predating 

> If you built your classes in a single directory and with no "package"

> directive, the .jar file will show a flat hierarchy. Pre-compiled jar

> files--ie.e, libraries from third parties--have their package

That's a non-sequitur. All JAR files are heirarchical: they are just 

ZIP archives of directories of class files. You can choose to adopt a 

completely flat heirarchy if you choose, or invent a package 

structure; this has nothing to do with whether you're packing the 

classes into JAR files or not (I don't know what you mean by "pre- 

compiled"), and nothing to do with whether they are third-party 

I would expect libraries to use a sensible package convention - by 

definition, they are going to be integrated into other applications, 

so they should have distinctive and clean namespaces. Conversely, 

simple MXJ objects will probably have simple (or no) package 

structure, although I think making package-less MXJ's is unwise: they 

> In the development pattern I was suggesting, you put your subsidiary

> classes into a jar file and build one more class, a subclass of

> MaxObject, that will access them. You keep them together for

I don't see what you gain by separating subsidiary classes from the 

MXJ class, unless the former are generic libraries or utilities.

The way I work in Eclipse is purely with class file directories 

(third-party libraries apart), and multiple Eclipse projects which 

Newbie installing HSQLDB