On Mon, 2007-10-08 at 08:22 +0200, Felix Meschberger wrote:
Am Freitag, den 05.10.2007, 21:36 +0100 schrieb Torgeir Veimo:
I feel it's cleaner to fetch the manager from some sort of factory
instance. It wouldn't expose the implementation details of how the
manager is kept local to the
Felix Meschberger wrote:
Hi all,
Upon replying to Edgar's question regarding writing Content, I came to
thinking, that the ContentManager is a core interface of Sling and
probably should be made available more prominently. The most prominent
location for an interface in Sling would be the
On 5 Oct 2007, at 15:56, Felix Meschberger wrote:
What do you think of moving the o.a.s.content.ContentManager interface
to the Sling API and provide it through the ComponentRequest
instead of
having to access a request attribute:
public interface ComponentRequest extends
Hi Torgeir,
Am Freitag, den 05.10.2007, 17:25 +0100 schrieb Torgeir Veimo:
Having done some work recently with Day Communique, one of the
annoying things was that it subclasses HttpServletRequest.
Can you please elaborate on this ? Because we initially did not extend
HttpServletRequest but
On 5 Oct 2007, at 17:30, Felix Meschberger wrote:
Hi Torgeir,
Am Freitag, den 05.10.2007, 17:25 +0100 schrieb Torgeir Veimo:
Having done some work recently with Day Communique, one of the
annoying things was that it subclasses HttpServletRequest.
Can you please elaborate on this ? Because
