Doug Chestnut wrote:
-1 This requirement is just imposing something which is in many cases
not necessary at all, e.g.
Search Engine Screen
Dynamic Listing
Aggregation of various content
....
I am afraid that my knowledge of doctypes/publets in 1.4 is too
limited for me to vote, but wouldn't the above examples be considered
usecases and not doctypes? (possibly usecases of the doctype
publet?). Sorry for another stupid question :).
no problem ;-) I might have to explain why the change was done in the
first place:
When you apply the menu transformer, which is a meta-stylesheet then the
workflow is being triggered within (global-sitemap.xmap, see lenya-page)
and this leads
to an error if there is no workflow. So the problem isn't really about
doctypes
or usecases or whatsoever.
But beside the original reason for the fix I strongly believe that doctypes
do not necessarily need a workflow. For instance an aggregation doctype
makes
sense in many cases resp. a portlet doctype, whereas the aggregated
content might
have a workflow, but the envelope doesn't need on.
Michi
--Doug
Let's not put a requirement which makes development very rigid.
Michi
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Michael Wechner
Wyona - Open Source Content Management - Apache Lenya
http://www.wyona.com http://lenya.apache.org
[EMAIL PROTECTED] [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
