sbasani wrote:
> Ralf,
>
> Thanks for the reply.
>
> You are concentrating on the example I am explained initially.
>
> But, that just sample example.
>
> In runtime only it'll be decided, how many parameters we are going to have
> and based on that parameters we have to create the xml file. We can't
> predict the xml file structure at initial stage.
>
> For ex:
>
> <Supermarket>
> <Item1></Item1>
> <Item2></Item2>
> <Item3></Item3>
> <Item4></Item4>
> <Item5></Item5>
> <Item6></Item6>
> <Item7></Item7>
> ....
> ....
> ....
> ....
> </Supermarket>
>
> Like the above example, initially we don't no how many items are there.
> Based on the requirement in runtime we have to decide..
>
> For clear understanding...
>
> <xmlfile>
> <supermarket>
> <name></name>
> <order>
> <Item1></Item1>
> <Item2></Item2>
> <Item3></Item3>
> <Item4></Item4>
> <Item5></Item5>
> <Item6></Item6>
> <Item7></Item7>
> </order>
> <order>
> <Item1></Item1>
> <Item2></Item2>
> <Item3></Item3>
> </order>
> <order>
> <Item1></Item1>
> <Item2></Item2>
> <Item3></Item3>
> <Item4></Item4>
> <Item5></Item5>
> </order>
> </supermarket>
> <xmlfile>
>
> In the above xml file, parent tags are fixed like super tag <xmlfile>,
> <order> and sub parent tag <Supermarket>, but the attributes(Items) of
> <Supermarket> are not defined (as fixed number of items we will get). We can
> say like 'n' number of Items can come.
> Is there any way to define Items as collection?
Yes, but only if you happen to be using a type hierarchy.
>
> Please let me know, if you need any clarification.
>
> Thanks & Regards,
> Sree
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
