Does this mean that 1.7.0 has better embedable support so we don't have to hack up the dist to make it work with JBoss? I didn't look at the new stuff, so I don't have a clue... but I am hoping that is what it means.
I am simply concered that with the current impl we don't really have much control over the maintenece... which I would like to have fixed. --jason Peter Fagerlund wrote: >on 04-04-2 03.13, Jason Dillon at [EMAIL PROTECTED] wrote: > >>Where are the patched sources for the JBoss HSQLDB? Does anyone know if >>the 1.7.x version is flexible enough to use it out of the box? If not, >>could whoever patched it in the first place try to get those changes >>commited... assuming they are not completly JBoss specific. >> > >They are at 1.7.0RC3 and are looking at implementing the patch We have been >using ... > > >>If the patch is JBoss specific, then we should start managing the >>sources internally (like we do with Jetty), so we can maintain the >>patched version effectivly. >> > >lets wait until they go 1.7.0 ... then We can upgrade ... depending on >1.7.0's choosen embedded support ... alt. We could manage the listener >components ourself and use the Database class directly from there ... the >way We traditionaly started hsql is to call the org.hsql.Server class that >is a listerner ... We could reuse Jetty's or web module's listener >components and so unify with a new hsqldb listener. And then perhaps also >refactor JNP to use the same listener components ? ... Today all 4 mentioned >have there own listener implementation. > >/peter_f > _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
