[opencms-dev] OCMS6.0alpha3: create new ressourcetypes for xmlcontent - common practice or howto?
Manfred Schenk
manfred.schenk at zerobyte.de
Fri Jan 7 22:59:33 CET 2005
Hi!
Looking into the source code of OCMSalpha1 and OCMSalpha3 I think there
were some changes in the way to create a new type for xmlcontent and the
post of Alex (It's from Oct 30, 2004 - a reply to a message from Marc
Davenport - the title was "XML Content Demo". ) seems to be a little
outdated.(The confusing part is the changing of opencms-vfs.xml .)
I found the following definitions in the xmlcontent module but don't
know how to produce them using the workplace.
(excerpt from manifest.xml of the xmlcontent module)
...
<resourcetypes>
<type class="org.opencms.file.types.CmsResourceTypeXmlContent">
<param name="resource.type.id">12</param>
<param name="resource.type.name">article</param>
<param name="schema">/sites/default/xmlcontent/article.xsd</param>
</type>
<type class="org.opencms.file.types.CmsResourceTypeXmlContent">
<param name="resource.type.id">13</param>
<param name="resource.type.name">widgetdemo</param>
<param
name="schema">/sites/default/xmlcontent/widgetdemo/widgetdemo.xsd</param>
</type>
<type class="org.opencms.file.types.CmsResourceTypeXmlContent">
<param name="resource.type.id">14</param>
<param name="resource.type.name">bookmark</param>
<param
name="schema">/sites/default/xmlcontent/nestedcontent/bookmark.xsd</param>
</type>
</resourcetypes>
...
A solution may be:
a) create a module with the gifs, properties, xsds ...
b) export the module
c) change the manifest.xml of the module by hand
d) reimport the changed module
Is there an easier way to achieve the same goal - perhaps using the
workplace?
Did I miss something in list of steps?
ciao,
Manfred
--
| Manfred Schenk | born between RFC638 and RFC640
| PGP-Keys unter |
| http://www.ZEROByte.de/pgp/ | WWW: http://www.ZEROByte.de/
More information about the opencms-dev
mailing list