Re: [GUMP] Next JAXME issues
On 9/2/05, Stefan Bodewig <[EMAIL PROTECTED]> wrote: > java.sql.SQLException: Wrong database file version That's strange. According to http://www.devdaily.com/java/jwarehouse/hsqldb/src/org/hsqldb/Trace.shtml this is the hsqldb error code WRONG_DATABASE_FILE_VERSION. And, according to http://www.devdaily.com/java/jwarehouse/hsqldb/src/org/hsqldb/HsqlDatabaseProperties.shtml that error code is caused by a database version, which is newer than the driver. I have no idea, how a second version of hsqldb may come into play. My guess is, that sometimes the version from the JaxMe repository is used and a gump version at other times. Do you think that's possible? Regards, Jochen -- Having experienced 7 years of labour/green government, I now know the reason, why a conservative government is good for the economy: The economy's unable to imagine anything else ... - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [GUMP] Next JAXME issues
On Thu, 01 Sep 2005, Stefan Bodewig <[EMAIL PROTECTED]> wrote: > I've modified the descriptor to allow Ant whatever classpath > settings are used in the build file. If we are just missing on the > CLASSPATH the we will see the next build succeed. Well, it helped. the next issue really seems to be something different. Stefan Testsuite: org.apache.ws.jaxme.pm.junit.SessionTest Tests run: 9, Failures: 0, Errors: 7, Time elapsed: 0.667 sec Testcase: testCreateFactory took 0.431 sec Testcase: testCreateManager took 0.108 sec Caused an ERROR Wrong database file version java.sql.SQLException: Wrong database file version at org.hsqldb.Trace.getError(Unknown Source) at org.hsqldb.Trace.check(Unknown Source) at org.hsqldb.Trace.check(Unknown Source) at org.hsqldb.Log.open(Unknown Source) at org.hsqldb.Database$Logger.openLog(Unknown Source) at org.hsqldb.Database.open(Unknown Source) at org.hsqldb.Database.(Unknown Source) at org.hsqldb.jdbcConnection.openStandalone(Unknown Source) at org.hsqldb.jdbcConnection.(Unknown Source) at org.hsqldb.jdbcDriver.connect(Unknown Source) at java.sql.DriverManager.getConnection(DriverManager.java:512) at java.sql.DriverManager.getConnection(DriverManager.java:171) at org.apache.ws.jaxme.pm.jdbc.PMJdbcImpl.getConnection(PMJdbcImpl.java:92) at org.apache.ws.jaxme.pm.junit.SessionTest.testCreateManager(SessionTest.java:81) Testcase: testClear took 0.014 sec Caused an ERROR Failed to execute query SELECT ID, IPADDRESS, LOGINTIME, LASTACTION, EXPIRETIME, COOKIE, RANDOMSEED, PRECEDENCE FROM HTTPSESSION: Wrong database file version org.apache.ws.jaxme.PMException: Failed to execute query SELECT ID, IPADDRESS, LOGINTIME, LASTACTION, EXPIRETIME, COOKIE, RANDOMSEED, PRECEDENCE FROM HTTPSESSION: Wrong database file version at org.apache.ws.jaxme.test.pm.session.impl.SessionTypePM.select(SessionTypePM.java:229) at org.apache.ws.jaxme.pm.impl.PMImpl.select(PMImpl.java:83) at org.apache.ws.jaxme.pm.impl.PMImpl.select(PMImpl.java:59) at org.apache.ws.jaxme.pm.junit.SessionTest.testClear(SessionTest.java:91) Caused by: java.sql.SQLException: Wrong database file version at org.hsqldb.Trace.getError(Unknown Source) at org.hsqldb.Trace.check(Unknown Source) at org.hsqldb.Trace.check(Unknown Source) at org.hsqldb.Log.open(Unknown Source) at org.hsqldb.Database$Logger.openLog(Unknown Source) at org.hsqldb.Database.open(Unknown Source) at org.hsqldb.Database.(Unknown Source) at org.hsqldb.jdbcConnection.openStandalone(Unknown Source) at org.hsqldb.jdbcConnection.(Unknown Source) at org.hsqldb.jdbcDriver.connect(Unknown Source) at java.sql.DriverManager.getConnection(DriverManager.java:512) at java.sql.DriverManager.getConnection(DriverManager.java:171) at org.apache.ws.jaxme.pm.jdbc.PMJdbcImpl.getConnection(PMJdbcImpl.java:92) at org.apache.ws.jaxme.test.pm.session.impl.SessionTypePM.select(SessionTypePM.java:173) at org.apache.ws.jaxme.pm.impl.PMImpl.select(PMImpl.java:83) at org.apache.ws.jaxme.pm.impl.PMImpl.select(PMImpl.java:59) at org.apache.ws.jaxme.pm.junit.SessionTest.testClear(SessionTest.java:91) Testcase: testCreate took 0.036 sec Testcase: testInsert took 0.008 sec Caused an ERROR Failed to execute query INSERT INTO HTTPSESSION (ID, IPADDRESS, LOGINTIME, LASTACTION, EXPIRETIME, COOKIE, RANDOMSEED, PRECEDENCE) VALUES (?, ?, ?, ?, ?, ?, ?, ?): Wrong database file version org.apache.ws.jaxme.PMException: Failed to execute query INSERT INTO HTTPSESSION (ID, IPADDRESS, LOGINTIME, LASTACTION, EXPIRETIME, COOKIE, RANDOMSEED, PRECEDENCE) VALUES (?, ?, ?, ?, ?, ?, ?, ?): Wrong database file version at org.apache.ws.jaxme.test.pm.session.impl.SessionTypePM.insert(SessionTypePM.java:54) at org.apache.ws.jaxme.pm.junit.SessionTest.testInsert(SessionTest.java:111) Caused by: java.sql.SQLException: Wrong database file version at org.hsqldb.Trace.getError(Unknown Source) at org.hsqldb.Trace.check(Unknown Source) at org.hsqldb.Trace.check(Unknown Source) at org.hsqldb.Log.open(Unknown Source) at org.hsqldb.Database$Logger.openLog(Unknown Source) at org.hsqldb.Database.open(Unknown Source) at org.hsqldb.Database.(Unknown Source) at org.hsqldb.jdbcConnection.openStandalone(Unknown Source) at org.hsqldb.jdbcConnection.(Unknown Source) at org.hsqldb.jdbcDriver.connect(Unknown Source) at java.sql.DriverManager.getConnection(DriverManager.java:512) at java.sql.DriverManager.getConnection(DriverManager.java:171) at org.apache.ws.jaxme.pm.jdbc.PMJdbcImpl.getConnection(PMJdbcImpl.java:92) at org.apache.ws.jaxme.test.pm.session.impl.SessionTypePM.insert(SessionT
Re: jaxme
On Thu, 2005-09-01 at 06:09 +0200, Stefan Bodewig wrote: > On Tue, 30 Aug 2005, robert burrell donkin <[EMAIL PROTECTED]> wrote: > > > the original plan was to try to run two gump builds until the > > mavenised one was debugged. however, since the original run is no > > longer running very well, i suppose that there may be an argument > > for biting the bullet and moving now. > > I wouldn't expect the Maven run to work any better or worse than the > Ant one, so go ahead if you feel like it. > > The main problems we have with mavenized projects in Gump are > > (1) artifact-Id mismatches > > (2) projects depending on Maven plugins that are not (yet) installed > on the Gump machines. > > The second point somewhat bothers me since we have a few builds that > don't run just because a plugin that we wouldn't use for our builds is not > installed. But that's just me disagreeing with Maven's worldview 8-) i agree that this is a little bit bothersome. i wonder whether it's not so much a problem with the worldview as a lacking feature. i don't know how to specify plugin dependencies for a maven build (so they could be automatically downloaded). without this feature, the build is not truly automatic or replicable. - robert signature.asc Description: This is a digitally signed message part
Re: Gump3 Presentation
Stefano Mazzocchi wrote: Thomas wrote: Hi ! I have now uploaded a working compy of the Gump3 pressentation. The webapplication is far from done. But it would be nice with some feedback. The code is a bit of a mess so refactoring is indeed needed. Mostly I would like idees on what functionality you would like to se in the application. Also a comment on the documentation/installation manual would be nice. My spelling isn't that good so, be nice ;) but don't keep quite either. (need to learn) So if you have the time please take a look. I'm on it. A few comments: 1) thanks for keeping the dynagump resources! 2) I never used struts but seems easy to learn by example, which is good for this (and probably much easier than cocoon for newbies) 3) I never ran a JSP on this machine (macosx) and I'm experiencing all sort of defective behaviors in jetty due to the jsp compiler trying to open a jni library as a zip file (???) 4) the web application should *never* start with a directory listing, the index.jsp page should be in the root not in a folder that you have to guess where to go 5) the tar.gz package should be a war and should contain the classes compiled into /WEB-INF/classes so that you can deploy-and-forget (or at least just change the JDBC parameters) 6) the SQL data seems weird, but this is probably not your fault 7) java 1.5 is, IMNSHO, a little too bleeding edge (especially on a mac) and eclipse gives all sort of warnings. Not having used generics yet, I still have no clue of what they mean and how serious they are. You might want to look into that, though, code should not have warnings. 8) I have not looked into the code yet, as I still can't run JSP pages, but I will as soon as I can. 9) there should be a /legal folder that contains all the licenses of the libraries 10) and would also be nice to have a file that depicts the dependencies between the libraries (so that we could have gump building dynagump) 11) you say the mysql jdbc driver is in /lib but it's not (or at least, not as a standalone jar)... but I suggest we keep it out since it's GPL stuff. In any case, it looks like a very good job from where I stand. Will know more as soon as I can get it running ;-) Seem that Java 1.5 was indeed a bad idea. http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6295519 Thomas, how much work would be to downgrade this to 1.4? -- Stefano. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Gump3 Presentation
Thomas wrote: Hi ! I have now uploaded a working compy of the Gump3 pressentation. The webapplication is far from done. But it would be nice with some feedback. The code is a bit of a mess so refactoring is indeed needed. Mostly I would like idees on what functionality you would like to se in the application. Also a comment on the documentation/installation manual would be nice. My spelling isn't that good so, be nice ;) but don't keep quite either. (need to learn) So if you have the time please take a look. I'm on it. A few comments: 1) thanks for keeping the dynagump resources! 2) I never used struts but seems easy to learn by example, which is good for this (and probably much easier than cocoon for newbies) 3) I never ran a JSP on this machine (macosx) and I'm experiencing all sort of defective behaviors in jetty due to the jsp compiler trying to open a jni library as a zip file (???) 4) the web application should *never* start with a directory listing, the index.jsp page should be in the root not in a folder that you have to guess where to go 5) the tar.gz package should be a war and should contain the classes compiled into /WEB-INF/classes so that you can deploy-and-forget (or at least just change the JDBC parameters) 6) the SQL data seems weird, but this is probably not your fault 7) java 1.5 is, IMNSHO, a little too bleeding edge (especially on a mac) and eclipse gives all sort of warnings. Not having used generics yet, I still have no clue of what they mean and how serious they are. You might want to look into that, though, code should not have warnings. 8) I have not looked into the code yet, as I still can't run JSP pages, but I will as soon as I can. 9) there should be a /legal folder that contains all the licenses of the libraries 10) and would also be nice to have a file that depicts the dependencies between the libraries (so that we could have gump building dynagump) 11) you say the mysql jdbc driver is in /lib but it's not (or at least, not as a standalone jar)... but I suggest we keep it out since it's GPL stuff. In any case, it looks like a very good job from where I stand. Will know more as soon as I can get it running ;-) -- Stefano, who is pleased to have been reminded on why he hated JSPs in the first place :-) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
BATCH: All dressed up, with nowhere to go...
Dear Gumpmeisters, The following 10 notifys should have been sent *** G U M P [EMAIL PROTECTED]: Module jakarta-commons-sandbox success, but with warnings. [EMAIL PROTECTED]: Project asn1-der (in module asn1) failed [EMAIL PROTECTED]: Project txt2html-task (in module jakarta-servletapi-5) success, but with warnings. [EMAIL PROTECTED]: Project mina (in module mina) failed [EMAIL PROTECTED]: Project jtidy-cvs (in module jtidy) failed [EMAIL PROTECTED]: Project stub-compiler (in module asn1) failed [EMAIL PROTECTED]: Project xml-security-tests (in module xml-security) failed [EMAIL PROTECTED]: Project groovy (in module groovy) failed [EMAIL PROTECTED]: Project commons-feedparser (in module jakarta-commons) failed [EMAIL PROTECTED]: Project derby (in module db-derby) failed *** G U M P [EMAIL PROTECTED]: Module jakarta-commons-sandbox success, but with warnings. To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Module jakarta-commons-sandbox contains errors. The current state of this module is 'Success'. Full details are available at: http://vmgump.apache.org/gump/public/jakarta-commons-sandbox/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -ERROR- *** Failed to update from source control. Stale contents *** The following work was performed: http://vmgump.apache.org/gump/public/jakarta-commons-sandbox/gump_work/update_jakarta-commons-sandbox.html Work Name: update_jakarta-commons-sandbox (Type: Update) Work ended in a state of : Failed Elapsed: 15 secs Command Line: svn --quiet update --non-interactive jakarta-commons-sandbox [Working Directory: /usr/local/gump/public/workspace/cvs] - svn: REPORT request failed on '/repos/asf/!svn/vcc/default' svn: Cannot replace a directory from within - To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/jakarta-commons-sandbox/rss.xml - Atom: http://vmgump.apache.org/gump/public/jakarta-commons-sandbox/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 2001092005, vmgump.apache.org:vmgump-public:2001092005 Gump E-mail Identifier (unique within run) #1. *** G U M P [EMAIL PROTECTED]: Project asn1-der (in module asn1) failed To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project asn1-der has an issue affecting its community integration. This issue affects 3 projects, and has been outstanding for 80 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - asn1-der : Apache ASN.1 Tools - kerberos-common : Apache Directory Project - kerberos-protocol : Apache Kerberos Server Full details are available at: http://vmgump.apache.org/gump/public/asn1/asn1-der/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [asn1-der-01092005.jar] identifier set to project name -DEBUG- (Gump generated) Maven Properties in: /usr/local/gump/public/workspace/asn1/der/build.properties -INFO- Failed with reason build failed -DEBUG- Maven POM in: /usr/local/gump/public/workspace/asn1/der/project.xml -DEBUG- Maven project properties in: /usr/local/gump/public/workspace/asn1/der/project.properties -INFO- Project Reports in: /usr/local/gump/public/workspace/asn1/der/target/test-reports -WARNING- No directory [/usr/local/gump/public/workspace/asn1/der/target/test-reports] -INFO- Failed to extract fallback artifacts from Gump Repository The following work was performed: http://vmgump.apache.org/gump/public/asn1/asn1-der/gump_work/build_asn1_asn1-der.html Work Name: build_asn1_asn1-der (Type: Build) Work ended in a state of : Failed Elapsed: 3 secs Command Line: maven --offline jar [Working Directory: /usr/local/gump/public/workspace/asn1/der] CLASSPATH: /opt/jdk1.4/lib/tools.jar:/usr/local/gump/public/workspace/dist/junit/junit.jar - __ __ | \/ |__ _Apache__ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.0.2 The build cannot continue because of the following unsatisfied dependency: nlog4j-1.2.14.jar (try downloading from http://slf4j.org/nlog4j) Total time: 2
BATCH: All dressed up, with nowhere to go...
Dear Gumpmeisters, The following 10 notifys should have been sent *** G U M P [EMAIL PROTECTED]: Module jakarta-commons-sandbox success, but with warnings. [EMAIL PROTECTED]: Project asn1-der (in module asn1) failed [EMAIL PROTECTED]: Project txt2html-task (in module jakarta-servletapi-5) success, but with warnings. [EMAIL PROTECTED]: Project mina (in module mina) failed [EMAIL PROTECTED]: Project jtidy-cvs (in module jtidy) failed [EMAIL PROTECTED]: Project stub-compiler (in module asn1) failed [EMAIL PROTECTED]: Project xml-security-tests (in module xml-security) failed [EMAIL PROTECTED]: Project groovy (in module groovy) failed [EMAIL PROTECTED]: Project commons-feedparser (in module jakarta-commons) failed [EMAIL PROTECTED]: Project derby (in module db-derby) failed *** G U M P [EMAIL PROTECTED]: Module jakarta-commons-sandbox success, but with warnings. To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Module jakarta-commons-sandbox contains errors. The current state of this module is 'Success'. Full details are available at: http://vmgump.apache.org/gump/public/jakarta-commons-sandbox/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -ERROR- *** Failed to update from source control. Stale contents *** The following work was performed: http://vmgump.apache.org/gump/public/jakarta-commons-sandbox/gump_work/update_jakarta-commons-sandbox.html Work Name: update_jakarta-commons-sandbox (Type: Update) Work ended in a state of : Failed Elapsed: 15 secs Command Line: svn --quiet update --non-interactive jakarta-commons-sandbox [Working Directory: /usr/local/gump/public/workspace/cvs] - svn: REPORT request failed on '/repos/asf/!svn/vcc/default' svn: Cannot replace a directory from within - To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/jakarta-commons-sandbox/rss.xml - Atom: http://vmgump.apache.org/gump/public/jakarta-commons-sandbox/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 2001092005, vmgump.apache.org:vmgump-public:2001092005 Gump E-mail Identifier (unique within run) #1. *** G U M P [EMAIL PROTECTED]: Project asn1-der (in module asn1) failed To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project asn1-der has an issue affecting its community integration. This issue affects 3 projects, and has been outstanding for 80 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - asn1-der : Apache ASN.1 Tools - kerberos-common : Apache Directory Project - kerberos-protocol : Apache Kerberos Server Full details are available at: http://vmgump.apache.org/gump/public/asn1/asn1-der/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [asn1-der-01092005.jar] identifier set to project name -DEBUG- (Gump generated) Maven Properties in: /usr/local/gump/public/workspace/asn1/der/build.properties -INFO- Failed with reason build failed -DEBUG- Maven POM in: /usr/local/gump/public/workspace/asn1/der/project.xml -DEBUG- Maven project properties in: /usr/local/gump/public/workspace/asn1/der/project.properties -INFO- Project Reports in: /usr/local/gump/public/workspace/asn1/der/target/test-reports -WARNING- No directory [/usr/local/gump/public/workspace/asn1/der/target/test-reports] -INFO- Failed to extract fallback artifacts from Gump Repository The following work was performed: http://vmgump.apache.org/gump/public/asn1/asn1-der/gump_work/build_asn1_asn1-der.html Work Name: build_asn1_asn1-der (Type: Build) Work ended in a state of : Failed Elapsed: 3 secs Command Line: maven --offline jar [Working Directory: /usr/local/gump/public/workspace/asn1/der] CLASSPATH: /opt/jdk1.4/lib/tools.jar:/usr/local/gump/public/workspace/dist/junit/junit.jar - __ __ | \/ |__ _Apache__ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.0.2 The build cannot continue because of the following unsatisfied dependency: nlog4j-1.2.14.jar (try downloading from http://slf4j.org/nlog4j) Total time: 2
