Hi Thomas, hi Youngho,

this is quite straightforward - package is an allowed element (but not yet 
in schema) in 
org.apache.torque.templates.transformer.om.InheritanceAttributeName.

But as the class says about itself it "Contains the attributes for a 
inheritance source element which are not defined in the Torque schema."

That is, if we want to allow it to be changed in xml we have to change the 
schema (database-5-0.xsd) as well, updating e.g. to a internal version 5.1 
seems to be sufficient as it is an optional attributes addition.

The same is true for beanPackage, but some intricaties are to be respected 
with extends bean package heuristics.

I could think of adding a patch to issue Torque-360 or commit the changes 
as I may also fix a bug (while checking the compiled generated classes).

.. should be continued in Torque-dev mailing list..

Best regards, Georg



Von:    Thomas Vandahl <t...@apache.org>
An:     Apache Torque Users List <torque-user@db.apache.org>
Datum:  16.11.2021 13:54
Betreff:        Re: Inheritance question



Hi Youngho,

> Am 15.11.2021 um 22:20 schrieb 조영호 <youn...@easydesk.co.kr>:
> 
> I would like to look at the code if I have an available time.
> Where is a good starting point?

I suggest to look at 
org.apache.torque.templates.transformer.om.OMInheritanceTransformer in the 
torque-templates project as a starting point.
Line 69 looks promising to me.

Bye, Thomas 
---------------------------------------------------------------------
To unsubscribe, e-mail: torque-user-unsubscr...@db.apache.org
For additional commands, e-mail: torque-user-h...@db.apache.org



Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to