For a publish server the repository action for a delete or a deactivate are the same - the publish server deletes the node and all it's children. When you deactivate the item is only retained on the author server. Whether or not a deactivation of that scale will impact your publish servers is highly...

You can also take a look at the bundles console in Felix and look for bundles that have not started. If you drill down to the details screen it should show where you have problem/missing dependencies. In addition as Jörg said your log files from the startup phase will have informative messages. In a...

Have you tried to recompile your OSGI services against the 5.6.1 dependencies. There have been significant API changes since 5.4 - my guess is some of your bundles may not be able to find required dependencies. You will likely need to change either dependency names or versions, and some case you may...

Are you using Jackrabbit instead of CRX? I have not idea what the upgrade path would look like if you were actually using Jackrabbit - I don't know of anyone who uses Jackrabbit with CQ. 

When you do the upgrade for from 5.4 to 5.6.1 your CRX instance will be upgraded for you, you shouldn't need to change your content at all. 

What are you using the generate your MessageDigest? If the source of you message digest is a node in the repository, as opposed to the actual file then difference is probably due to the last modified data varying across publish instances (that or the created date). If you are using the node then I'd...

Have you included the XML extension in you script name? .html is the default extension so you don't need to include it in script names, but when you need to support other script names they need to be included in the extension. So for example rather than just webinar.jsp you need to name your script ...

One approach I know will work is create a page at the URL you want to use and then pass the search term in as with a selector or a query string. The template you case your page off of could be implemented as a servlet - which would potentially be cleaner given you want to generate XML. 

The first example is the correct one, the second example is from version 5.1 and so is old and doesn't account for the latest updates to sling. Refer to these URLs for the latest Sling Script resolution logic:http://dev.day.com/content/ddc/blog/2010/08/understanding_howsc.html - blog post with some ...

So this was an interesting exercise in reverse engineering. I believe I have figured out - the naming conventions are 100 clear, but the key is following accurate naming conventions. If you want to access rendition with using the thumb selection (which maps to the com.day.cq.wcm.core.impl.servlets.T...