[opencms-dev] "Content definition" and "Master Module" APIs heading to be obsolete

[Dušan Saiko]

Hi all.

I have found this information from Alexander Kandzior in the mailing 
list, stating that the "Content definition" and the "Master Module"  
will be obsolete in feature releases of OpenCms:

"OpenCms 6 will feature the so called "xmlcontent" for structured content.
This will render the "News" module as well as the "Content definition" and
"Master Module" APIs obsolete."

Our case is, that we have quite complicated object model which is 
interconnected all together and there are thousands of articles written 
in it.
This objects can not be probably stored very much in XML, mainly because 
the inner object references and searching capabilities through the 
object properties.

Could you please help me answering the question, if the content 
definition is going to be deprecated,
what is the best way to develop our OpenCms solution in such a way we 
would have our own data model residing in our own db tables,
and our objects will have most of the OpenCms object properties like 
locking, publishing, versioning/history, wysiwyg form design etc ?
It is quite important question for us right now.

Thanx in advance for help.

Dusan Saiko


In the topic "News Module/Form based editing of content items" Alexander 
Kandzior wrote:

>Hi,
>
>regarding the news module 
>
>  
>
>>>at http://www.opencms.org/opencms/en/support/tour/6.html 
>>>      
>>>
>>i?ve seen a 
>>    
>>
>>>very interesting functionality but i can?t find these in opencms 5 
>>>distribution nor in the modules offered on www.opencms.org.
>>>
>>>Any Hints?
>>>      
>>>
>>AFAIK is this functionality not for free. I do not understand 
>>why the 'news-module' is not included. Many opensource CMS 
>>(postnuke, mambo) have a news-module with 'read more...' option. 
>>
>>Is there any change to give the news-module to the public?
>>    
>>
>
>OpenCms 6 will feature the so called "xmlcontent" for strcutured content.
>This will render the "News" module as well as the "Content definition" and
>"Master Module" APIs obsolete. In short you will be able to create a
>(simplified) XML Schema and define this as a template for content items in
>the workplace. An editor for this will be automatically created accoring to
>the schema. With some simple taglib commands you will be able to access the
>content items and build lists and details pages etc.
>
>The old APIs will remain in the 6.0 release, but not be supported after that
>release. I don't think many people will really want to use the old APIs with
>6.0, so this should be no problem.
>
>The functionality for xmlcontent already is included in the 6.0 alpha 1, but
>it still needs to be refined. We will include a demo for what is already
>available in the next (alpha 2) release. 
>
>Best Regards,
>Alex.
>
>Alexander Kandzior
>Alkacon Software - The OpenCms Experts
>http://www.alkacon.com
>
>  
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://webmail.opencms.org/pipermail/opencms-dev/attachments/20041207/bad5e0a0/attachment.htm>