Archive for the ‘Sling’ Category

OSGi Bundles, Apache Felix and Versioning

Thursday, March 3rd, 2011

I recently had an experience while working with a customer that has prompted me once again to post about what it taught me. The requirement that drove this experience was the necessity for a Maven/AntHill build and deploy automation for CQ package and OSGi bundle deployments. In order to make sure that all our code (bundles, jsp and design) was deployed simultaneously, we decided to take advantage of the “install” directory that can be located as a child of an “/apps/myApp” directory in CQ. This “install” directory is treated as a watched directory by the OSGi installer, and so any jars in that directory will be auto-installed upon installation of the package…or so we thought…


Blog Trickery Using XML-RPC

Monday, June 28th, 2010

I was recently asked by a client to explore a proof of concept to create a servlet within the CQ system that could receive requests via XML-RPC from a mobile or desktop based WordPress blogging application and basically trick it into thinking it was communicating with a WordPress blog. The idea was to let the authors of their blog pages have the flexibility to use pre-existing blogging applications without having to limit the pages themselves to rely on pre-fabricated blogging solutions such as Blogger, WordPress, or Movable Type.


OSGi Bundles…creating reference to BundleContext

Wednesday, April 21st, 2010

This week I was tasked with a relatively complex task by a client, which is requiring me to create an OSGi component that directly interacts with other OSGi services within the repository. My experience with OSGi being relatively minimal, I ran into a little snag: how to reference other OSGi services (a service can be an Interface or a Component) in the repository from MY OSGi component.


Interesting New Feature in CQ 5.3

Thursday, April 8th, 2010

So I’m on-site with a client in Phoenix, and I was directed to perform a “test-upgrade” to their CQ 5.2.1 code, to see how smooth the upgrade to 5.3 would be. It was a pretty good experience all-in-all, but I thought I would share a couple minor hiccups with the audience, just in case they may save some of you some time and frustration later.


University Of Cincinnati

Wednesday, April 7th, 2010

Towards the end of last year I helped the University of Cincinnati architect their undergraduate admissions site using Day Software’s revolutionary CMS product CQ 5.2.

The idea was to create templates and components for the admissions site in such a way that they could be easily extended and re-purposed for use with all the other numerous sites that currently live under the university’s domain. The project lasted about a month, and I not only provided the client with the architecture, templates and components that they needed to achieve this well thought out goal, I also helped to train the main U.C. web development team to use the product so that they could continue to work in the future with less support.

I’ve recently updated my own portfolio to include the U.C. undergraduate admissions site…you can see it by following the link below: of Cincinnati/

Cheers to Donna, T.J. and all the rest of you guys on the ongoing success of your implementation of the CQ system…it was truly a pleasure working with you!