> How do you think? Is going to be a good direction to:
> 1) specify a standard way for including additional functionality (product=
ionality)
> in the torque-generator (at least some manual for extending the templates=
)
That would be nice to have a velocity template generator (using velocity
?!) , before adding a property to the column in torque DTD !
Does such a generator exist ? is it the aim of org.apache.torqur-gen ?
I guess it's not.
But if xml validation is set to false, I think you can extend your
torque-schema to a super-set and include attribute in you columns and do
wathether you like with it. Definitly it won't concern OM-datalayer
isn't it ?
> 2) extend devaki to be able to include custom defined attributes=20
> inside the column/table tags
If you had to do that how would you do it ?
Got an idea about this, is that right :
1) add a visible column, that's always good to have that propertie
2) add a key-value pair column named attribute (ex: owner=3Dbob,rocks=3Dtru=
e)
After you feedback (few weeks ago) I also added the ability to add
custom build.properties . They were always overwritten ...
> 3) extend (or make extendable) the org.apache.torque.model to support the=
xml
> parsing and objectizing of user defined objects/attributes
> for example in my case i might define inside the xml model some attribute=
s for
> my columns like (include the column in the html table or not; for now i =
think i=20
> can realize this only by using the column's description attribute to defi=
ne=20
> extra functionality)
I think that Torque will stay an OM-datalayer but that would be very
nice to have a database of velocity template.
Also a database of model would be very nice for educational purpose.
Both should be two standalone projects.
You should have to suggest it as a torque-gen patch.
The rest will/must/should be integrated in devaki-nextobjects.
That should be a request for feature at sf.net project tools.
EF
|
