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 "Tal Kramer (JIRA)" <ji...@apache.org> on 2009/02/11 11:45:02 UTC
[jira] Updated: (TORQUE-121) Peer generation, using Peer.vm does
not call super class' methods but always calls BasePeer.method(...)
[ https://issues.apache.org/jira/browse/TORQUE-121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tal Kramer updated TORQUE-121:
------------------------------
Attachment: Peer.vm
Suggested solution, based on Peer.vm from torque-gen-3.1.1.jar
> Peer generation, using Peer.vm does not call super class' methods but always calls BasePeer.method(...)
> -------------------------------------------------------------------------------------------------------
>
> Key: TORQUE-121
> URL: https://issues.apache.org/jira/browse/TORQUE-121
> Project: Torque
> Issue Type: Bug
> Affects Versions: 3.1.1
> Environment: Java
> Reporter: Tal Kramer
> Attachments: Peer.vm
>
>
> When generating the om, the *Peer generated classes call BasePeer methods when calling to the original method, This ignores the base class.
> On generation, it is possible to define a basePeer object, but it is irrelevant at the current state since it is not used within the static generated class.
> To fix it, I have replaced in torque-gen.XX.jar in the file om/Peer.vm all calls to BasePeer.method(...) by ${table.BasePeer}.method(...). Is there a better solution? Or anything wrong with this suggestion?
--
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: torque-dev-unsubscribe@db.apache.org
For additional commands, e-mail: torque-dev-help@db.apache.org