OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]
Re: [xml-dev] Best way to create an XML document

On Sat, 2008-04-12 at 20:50 +0100, Andrew Welch wrote:
> I was looking for the "top down" approach where you annotate a class
> it just creates the XML for you, as opposed to the "bottom up"
> approach where you supply the schema and it autogenerates the classes.
> Ideally you should be able to just annotate a class with something
> like @XMLEntity, pass it to the entity manager's save() method and
> have it create the XML for you - just like JPA  :)

This shouldn't be too hard. Something like:


and the annotation processor just goes through the non-transient fields

  <field1>field1 value</field1>

It has also made me rethink putting my metadata for forms/UI in a
hibernate mapping file (@XMLEntityForm). It would seem like a good
compile time annotation to generate a form/js 'stub' that can be
included in a transformation later in the build process. I would still
need method level annotations (a lot could be done with the existing JPA
and/or hibernate annotations). hmmm... I think I will work on these in
the next few days.

thanks for making me think :)

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]

News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 1993-2007 XML.org. This site is hosted by OASIS