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:23 ------- (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. > i'd rather have them in webapp/lenya/config/workflow, so that the current > location does not have to change (i hope that's where fallback:// would look, > but i'd need to check that). 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). > but if you disagree, any other place is fine with me. my main issue is that we > do make assumptions about states and transitions being there, and these should > be provided by the core if a publication does not include its own workflow > (and > not just as examples, but as a resource to fallback:// to). > > 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? Hmm, no idea - what do the others think? -- 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]
