Hi James,
I'm just looking over the maven project descriptor in the tests and I
was thinking again about a 'standard' format for XML files and was
wondering if you had any opinions?
Using all lower case:
<project>
...
</project>
Where the root element matches to a Project class.
And something like:
<short-description>Project Management Tool</short-description>
and having that map to the setShortDescription(String) property.
Or having the XML elements have Java variable looking names like:
<Project>
...
</Project>
and
<shortDescription>...</shortDescription>
I honestly prefer the lower case with hypens but I'm not all that fussy.
I will use the default behavior of betwixt to map everything that I've
used my little mapper for so that all things Turbine will eventually use
the a common format so that mapping will be consistent, error free and
easy.
Also how are nested objects created? Are they expected to be in the same
package as the parent class?
So if I have:
<project>
<mailing-lists>
<mailing-list>
<name/>
<description/>
<subscribe/>
<unsubscribe/>
<archive/>
</mailing-list>
</mailing-lists>
</project>
Is the MailingList class expected to be in the same package as Project
class?
Also would you mind if something like the following was added as default
behaviour:
<pipeline>
<valve className="o.a.t.valve.Valve1"/>
<valve className="o.a.t.valve.Valve2"/>
</pipeline>
Where the className attribute would be used to instantiate the desired
object?
In the little mapper I made I used attributes as mapping information and
the elements as bean data. Maybe you are doing the same but I'm just
getting familiar with betwixt but I love it so far it's exactly what
I've been wanting I just didn't know it :-)
--
jvz.
Jason van Zyl
[EMAIL PROTECTED]
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
