atom feed18 messages in org.apache.incubator.sling-devRe: Expose standard SlingPostOperatio...
FromSent OnAttachments
Alexander KlimetschekAug 26, 2010 5:13 am 
Felix MeschbergerAug 26, 2010 5:47 am 
Alexander KlimetschekAug 26, 2010 6:34 am 
Alexander KlimetschekAug 26, 2010 6:34 am 
Bertrand DelacretazAug 26, 2010 6:55 am 
Felix MeschbergerAug 26, 2010 7:52 am 
Alexander KlimetschekAug 26, 2010 9:37 am 
Alexander KlimetschekAug 26, 2010 9:42 am 
Justin EdelsonAug 26, 2010 10:18 am 
Alexander KlimetschekAug 27, 2010 2:08 am 
Felix MeschbergerAug 27, 2010 2:44 am 
Alexander KlimetschekAug 27, 2010 3:47 am 
Felix MeschbergerAug 27, 2010 4:22 am 
Bertrand DelacretazAug 27, 2010 4:50 am 
Alexander KlimetschekAug 27, 2010 5:49 am 
Felix MeschbergerAug 27, 2010 6:56 am 
Alexander KlimetschekAug 27, 2010 7:06 am 
Felix MeschbergerSep 2, 2010 11:30 am 
Subject:Re: Expose standard SlingPostOperations as services?
From:Bertrand Delacretaz (bdel@apache.org)
Date:Aug 27, 2010 4:50:56 am
List:org.apache.incubator.sling-dev

On Fri, Aug 27, 2010 at 1:22 PM, Felix Meschberger <fmes@gmail.com> wrote:

On 27.08.2010 12:47, Alexander Klimetschek wrote:

...For the "interesting" stuff, like NodeNameGenerator or MediaRangeList and co, I'd suggest to move them to public locations in commons-style-libraries, such as jackrabbit-jcr-commons or (I-don't-know-yet), to make them publicly available.

jackrabbit-jcr-commons is an uncontrollable biest .. ;-) So I'd rather not put stuff there, esp. not Sling specific or Web App specific stuff....

But we could have our own sling-jcr-commons or something like that. -Bertrand