Here's a message in the mail archive which links to the resources for creating turbine xdocs. http://www.mail-archive.com/turbine- user%40jakarta.apache.org/msg05837.html
Maven has taken off since the time that conversation took place, but I think most of the rules still apply. Since you are proposing modifications to the existing docs, it would be especially helpful if you would submit your changes as a patch to the existing xdoc addressed turbine-torque-dev with [PATCH] in the subject line. Unidiffs (diff -u) are the preferred form of patch. See the Patches section of this doc: http://jakarta.apache.org/site/source.html Hope that helps. -Eric On Tuesday, April 9, 2002, at 01:51 PM, Peter S. Hamlen wrote: > I've now gotten the Postgres drivers (7.2.1) to work with Turbine 2.1. > The Postgres-Torque HOWTO is out of date, and the TDK does not work > "out-of-the-box". The Postgres db.props file must be altered so that > VARBINARY is translated to "bytea" not "oid". (I have a diff, and > instructions on what has to change.) > > What's the best way to get this information into the documentation? > > Details: > Before Postgres 7.1, Postgres required that fields larger than 8K need > to stored as "large objects". Unfortunately, the Postgres driver > returned the "type" of these large objects as "oid" which is int4 > instead of varbinary. So the postgres-Torque HOWTO describes a patch > you need to make in order to have the driver work correctly. > > Now that Postgres 7.1 has been released, that patch is no longer needed > (and, indeed, doesn't work as Field.java has been changed and so you > have to patch in Connection.java instead. Even then, it doesn't work > correctly.) Instead, you merely need to change the field for > "VARBINARY" to "bytea" in the db.props file. (Nice coding in the Turbine > files, btw, to make this so clean to change.) > > -Peter Hamlen > > On Tue, 2002-04-09 at 10:40, Peter S. Hamlen wrote: >> Having spent some time trying to get Turbine 2.1 to work with >> Postgresql >> 7.2.1 (and being only partially successful), it looks like the >> Postgres-Turbine HOWTO is out of date. >> >> I'm getting the same error mentioned in the HOWTO - namely that the >> Postgres driver needs to be modified to see an OID as a VARBINARY, not >> an integer. However, it looks like the code has been reorganized for >> the >> Postgres Java Driver and so the patch needs to be changed (because you >> have to make the changes in /org/postgresql/jdbc2/Connection.java >> rather >> than in /org/postgresql/Field.java) >> >> Even making the patch as described (but now in the correct file), I >> still get an error when trying to create/modify users... >> >> Exception: java.lang.reflect.InvocationTargetException >> Stack Trace follows: >> java.lang.reflect.InvocationTargetException: java.sql.SQLException: >> ERROR: oidin: error in >> "\254\355\000\005sr\000\023java.util.Hashtable\023\273\017%!J\344\270\003\ >> 000\002F\000\012loadFactorI\000\011thresholdxp?@\000\000\000\000\000\000w\ >> 010\000\000\000\001\000\000\000\000x": can't parse >> "\254\355\000\005sr\000\023java.util.Hashtable\023\273\017%!J\344\270\003\ >> 000\002F\000\012loadFactorI\000\011thresholdxp?@\000\000\000\000\000\000w\ >> 010\000\000\000\001\000\000\000\000x" >> >> So I was wondering: >> a) is there updated documentation that I'm missing? Am I just being >> stupid? >> b) if the answer to (a) is "no", I'm willing to put together a revised >> HOW-TO. In which case, if someone has any information on how to >> eliminate this remaining problem, I would appreciate it (and include it >> in the HOW-TO.) >> >> -Peter >> >> >> -- >> To unsubscribe, e-mail: <mailto:turbine-torque-user- >> [EMAIL PROTECTED]> >> For additional commands, e-mail: <mailto:turbine-torque-user- >> [EMAIL PROTECTED]> >> > > > > -- > To unsubscribe, e-mail: <mailto:turbine-torque-user- > [EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:turbine-torque-user- > [EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
