I was wondering the same thing myself and thought you might have found a bug
when using implicit and explicit orderings in separate modules.
Here is how Tapestry initializes them:
configuration.add("DocumentLinker", documentLinker);
configuration.add("JavaScriptSupport", javaScriptSupport);
configuration.add("RenderSupport", renderSupport);
configuration.add("InjectDefaultStylesheet",
injectDefaultStylesheet);
configuration.add("ClientBehaviorSupport", clientBehaviorSupport);
configuration.add("Heartbeat", heartbeat);
configuration.add("ValidationDecorator",
defaultValidationDecorator);
And the javadocs from OrderedConfiguration:
"If no constraints are supplied, then an implicit constraint is supplied:
after the previously contributed id within the same contribution method."
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/BreadCrumbsModule-error-tp5713794p5713805.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
