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>
Date: Fri, 15 Jul 2011 15:27:00 +0000 (UTC)
From: "Thomas Vandahl (JIRA)" <jira@apache.org>
To: torque-dev@db.apache.org
Message-ID: 
 <1692986126.17574.1310743620600.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <292885658.2996.1309937537178.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (TORQUE-163) Map builders are emptied on
 Torque.shutdown() and not rebuilt on subsequent init()
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/TORQUE-163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13066004#comment-13066004 ] 

Thomas Vandahl commented on TORQUE-163:
---------------------------------------

Agreed. The general idea of the Avalon lifecycle contract is the symmetry of initialize/dispose, start/stop etc. So the requirement would be that dispose() or shutdown() left the component or instance in the same state as it was before the first initialize() or init(). Clearly this doesn't work the way Torque is designed right now. Nevertheless, my humble opinion is that we should strive to remove as much static stuff as possible from Torque to reach that goal one day. A clean lifecycle is a Good Thing(TM), be it Avalon or not.

> Map builders are emptied on Torque.shutdown() and not rebuilt on subsequent init()
> ----------------------------------------------------------------------------------
>
>                 Key: TORQUE-163
>                 URL: https://issues.apache.org/jira/browse/TORQUE-163
>             Project: Torque
>          Issue Type: Bug
>    Affects Versions: 3.3
>            Reporter: Thomas Fox
>            Assignee: Thomas Fox
>
> Problem: After a shutdown() and init() of Torque, the Map Builder cache entries which have been present before shutdown are not present anymore after a new init.
> Analysis: If a Peer class is loaded, it registers its map builder and the MapBuilder is built immediately or on Torque initialisation, depending on whether Torque is initialized or not.
> On Torque.shutdown(), all known map builders are removed.
> On a new init(), these Map builders will not be rebuilt anew because the Peer class will not be loaded a second time.
> Solution: The Map Builder cache entries should not be removed on Torque.shutdown()

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

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