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-24 04:01 ------- (In reply to comment #7) > (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 :) Hmm, I'm afraid I don't see the point ... If the user reads something like <resource-type name="xhtml" workflow="cocoon://modules/workflow/presets/no-staging.xml"/> I guess she will figure out how to configure her own workflow schema. -- 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]
