Thanks a lot for your feedback. The described way is also present in the current (CQ5.5) implementation for the LinkCheckerTransformer (LinkCheckerSettingsProvider or so) and I will use this approach in my implementation too.
But what to do when I want to use a special Transformer (an therefor a separated pipeline) on any publish instance but not on any author instance? Well the solution could be to introduce an "enabled" flag but is this the best solution? Wouldn't it make sense to obtain different configurations per runmode in the ProcessorManagerImpl directly (that is also a OSGI Service implementing the ProcessorManager interface)? Again, thanks a lot, Dirk -----Ursprüngliche Nachricht----- Von: Carsten Ziegeler [mailto:[email protected]] Gesendet: Mittwoch, 10. April 2013 14:36 An: [email protected] Betreff: Re: Configure rewriter pipeline per runmode What about having rewriter configurations as OSGi configurations? This should be not too hard to implement. However as an OSGi configuration is a simple map, defining how to handle configuration props might not look that nice. Carsten 2013/4/10 Ryan Lunka <[email protected]> > Interesting timing...I actually just wrote a blog post on this topic: > http://www.citytechinc.com/us/en/blog/2013/04/extensionless-urls-in-ad > obe-experience-manager.html > . > > However the specific answer to you question is that you use a factory > class that actually creates your pipeline component. That factory > class will be an OSGi service which can be configured differently per > run mode, by using the typical OsgiConfig node type. The actual class > that does the work of the pipeline component is just a class, not an > OSGi service. The factory class/OSGi service knows which pipeline > component object to build and has a "pipeline.type" property specified > that effectively registers is it with Sling. > > Make sense? > > -- > > Ryan D. Lunka > > > > > > On Apr 10, 2013, at 4:34 AM, "Rudolph, Dirk" > <[email protected]> > wrote: > > > Hi all, > > > > > > > > currently I'm working with the Apache Sling rewriter bundle to build > > a > pipeline for post-rendering link manipulation. I had a look on the > source code and have seen, that the pipeline configuration path is fix > (/config/rewriter) below my application directory (/apps/appname). Now > my question is: What is the common way to configure different > pipelines for different runmodes? E.g. I have a runmode "publish" that > should use /apps/appname/config.publish/rewriter and one called > "author" that should use /apps/appname/config.author/rewriter. > > > > > > > > Thanks alot, > > > > Dirk Rudolph > > > > > > > > > > T-Systems Multimedia Solutions GmbH > > Organisationseinheit CCS > > Dirk Rudolph > > Software-Entwicklung, OCJP > > > > Hausanschrift: Riesaer Straße 5, 01129 Dresden > > Postanschrift: Postfach 10 02 24, 01072 Dresden > > +49 351 2820-5363 (Tel) > > E-Mail: [email protected] <mailto: > [email protected]> > > Internet: http://www.t-systems-mms.com > > <http://www.t-systems-mms.de/> > > > > T-Systems Multimedia Solutions GmbH > > > > Aufsichtsrat: Klaus Werner (Vorsitzender) > > Geschäftsführung: Peter Klingenburg, Dr. Jens Nebendahl > > Handelsregister: Amtsgericht Dresden HRB 11433 Sitz der > > Gesellschaft: Dresden > > Ust-IdNr.: DE 811 807 949 > > > > > > > > > > > > -- Carsten Ziegeler [email protected]
