[opencms-dev] schema recursion ....

Ruben Malchow ruben at disk0.de
Wed Jun 30 10:58:03 CEST 2010


hi achim

well, in my case, this would be input for a custom selector widget that 
lets you select from items in a hierarchy. also, the actual depth is 
defined by what the user actually wants to put in there.

i __could__ make it a N-level hierarchy with a fixed N, but that's even 
more ugly than arbitrary recursion that _could_ get kind of awkward if 
the user really, really wants that.

i think the main point is that the content definition is only cached 
after it has been completely parsed (CmsXmlContentDefinition, line 753 
in v7.5.2). if it would be parsed before unmarshal goes into the 
contents of it, it would be fine ... i guess.

.rm



On 30/06/2010 16:10 , Achim Westermann wrote:
> Hi Florian,
>
> just think how this should look in the XML content editor. A box in a box in a box in a box in a box in a box....
> Developers, don't forget "end user bility" when hunting the perfect data model ;-).
>
> cheers,
>
> Achim
> -------- Original-Nachricht --------
>> Datum: Wed, 30 Jun 2010 09:59:50 +0200
>> Von: Florian Hopf<hopf at synyx.de>
>> An: The OpenCms mailing list<opencms-dev at opencms.org>
>> Betreff: Re: [opencms-dev] schema recursion ....
>
>> Hi,
>>
>> I just this week also had the need to develop a recursive structure and
>> it didn't work. The root cause seems to be that in
>> CmsXmlContentDefinition the visited nested elements are only stored
>> locally so there's no way to tell if an element has been visited before.
>>
>> I think this could be fixed quite easily but I am worried that there are
>> more reasons why this is not allowed?
>>
>> Regards
>
> _______________________________________________
> This mail is sent to you from the opencms-dev mailing list
> To change your list options, or to unsubscribe from the list, please visit
> http://lists.opencms.org/mailman/listinfo/opencms-dev



More information about the opencms-dev mailing list