db-torque-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Vandahl (JIRA)" <j...@apache.org>
Subject [jira] Assigned: (TORQUE-121) Peer generation, using Peer.vm does not call super class' methods but always calls BasePeer.method(...)
Date Sun, 22 Mar 2009 18:21:50 GMT

     [ https://issues.apache.org/jira/browse/TORQUE-121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Thomas Vandahl reassigned TORQUE-121:
-------------------------------------

    Assignee: Thomas Vandahl

> 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
>            Assignee: Thomas Vandahl
>             Fix For: 4.0
>
>         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


Mime
View raw message