Jörn Nettingsmeier wrote:
Richard Frovarp wrote:
I probably should know this, but what is the difference between
cocoon:/ and cocoon://?
cocoon:/ points at a matcher in the current sitemap, cocoon:// points
at the root sitemap.
I see this in the logs and would like to clear it up:
SocketListener0-9 WARN flow - usecases.js::executeUsecase() : The
use of the cocoon:/ protocol prefix in the <view uri="..."> attribute
is deprecated!
i think i introduced that message a while ago, because cocoon flow can
only handle cocoon:/-type urls, not arbitrary ones - imho it's better
to just have a matcher in there without the protocol part, lest people
think they can use arbitrary protocols in there.
If we are releasing a rewrite, we should probably try to eliminate
deprecation messages in our logs where possible.
very true. i should have cleaned that up while i was at it...
generally, in all <view uri=""> attributes, cocoon:/ can be removed
without any adverse effects (and should be)...
So my question for you is this: Is it just cocoon:/ or does it include
cocoon:// as well? The code in usecases.js matches cocoon:/ but the
subsequent substring will leave the trailing / from cocoon://
Richard
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
