Good point, hadn't thought about that. :)
Thanks,
Nick Stolwijk
~Java Developer~
Iprofs BV.
Claus Sluterweg 125
2012 WS Haarlem
www.iprofs.nl
On Mon, Sep 29, 2008 at 2:34 PM, Jeroen Reijn <[EMAIL PROTECTED]> wrote:
> So if I understand it correctly, the pagelayout is determined by the
> available types, which are specified in the types.xml. Now you need some
> types (for the portal) that are not present in the types.xml.
>
> What about changing the pipeline to an aggregate that reads both type.xml as
> well as portal-types.xml or something like that?
>
> Of course it will mean that you will have 2 places to maintain it, but as
> long as it's document in this matcher, it should be clear to everyone right?
>
> Jeroen
>
> Nick Stolwijk wrote:
>>
>> For our cocoon frontend we use the sitemenu to order our content. This
>> file is according to an XSD which includes the generated
>> sitemenu-types xsd. From the cms code:
>>
>> <map:match pattern="schemas/generated/sitemenu-types.xsd">
>> <map:generate
>> src="{globalconstants:cms-types-dir}/{globalconstants:cms-types}"/>
>> <map:transform src="types2sitemenu.xsl"/>
>> <map:serialize type="xml"/>
>> </map:match>
>>
>> The types.xml used here (as variable cms-types) is used to determine
>> the possible values of the template tag in the sitemenu. Now we have a
>> few template types, which don't have a corresponding item in the
>> types.xml. These templates are used by our hippo portal, which also
>> uses the sitemenu xml to setup its sitemap.
>>
>> I am trying to extend our sitemenu xsd to include those template
>> types, so the sitemenu is editable by Xopus again. (Now we can not
>> edit it because it isn't valid according to its XSD.
>>
>> With regards,
>>
>> Nick Stolwijk
>> ~Java Developer~
>>
>> Iprofs BV.
>> Claus Sluterweg 125
>> 2012 WS Haarlem
>> www.iprofs.nl
>>
>>
>>
>> On Mon, Sep 29, 2008 at 12:08 PM, Jeroen Reijn <[EMAIL PROTECTED]>
>> wrote:
>>>
>>> Hi Nick,
>>>
>>> I'm not really sure, what you are actually trying to achieve. Could you
>>> perhaps elaborate a bit more on the usecase? I'm a bit confused by the
>>> sitemenu.xsd and the types.xml.
>>>
>>> Regards,
>>>
>>> Jeroen
>>>
>>> Nick Stolwijk wrote:
>>>>
>>>> Hi,
>>>>
>>>> I want to add some template types to the sitemenu.xsd, but without a
>>>> corresponding content type. Only the PageType xsd element is generated
>>>> by the CMS system, based on the types.xml. Is it possible to add some
>>>> templates without their corresponding content-type?
>>>>
>>>> With regards,
>>>>
>>>> Nick Stolwijk
>>>> ~Java Developer~
>>>>
>>>> Iprofs BV.
>>>> Claus Sluterweg 125
>>>> 2012 WS Haarlem
>>>> www.iprofs.nl
>>>> ********************************************
>>>> Hippocms-dev: Hippo CMS development public mailinglist
>>>>
>>>> Searchable archives can be found at:
>>>> MarkMail: http://hippocms-dev.markmail.org
>>>> Nabble: http://www.nabble.com/Hippo-CMS-f26633.html
>>>>
>>> ********************************************
>>> Hippocms-dev: Hippo CMS development public mailinglist
>>>
>>> Searchable archives can be found at:
>>> MarkMail: http://hippocms-dev.markmail.org
>>> Nabble: http://www.nabble.com/Hippo-CMS-f26633.html
>>>
>>>
>> ********************************************
>> Hippocms-dev: Hippo CMS development public mailinglist
>>
>> Searchable archives can be found at:
>> MarkMail: http://hippocms-dev.markmail.org
>> Nabble: http://www.nabble.com/Hippo-CMS-f26633.html
>>
> ********************************************
> Hippocms-dev: Hippo CMS development public mailinglist
>
> Searchable archives can be found at:
> MarkMail: http://hippocms-dev.markmail.org
> Nabble: http://www.nabble.com/Hippo-CMS-f26633.html
>
>
********************************************
Hippocms-dev: Hippo CMS development public mailinglist
Searchable archives can be found at:
MarkMail: http://hippocms-dev.markmail.org
Nabble: http://www.nabble.com/Hippo-CMS-f26633.html
