 |
|
|
Robert Koberg wrote:
> I use the hibernate tools to generate my SQL, but for java they only
> produce the simple bean. Sure this can be modified using well-know
> meta/@attributes.
In md4j we generate all-tier CRUD using XSLT on the mappings.
>> [1] http://dev.abiss.gr/md4j/metadata-reference.html
>
> I started using multiple meta/@attribute, but I found myself bouncing
> against the need for a hierarchy.
Same here, although our XSLTs mostly feed on the model described by the
mapping itself and not the meta.
> I want to use the property element as
> much as possible and I want inherit/override ancestors. For example, if
> a property/@name changes I wouldn't have to change it for the UI's form
> elements, template language variables or javascript validation.
Yep, the iterative process was the main reason we did this, to remove
the need to change code throughout the tiers of the app.
>> [2] http://dev.abiss.gr/md4j/
>
> Cool stuff!
Thanks!
Cheers,
Manos
|
|
| |
These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.
| |
| |
|
|
|
