You are viewing a plain text version of this content. The canonical link for it is here.
Posted to torque-dev@db.apache.org by "Thomas Fox (JIRA)" <ji...@apache.org> on 2011/05/29 19:43:47 UTC
[jira] [Resolved] (TORQUE-159) Split generated peer classes into
implementation and a static wrapper
[ https://issues.apache.org/jira/browse/TORQUE-159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thomas Fox resolved TORQUE-159.
-------------------------------
Resolution: Fixed
Fix Version/s: 4.0
> Split generated peer classes into implementation and a static wrapper
> ---------------------------------------------------------------------
>
> Key: TORQUE-159
> URL: https://issues.apache.org/jira/browse/TORQUE-159
> Project: Torque
> Issue Type: New Feature
> Affects Versions: 3.3
> Reporter: Thomas Fox
> Assignee: Thomas Fox
> Fix For: 4.0
>
>
> The peer classes are accessed in a static way so the behavior cannot be changed at runtime. This is bad e.g. when one wants to insert mock classes for testing.
> Therefore, the peer classes shoul be plit into a static wrapper which holds an implementation class and delegates all function calls to the implementation class. the implementation can be exchanged via a setter. The static fields should stay in the static wrapper.
--
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