[
https://issues.apache.org/jira/browse/TORQUE-147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12917183#action_12917183
]
Christoph Engelbert commented on TORQUE-147:
--------------------------------------------
Personally I like the idea of removing inheritance to give the opinion of
inheriting from other classes. If something is needed to recognize it as an
legal Torque object it could be an marker interface or marker annotation.
But for me, if I'm not wrong, there's a problem about (at least) the Maven
plugin which regenerates the BaseClasses on every build or do you guys want to
remove that double-class concept at all?
> Database objects should not need to inherit from BaseObject
> -----------------------------------------------------------
>
> Key: TORQUE-147
> URL: https://issues.apache.org/jira/browse/TORQUE-147
> Project: Torque
> Issue Type: Improvement
> Reporter: Thomas Fischer
> Assignee: Thomas Fischer
>
> Currently it is an error if database objects do not inherit from BaseObject.
> This makes embedding of Torque objects in other frameworks very difficult,
> because it does not allow to choose an own parent to inherit from.
> The minimum requirement would be that it is not required any more that
> database objects inherit from BaseObject.
> Ideally BaseObject dies and the base objects inherit directly from
> java.lang.object.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
