This post originated from an RSS feed registered with Java Buzz
by Fred Grott.
Original Post: I was wrong, C-JDBC-2.0.1dtd
Feed Title: ShareMe Technologies LLC-The Mobile Future
Feed URL: http://www.jroller.com/shareme/feed/entries/rss
Feed Description: A Weblog about Java programming and digital convergence on mobile devices in such areas as P2P and collaborative technology.
The C-JDBC-2.0.1.dtd is in fact correct. The confusion is in the differences in direcitons between the manual, ApacheCon notes, and etc. To increase the confusion the manual is not per version, ie the same manual for all releases with no sign of corrections for the newer versions.
The RecoveryLog example from ApacheCon is close to what you need to use in C-JDBC-2.0.1 but I still get an error. Not the same error in using the example recoveryLog with the binary as that was cannot check JDBCRecoveryLog. Thus, its download the source and go directly to the class in the error log and see what is happening with the RecoveryLog elements set in my virtualdatabase xml configuration file.
Its still very aggravating with XML errors that should have been caught via XMl validation, differences between the manual and examples, and etc in what should be a mature release from a mature project such as C-JDBC. Not that the features are not desired and appreciated. In fact, I do appreciate having a log of the controller actions/trace so that I can track which part of the C-JDBC directions are incorrect.
Previous Topic
