DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=42994>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=42994 ------- Additional Comments From [EMAIL PROTECTED] 2007-08-05 04:50 ------- (In reply to comment #6) > (In reply to comment #5) > > (In reply to comment #4) > > > Maybe we can add a some workflow schema presets to the workflow module? > > > > hmmm. that means publications would have to place their workflow in > > <pub>/lenya/modules/workflow/config... > > No, they are addressed via URLs so they can be everywhere. <snip> > I don't think we need fallback for workflow schemas, since you typically don't > override a schema, but use a different one (which has a different name). > i'd like to reduce boilerplate code in publications, and to sprinkle some more "convention over configuration" fairy dust on the publications... hence my wish to use fallback. but you are right, we could also accomplish this by setting a default URL that points to a minimal workflow.xml in the core, and it can be overridden by using the workflow attribute in publications.xml/resource-types/resource-type. but the advantage of using fallback:// is that this configuration option is discoverable for users. everybody will read their publication.xml and find out they can override the workflow if there is a fallback:// entry. the absence of an attribute is rather less enlightening :) > > this core workflow should include authoring and live as states and edit, > > publish > > and maybe deactivate as events. i guess this is the minimal subset below > > which a > > cms no longer makes sense. wdyt? bob has a point in that there may not even be a publish transition. but regardless of that, i'd say we should provide our default publication workflow in the core, so that all interesting features of Lenya are available without requiring boilerplate code. users can always replace it with a more minimalistic one. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
