Modules as content tree nodes

Tuesday 20 November 2007 9:43:15 am

Maybe a risky question ;)

Is it possible to change the default behavior of eZ Publish where all content nodes encapsulate content to one where nodes encapsulate my own extension/module? For example:

+ root (id:2)
  + some content (id:100)
    + MODULE NODE (id:101)
  + other content (id:102)

So that <i>MODULE NODE</i> does not actually reach content data, but rather runs my own module? In other words, the URL <b>/root/some_content/module_node</b>, instead of being translated to <b>/content/view/full/101</b> or overriden in any way, gets translated into <b>/custommodule/customview/101</b>... ?
Would it be entirely against the core of eZ?

Please let me know what you think about it or what do I miss ;)

Thanks,
Piotrek

--
Company: mediaSELF Sp. z o.o., http://www.mediaself.pl
eZ references: http://ez.no/partners/worldwide_partners/mediaself
eZ certified developer: http://ez.no/certification/verify/272585
eZ blog: http://ez.ryba.eu