since you have the osgiconfig node, this can be safely in your git/svn. So always change the nodes in prod by installing a new config package which does this. This allows you better control.

In configuration tab in system console, you will see the pid for each configuration. When you click open the configuration model, you will see something like this.      Persistent Identity (PID)com.adobe.acs.commons.wcm.impl.ComponentHelperImpl

Yes, the best way to handle configurations for the same class, same project but in different environments is via run modes. Please refer to http://docs.adobe.com/docs/en/aem/6-0/deploy/configuring/configuring-osgi.html#OSGi%20Configuration%20in%20the%20Repository .

You can may be create a static collection. Please refer to http://docs.adobe.com/docs/en/aem/6-0/author/assets/managing-assets-touch-ui/managing-collections-touch-ui.html#Creating%20a%20Collection. These just group the images you select in to a collection. Collections are a logical concept. Referenc...

 http://jackrabbit.apache.org/oak/docs/security/authentication/ldap.html This link talks about how LDAP is plugged in. They have written an LDAPIdentityProvider http://grepcode.com/file/repo1.maven.org/maven2/org.apache.jackrabbit/oak-auth-ldap/0.17.1/org/apache/jackrabbit/oak/security/authenticatio...

The kerberos token needs to be validated and then only the user would be allowed. you can use http://jackrabbit.apache.org/oak/docs/security/authentication/externalloginmodule.html and create an externalloginmodule for this. Then you can also try to leverage http://docs.oracle.com/javase/7/docs/jre/...

Please check for js errors.If you remove your project code, is it coming up fine?

As long as your event handler is a osgi component ( @component annotation above your class name), you should be able to get the workflowService instance by doing the following. @Reference    private WorkflowService workflowService; 

Hi,  Typically , you need to identify all the packages that you need and export them. Identify all the dependent bundles and embed them in one big bundle. Please use an already existing osgi solr bundle like http://mvnrepository.com/artifact/org.apache.servicemix.bundles/org.apache.servicemix.bundle...

AEM already integrates with solr. Please have a look at http://docs.adobe.com/docs/en/aem/6-0/deploy/upgrade/queries-and-indexing.html . So solrj is already present as a bundle in AEM. In any case, i suggest you leverage the OOB integration. The OOB integration also respects the ACLs when it fetches...