Mailing-List: contact torque-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Torque Developers List" <torque-dev@db.apache.org>
Received-SPF: pass (hermes.apache.org: local policy)
Message-ID: <4237FA60.7090105@tewisoft.de>
Date: Wed, 16 Mar 2005 10:20:32 +0100
From: Thomas Vandahl <thomas.vandahl@tewisoft.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
 rv:1.6) Gecko/20040113
MIME-Version: 1.0
To: Apache Torque Developers List <torque-dev@db.apache.org>
Subject: Re: merge Object.vm and ObjectwithManager.vm
References: 
 <OFDB6E73DC.E0063171-ONC1256FC6.0027D879-C1256FC6.00286692@seitenbau.net>
In-Reply-To: 
 <OFDB6E73DC.E0063171-ONC1256FC6.0027D879-C1256FC6.00286692@seitenbau.net>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Thomas Fischer wrote:
> by the effort of Thomas Vandahl, the templates Object.vm and
> ObjectWithManager.vm are in sync once again. If one compares these two
> templates now, there are very little differences. In my opinion, this
> situation should be used to merge the two templates into one, thus reducing
> the need to keep the two in sync manually.
When I went through the code, this was my first intention as well. As 
you know, I use the manager code including JCS caching. If 
torque.objectIsCaching is true, the objects keep their collections in 
the cache as well. This is bad because you need to invalidate the whole 
object with all collections if only one of the objects in a collection 
is modified. So my idea was to add a MethodResultCache for every 
collection including all necessary listeners to the ObjectWithManager 
code. For that reason I would rather not merge the two files.

Bye, Thomas.


---------------------------------------------------------------------
To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
For additional commands, e-mail: torque-dev-help@db.apache.org