svn commit: r481522 - /db/torque/tutorial/trunk/xdocs/step1.xml

Author: tfischer Date: Sat Dec 2 00:59:06 2006 New Revision: 481522 URL: http://svn.apache.org/viewvc?view=revrev=481522 Log: 3.3-RC1 instead of 3.3 in the tutorial Modified: db/torque/tutorial/trunk/xdocs/step1.xml Modified: db/torque/tutorial/trunk/xdocs/step1.xml URL:

tutorial redeployed

I redeployed the tutorial because there were instructions to download 3.3 instead of 3.3-RC1 Thomas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Custom Velocity Renderer (was: Torque 4.0 plan)

Hi Thoralf, would you mind to put this into jira as enhancement ? If I recall correctly, you have done this already, so a diff against the current svn version would be gerat. Thomas On Thu, 30 Nov 2006, Thoralf Rickert wrote: ... Another small topic is my suggestion some months ago

AW: Custom Velocity Renderer (was: Torque 4.0 plan)

Hi! I'll do this at the end of next week - because I've lot of work on my desk at the moment. bye Thoralf Von: Thomas Fischer [mailto:[EMAIL PROTECTED] Gesendet: Sa 02.12.2006 10:13 An: Apache Torque Developers List Betreff: Custom Velocity Renderer (was:

Aliases with Joins (was: Torque 4.0 plan)

Hi Thoralf, When you have time, could you describe what you did there ? Thomas On Fri, 1 Dec 2006, Thoralf Rickert wrote: I forgot something: We've implemented a working and easy way to use Aliases with JOINs. This is necessary if you join a table twice.

Status of discussion Torque 4.0

Hi, To get an overview of the torque 4.0 discussion status, here's what I consider the current status of discussion. If you think otherwise, please complain. I'll also set up a wiki page which is intended to keep pace with the current state of discussion (but not as replacement for discussion

[g...@vmgump]: Project db-torque-gen (in module db-torque-gen) 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 db-torque-gen has an issue affecting its community integration. This issue

[Db-torque Wiki] Update of FrontPage by ThomasFischer

Dear Wiki user, You have subscribed to a wiki page or wiki category on Db-torque Wiki for change notification. The following page has been changed by ThomasFischer: http://wiki.apache.org/db-torque/FrontPage The comment on the change is: Create link to Torque 4 page

[Db-torque Wiki] Update of TorqueFour by ThomasFischer

Dear Wiki user, You have subscribed to a wiki page or wiki category on Db-torque Wiki for change notification. The following page has been changed by ThomasFischer: http://wiki.apache.org/db-torque/TorqueFour New page: = Torque 4 = The plans of the Torque development team for Torque 4 are

[Db-torque Wiki] Update of NextRelease by ThomasFischer

Dear Wiki user, You have subscribed to a wiki page or wiki category on Db-torque Wiki for change notification. The following page has been changed by ThomasFischer: http://wiki.apache.org/db-torque/NextRelease The comment on the change is: Removed suggestions that are already implemented

[Db-torque Wiki] Update of TorqueFour by ThomasFischer

Dear Wiki user, You have subscribed to a wiki page or wiki category on Db-torque Wiki for change notification. The following page has been changed by ThomasFischer: http://wiki.apache.org/db-torque/TorqueFour The comment on the change is: contents moved to NextRelease

[Db-torque Wiki] Update of NextRelease by ThomasFischer

Dear Wiki user, You have subscribed to a wiki page or wiki category on Db-torque Wiki for change notification. The following page has been changed by ThomasFischer: http://wiki.apache.org/db-torque/NextRelease The comment on the change is: Detailed descriptions of the Torque 4 plan

Non-static Peers (was: Torque 4.0 plan)

Oops, I used the swear word singleton ... Fortunately, I probably misused it. I did not mean to enforce singleton behaviour, i.e. to forbid the existence of more than one instance. The static wrapper would be for ease of usage, the Backend class for those which do not want to use static method

Re: Primitives or not

On Fri, 1 Dec 2006, Thomas Vandahl wrote: Greg Monroe wrote: On the record side of things, I can't see that it's a big problem to keep supporting the primitive XML option. Let the application designer decided whether to use primitive or objects via this. It's only a VERY small set of

Maven 2 support in 4.0 (Was: Torque 4.0 plan)

I'd be -1 to switch to an ant build. It seems that people tend to forget the advantages that a maven build has, e.g. : - Maven has an easy dependency managing mechanism - Maven automatically executes the tests during building - Maven creates all these useful reports on the site And building the

[g...@vmgump]: Project db-torque (in module db-torque) 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 db-torque has an issue affecting its community integration. This issue affects 1

[g...@vmgump]: Project db-torque (in module db-torque) 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 db-torque has an issue affecting its community integration. This issue affects 1

Re: Maven 2 support in 4.0 (Was: Torque 4.0 plan)

Sure. As I said, I strongly recommend you to *think* before moving. Not to not moving at all. My point is about maintainability, not about technology. You don't have to list the advantages of maven 2 for development / site building to me. :-) Best regards Henning On Sat,