In response to KERN-2966[1], I'd like to disable the ".txt" selector. This
doesn't stop the retrieval of nodes that end in .txt but simply turns off
the default handler in Sling that produces text data for an arbitrary node
in the system that isn't covered by a specific handler (e.g. handler for
resource type or path).
So for nodes that are stored in JCR at /foo/bar/baz, you won't be able to do
GET /foo/bar/baz.txt
But you will still be able to do
GET /foo/bar/baz.json
For nodes outside JCR, i.e. nodes in sparse (mainly /p/abcdef and /~userid),
we already do not support text. To my knowledge we don't use text
feeds internally
at all.
If anyone has been relying on Nakamura emulating the pure Sling-like behavior
of serving data as text on arbitrary JCR nodes, please speak up now.
Otherwise, we will go ahead with the change.
Carl
[1] https://jira.sakaiproject.org/browse/KERN-2966
_______________________________________________
oae-dev mailing list
[email protected]
http://collab.sakaiproject.org/mailman/listinfo/oae-dev
