Need some advice or guidance on Custom Tags and XML-body

What is better:

a) Implementing custom tags for the children:

<mytag:Computer>

<mytag:Param key="foo" value="bar" />

<mytag:Param key="bar" value="foo" />

<mytag:Param key="some" value="stuff" />

</mytag:Computer>

b) parsing the body, which is xml:

<mytag:Computer>

<params>

<param>

<key>foo</key>

<value>bar</value>

</param>

<param>

<key>bar</key>

<value>foo</value>

</param>

</params>

</mytag:Computer>

Are there any benefits going the xml-way here or would I be better off implementing a custom tag for the params too, as for the Computer tag.

[954 byte] By [Ashama] at [2007-11-26 14:57:14]
# 1
Okay, I must have asked the wrong question or something.In terms of performance then, what would be better? I'm guessing <tags> but what I do know.
Ashama at 2007-7-8 8:45:55 > top of Java-index,Enterprise & Remote Computing,Web Tier APIs...
# 2
For myself I think the custom tag approach looks neater.However you're the designer of this tag - it is entirely up to you.I don't think there will be any significant difference in execution speed - just choose the one that fits your circumstances the best.
evnafetsa at 2007-7-8 8:45:55 > top of Java-index,Enterprise & Remote Computing,Web Tier APIs...
# 3
Ok, cool. If it is a matter of personal taste and there's no major performance difference between the two, I think I'll go with XML.
Ashama at 2007-7-8 8:45:55 > top of Java-index,Enterprise & Remote Computing,Web Tier APIs...
# 4

> Ok, cool. If it is a matter of personal taste and

> there's no major performance difference between the

> two, I think I'll go with XML.

IMHO, unless you know it beforehand, writing custom tags has significant rampup curve. Deployment is a headache for first time users. But then, as with most such things, the end result (which is a lot of knowledge gained) is worth the effort :)

ram.

Madathil_Prasada at 2007-7-8 8:45:55 > top of Java-index,Enterprise & Remote Computing,Web Tier APIs...