Is there an API deployed in CQ5 we can use to manipulate PDFs?  I found a bunch of bundles in the OSGi console, but saw no documentation on how to use these libraries. Thank you

 5.6.0.20130125Is there a known problem about the component?

As complement, I can access the targeted video directly, from the DAM.  But the player on the publish instance just won't load it.  No error in browser console.  I don't know how to debug this.

Strange problem.I am trying to use CQ video component to insert an mp4 video in my page.  It works fine in my author env., but it's not loading on our publish instance.  What could be the problem?Thank you for your help.

I don't get it.  chrisu168 wrote... hi, I found out my problem, I wasnt looking in the right position to find the styling  what is the right position? I am unable to make any of the 2 dropdowns appear!  I have no idea why, and the weird thing is that it works on our QA, but not on our UAT, same node...

The thing we wanted to accomplish with this is component container: example, tabs.  Within each tab there would be a parsys.  But we wanted those parsys to be already configured to a list of components, thus the dynamic write operation in the design path.But you are right.  Maybe we designed this th...

We're having a strange problem on some of our instances.In some of our template JSPs, we a writing in the repo under /etc/designs/<% Session session = (resource.getResourceResolver().adaptTo(Session.class)); //... try{ Node n= session.getNode(resourceDesign.getPath()+"/jcr:content/"+template+"/ancho...

Ok got it.In bundle version 0.0.1.R1394715, the class SslFilterRequest has a method:public StringBuffer getRequestURL() { if (this.requestURL == null) { // insert an 's' after the http scheme StringBuffer tmp = super.getRequestURL(); tmp.insert(4, 's'); this.requestURL = tmp.toString(); } return new...

it worked.we are using version 0.0.1.R1394715.were you aware of this already?

We're having a hard time finding the cause of a strange problem.  After we have enabled SSL on our publish instance, the error handler is page for 404s is behaving in a weird fashion: the JSP is receiving the original request, but the protocol is "httpss" (yes, another 'S', this is not a typo)Have y...